The AI Safety Order's Real Test: Procurement, Not Proclamations

Archi4 min read

aipolicyprocurement

Contents
  1. The Headline You Saw Versus the Rule That Binds
  2. What the Procurement Clause Actually Does
  3. The 180-Day Clock
  4. What the Coverage Got Wrong
  5. The Contract Clauses You Will Not See
  6. What to Watch Next
  7. The Local Gap

The Headline You Saw Versus the Rule That Binds#

When the executive order on artificial intelligence landed, most coverage led with the big numbers and the bold verbs: companies must report, agencies must assess, models must be tested. Those are the parts that fit in a headline. The parts that will actually change behavior are buried in Section 10, which directs the Federal Acquisition Regulation Council to consider amendments to the FAR within 180 days. That clause got almost no attention. It is the one that matters.

The federal government buys about $700 billion in goods and services each year, according to the most recent figures from the Office of Management and Budget. A meaningful and growing slice of that is software with machine learning components. When the FAR changes, every vendor selling to the government has to adjust contracts, documentation, and internal review processes. That is not a proclamation. It is a purchasing condition, and purchasing conditions have teeth.

What the Procurement Clause Actually Does#

The order does not ban any AI system. It does not create a new regulator. What it does is ask the acquisition council to think about whether contractors should be required to provide information about their AI systems, whether certain uses should be prohibited in federal contracts, and whether agencies should prefer vendors that meet specific safety and transparency practices.

That is careful, bureaucratic language. It is also how the government reshapes markets. Companies that sell payroll software, benefits administration platforms, and case management tools to federal agencies will have to answer questions about training data, model evaluation, and human oversight. Small vendors with thin compliance teams will feel this first.

The 180-Day Clock#

The 180-day window is short for a regulatory process that normally takes years. The FAR council has to draft language, publish it for comment, review thousands of responses, and finalize a rule. Historically, major FAR amendments take 18 to 36 months. The order sets an ambitious timeline, and the council may miss it. The missed deadline will not make headlines either, but it will tell you how seriously the procurement piece is being taken.

What the Coverage Got Wrong#

Two things went missing from most coverage. First, the order applies to federal agencies as buyers, not just to companies as sellers. That distinction matters because the government is one of the largest purchasers of AI-enabled tools in the country. When it changes what it buys, it changes what gets built.

Second, the order does not address state and local procurement. Cities and counties spend billions on algorithmic tools for policing, benefits eligibility, and school assignment. None of that is touched by the federal order. A police department in Ohio can still buy a predictive policing system without the documentation the federal rule might require. That gap is not a flaw in the order. It is a boundary, and the coverage that treated the order as a national AI policy missed it.

The Contract Clauses You Will Not See#

The real work happens in individual contract negotiations. Agencies will start inserting clauses about model documentation, audit rights, and data provenance. Those clauses will be inconsistent across agencies. A vendor selling to the Department of Veterans Affairs may face different requirements than one selling to the Department of Agriculture.

That inconsistency is not a bug in the system. It is how federal procurement usually works. Agencies have wide latitude to set their own requirements within the FAR framework. The result is a patchwork that large vendors can navigate and small vendors cannot. The consolidation of the government AI market is a likely outcome, and nobody wrote a press release about it.

What to Watch Next#

The first signal will be the draft FAR language. If it includes specific testing requirements, vendors will start building compliance documentation into their products. If it is vague and principle-based, the effect will be minimal.

The second signal will be the first contract award that includes AI-specific clauses. That award will set a precedent for what agencies expect. Vendors will read it closely. So should anyone who cares about how AI gets deployed in public services.

The third signal will be the budget. The order does not come with new funding for agency AI review offices. Without staff to evaluate vendor claims, the procurement rules become a paperwork exercise. The money is the tell.

The Local Gap#

The federal order does not reach state and local governments. That leaves a large share of public sector AI deployment unregulated by the new rules. Some states are moving on their own, but the pace is uneven. The federal procurement lever is powerful, but it stops at the agency boundary. The next front in AI policy is city hall, and the headlines have not found it yet.

More articles