Picture a fire-suppression shop that maintains a kitchen system at a U.S. military base. The company holding the federal award—the prime—sends over a form asking whether anyone used Claude to perform the job. Claude is the writing, research, and coding assistant made by Anthropic. The shop never sold software to the Pentagon, formally the U.S. Department of War; it used a common office tool to help turn field notes into a closeout report. Now it has a contract question it may not have known existed.

The shop is a composite, but the contract route is real. Claude-use restrictions are already appearing in public buys for custodial work, kitchen fire-suppression service, and furniture installation. If your business has no connection to a Pentagon agreement and no prime has passed this rule down to you, this specific restriction is probably not about your shop. If you do work inside that contract chain, do not sign a broad statement until you know what the agreement—and the software used on the job—actually say.

How an argument over military AI became a purchasing rule

Anthropic makes Claude, the writing, research, and coding assistant used by individuals, software companies, and government agencies. The Pentagon had been using versions of Claude for national-security work, but the two sides disagreed about the limits that should remain on that use. The Pentagon wanted permission to use the model for any lawful purpose. Anthropic agreed to loosen many restrictions but would not permit two uses: fully autonomous lethal weapons, which it said the technology was not yet reliable enough to power, and mass surveillance of Americans, which it said created serious democratic and civil-liberties risks. The Pentagon argued that those limits could make Claude unavailable when a mission required it.

In March 2026, the Pentagon used a federal technology-supply-chain law to begin removing Claude from its systems and to restrict its use in work performed for the Department. “Supply chain” is confusing language here: it refers to the government’s technology and service vendors, including software used by a prime supplier and by the smaller firms working underneath it.

Anthropic challenged the action. On September 25, 2026, the U.S. Court of Appeals for the D.C. Circuit rejected that challenge in a 2–1 decision. The court left the Pentagon’s narrower procurement action standing: Claude can be removed from Department systems and restricted when it is used to perform covered Department work.

Why you may have heard two different versions of the story

Another federal court in California had already blocked a broader government move against Anthropic. That judgment stopped an attempt to make military suppliers cut off unrelated commercial business with the company, and it vacated a separate designation under a different defense statute. The September 25 appeals-court ruling did not reverse that decision. The two cases dealt with different legal tools, so both results can exist at the same time.

In plain English: this is not a national ban on Claude, and it is not an automatic order to delete Claude from every company device. The surviving action is narrower. It follows Department systems and covered contract work. A company may have to stop using Claude on one federal job while remaining free to use it for unrelated commercial work. That distinction is why a headline cannot answer the question for your business; the agreement, order, modification, and written notice do.

How the rule reaches a shop that does not sell technology

Federal work often moves through layers. One company holds the government award. That company hires other firms, and the agreement passes certain requirements down to them. That passed-down rule is called a flowdown. Public solicitations have already included Anthropic terms in buys for custodial services, kitchen fire-suppression service, and furniture delivery and installation. None of those firms needs to build AI for the clause to appear.

Back to the shop in the opening. When the prime sends a certification asking whether Anthropic products were used “in performance” of the work, the shop has three separate questions: Was this order covered? Was the Claude-assisted report part of performing it? What exactly is the shop being asked to certify? Deleting the app does not answer any of them, and signing first is worse.

September 29 is the Pentagon’s outer date. Your date comes from the paperwork

The March 2026 removal memo told Department systems to remove Anthropic products as soon as practical and set 180 days as the outer limit. Reporting on a later April 2 implementation memo, along with the Department’s official compliance form, puts the Department-wide outer transition date at September 29, 2026. The September 25 ruling did not create that date. It left the underlying procurement action in place as the date approached.

Your own obligation can still be earlier, later, narrower, or nonexistent. The practical test has two parts. First, did the restriction enter the base agreement or this specific order through the original paperwork, an amendment before award, a formal modification after award, or a written flowdown from the prime? Second, did Claude touch the work or deliverables for that order? A general deadline in the news does not replace either answer.

If FAR 52.204-30 is already part of the agreement, its inquiry and reporting duties may apply when a new federal supply-chain order could affect the work. Identifying or receiving notice of covered use can trigger an initial report within three business days; the mitigation follow-up can be due within ten business days of that initial submission. A prime or Pentagon branch may also send separate instructions. Read that exact language and get unclear scope confirmed in writing.

Canadian businesses are not covered merely because they do defense work in Canada. They enter this issue when they sit inside a U.S. Department contract chain and accept the relevant rule.

What to check before anyone signs a statement

  1. Pull and search the complete agreement. Collect the award or subcontract, individual orders, solicitation, amendments, formal changes, prime notices, and every certification request. An umbrella agreement can say one thing while an order says another.
  2. Map the real workflow. Identify where Claude was used directly and whether another software product sends covered work to Anthropic behind the scenes. Separate the federal job from shared office systems and unrelated commercial activity.
  3. Stop confirmed covered use and put uncertainty in writing. Move a clearly covered workflow to an approved fallback. Ask the prime—or the contracting officer if you hold the federal award—which rule applies, which order it reaches, and what “use in performance” means here.
  4. Record the cost and get the right advice. Track new licences, staff time, retraining, testing, delay, and rework. Cost recovery is not guaranteed, but government-contract counsel will need those records to assess a request for added time or money.

Paperwork terms: Search for Anthropic, Claude, the Federal Acquisition Supply Chain Security Act (FASCSA), FAR 52.204-29, and FAR 52.204-30. FAR 52.204-29 is the solicitation-stage representation; FAR 52.204-30 carries the performance, inquiry, reporting, and flowdown duties. Technical note: DFARS 252.239-7017 and 252.239-7018 implement § 3252. California vacated Anthropic’s designation under that statute, so those clauses do not independently recreate an Anthropic restriction.

This is not legal advice. If the language is unclear or the certification is broad, take the full document stack to the prime, the contracting officer where appropriate, and government-contract counsel before signing.

What may land in your inbox next

Expect inconsistent paperwork rather than one dramatic nationwide switch. Pentagon branches and large suppliers have used different notices, deadlines, and statements, so smaller firms are likely to receive requests that are broader or less precise than the underlying rule. Disputes are likely to centre on whether the clause entered the order, whether it was passed down correctly, and whether a shared office tool counted as use in performing the job. Where a restriction was added mid-job, replacement costs may also lead to requests for added time or money. Anthropic may seek further review, but without a new court order pausing the action, that possibility does not change today’s paperwork.

OPS covered the broader risk of suddenly losing model access in June’s continuity guide. That article was about keeping the business running when a tool stops working. This event is different: Claude may still work perfectly while a specific agreement makes its use a problem.

Sources

If a Claude certification lands in your inbox, match it to the actual order before you sign.