A Court Voided the Designation. Check Your Contract Anyway.

This describes the record as of September 1, 2026. The government is expected to appeal and a separate, narrower Anthropic case is still pending in the D.C. Circuit. None of this is legal advice. If you are carrying an active obligation, take these questions to counsel and to your contracting officer.

Judge Rita F. Lin of the Northern District of California issued a 59-page decision on August 27, 2026 in Anthropic PBC v. U.S. Department of War (No. 26-cv-01996-RFL), granting permanent injunctive relief. The Department’s designation of Anthropic as a supply chain risk was unlawful retaliation for the company’s protected speech. The measures were, in the court’s words, “illegal and baseless,” and “the empty invocation of national security is not a blank check to punish and retaliate against government critics.”

If you run programs on DoD networks, the interesting question is not whether Anthropic won. It is what you are supposed to do on Monday. That answer is messier than the headline.

The sequence matters more than the ruling

When	What happened
Feb 2026	The Secretary of War designates Anthropic a supply chain risk, starting a six-month phase-out
Mar 9, 2026	Anthropic sues in N.D. Cal. One APA count for skipping the procedure Congress set, two First Amendment retaliation counts
Mar 26, 2026	Judge Lin grants a preliminary injunction. The Pentagon’s CTO says publicly that the ban still stands
Apr 8, 2026	Anthropic loses its appeals court bid to block the blacklisting pending appeal
Jul 9, 2026	Reporting indicates the Air Force Research Laboratory tells contractors to purge Anthropic products by September 1, with usage self-reports due August 1
Aug 27, 2026	After trial, Lin grants permanent injunctive relief

Look at the middle of that table. A federal court called the designation illegal retaliation in March. Purge directives were still going out to contractors in July, three and a half months later, with reporting deadlines in August. And the appellate posture cut the other way in April.

For five months the legal status of the designation and the instructions reaching contractors pointed in opposite directions. Nobody at a program office called anyone to explain.

What the August ruling does, and what it does not

It blocks the challenged designation and the broad measures built on it. Agencies cannot lean on that designation as the basis for action.

It does not make anyone buy anything. The Department can still decline to procure Anthropic products on ordinary acquisition grounds. A First Amendment remedy strips out an unlawful basis for exclusion. It does not hand anybody a contract.

Its scope is narrower than “the ban is over.” Reporting indicates Lin declined to extend permanent relief to agencies that took no relevant action, or that took only interim measures. Relief tracks conduct.

And it is not final. An appeal is expected. The D.C. Circuit case is still live.

The gap that actually determines your exposure

Your obligations do not run to a court docket. They run to a contract, a clause, and a contracting officer.

An injunction can knock out the legal foundation of a directive without retracting the directive itself. Program offices do not re-paper their instructions the moment a district court rules. Some will move fast, some will wait for the appeal, and some will not revisit it until a contractor asks. March is the proof. An injunction issued, the Pentagon’s own CTO said the ban stood, and the memos kept coming.

That leaves real risk running both directions, and both deserve saying plainly.

Purge anyway and you may strip working capability out of a delivered solution, at cost, under schedule pressure, possibly weakening your technical approach, all on the strength of a designation a court has now permanently enjoined. If the directive is later withdrawn you do not get that work back.

Hold and wait, and if a contracting officer or program office keeps enforcing, which is exactly what happened after March, you are non-compliant on a live instrument. Self-reporting deadlines do not pause because you believe the underlying designation is void.

Neither one is obviously right. A contractor is also not the party who gets to decide.

The disciplined move

Ask, in writing, on every affected instrument: does the purge direction remain in effect in light of the August 27 order?

That question does three useful things at once. You get an authoritative answer from the only party entitled to give one. You build a contemporaneous record of acting in good faith. And the risk of the answer sits with the government, where it belongs.

What it is not is a way to stall. A pending question relieves nothing that is currently in force, and the self-reporting obligations stand on their own regardless of what happens to the designation underneath them.

Why this outlives the case

Take the names out and a structural problem is left over, one that will keep recurring as agencies buy more AI from fewer suppliers.

A model vendor ends up buried inside delivered systems. Inside COTS products, inside subcontractor toolchains, inside development environments nobody inventoried. When that vendor’s status changes by administrative action rather than technical failure, the obligation propagates outward, prime to sub to teaming partner. That propagation is what makes it expensive. It is the Governance Must Span Systems problem arriving through procurement policy instead of architecture.

The legal status did not propagate the way the obligation did. The directive reached every tier of the supply chain in weeks. The ruling that undercut it reached almost none of them. Trust Does Not Travel usually gets invoked for delegation between agents. It works just as well for delegation between contract tiers, where each layer inherits an instruction without inheriting the context that would let it evaluate one.

The lesson is not about this vendor. It is that an organization which cannot answer “where does this model appear across everything we deliver, including our partners’ pieces” cannot respond to a designation event in either direction. It cannot comply quickly and it cannot safely decline to. Build that inventory before you need it. The next designation will not come with more warning than this one did.

Facts current as of September 1, 2026. This summarizes public reporting and court filings. It is not legal advice, and the posture is moving.