Product1 distinct publisher3 min readPublished
A judge in the Northern District of California ruled on the merits and struck the designation down on constitutional, statutory and APA grounds. For vendor-risk teams, the lesson is that a federal exclusion can be scoped around and can then evaporate.
The Product Desk · Product desk
Compiled by The Product DeskSomething wrong?How this is made
A designation like this one does its damage through other people's compliance departments. The order did not only tell federal agencies to stop using Anthropic's products. It told every defense contractor to stop doing business with the company, including work unrelated to the military [2]. That becomes a line in a vendor register, an exception ticket, a migration plan with a date on it. The office that wrote the order absorbs none of that work.
A federal supply-chain-risk designation can look like a fact of the world, the way an export rule is a fact of the world. The record says otherwise. According to Techdirt's account of the ruling, the punishment was broadcast on social media before the formal process of making the required findings had even begun [8], and the court has now ruled on the merits and given Anthropic both a permanent injunction and vacatur of the agency action [3].
The vacatur rests on four grounds: First Amendment retaliation, denial of the pre-deprivation process required under the Fifth Amendment, a violation of the governing statutory scheme at 10 U.S.C. 3252, and arbitrary and capricious action under the APA [5][6][7]. Four independent holdings [9]. To put the same ban back, the government has to cure all four, not the cheapest one.
The narrower half of the ruling matters more to a shortlist than the headline does. The court said the Department is free to select the AI vendor of its choice, and held only that the broad measures imposed on Anthropic were illegal and baseless [4]. So what came back is eligibility, not a contract. A vendor can be un-blacklisted by a judge on Thursday and still lose the deal on Monday for ordinary reasons, and nothing here obliges anyone to buy Claude.
One small filing detail with practical consequences: Techdirt notes that the court and Anthropic both used the administration's "Department of War" nickname, which Techdirt declines to adopt until Congress agrees to the renaming [10]. Anyone pulling the order for a risk file should search under both names.
The people this ruling is for are not the litigators. They are the vendor reviewers who received a directive with no findings attached and were expected to act on it inside a week. The test that would have helped them is a two-column sheet. Column one: the document the exclusion rests on, either a statutory finding with an administrative record or a press quote and a post. Hegseth's stated reasons included that Anthropic had "delivered a master class in arrogance" [11]. Column two: the cost of undoing compliance once you have complied.
A post in column one plus an expensive rip-out in column two is the case that just got vacated. The response that survives a Friday review is a documented pause rather than a purge: new spend frozen, the integration path and contract vehicle left standing until the litigation resolves. The tradeoff belongs in the same memo. Pausing means carrying a live compliance exposure while the case runs, and someone senior has to sign their name to that. Purging means paying for the removal and then paying again to reverse it, on the strength of an order a court found baseless [4].</body_markdown> </invoke>
Ranked by verification strength, evidence, and original report placement.
After an earlier preliminary injunction, the court ruled on the merits, finding in favor of Anthropic on most of its claims and granting all the relief it sought: both a permanent injunction and vacatur of Hegseth's agency action.
Pete Hegseth declared Anthropic a national security risk because it would not agree to his demands for what Claude should be able to do, and Anthropic sued to challenge the directives, including a challenge brought in the Northern District of California.
The challenged action was to designate Anthropic a supply chain risk to national security, order all federal agencies to permanently stop using Anthropic's products, and ban all defense contractors from doing any business with Anthropic, even if unrelated to the military.
The court stated that the Department is undisputedly free to select the AI vendor of its choice, but that the evidence demonstrated the broad measures imposed on Anthropic were illegal and baseless.
The court found the challenged actions constituted unlawful retaliation in violation of the First Amendment, with Anthropic's protected speech a substantial motivating factor for the defendants' speech-chilling conduct.
The court found Anthropic was denied the pre-deprivation process required under the Fifth Amendment.
Distinct publishers with included, body-backed reporting in this cluster.
2 articles · August 28, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
product
Court reversal turns the Pentagon's Anthropic ban into a migration teams may have to run twice1 distinct publisher
build
Anthropic's federal ban falls on a record that failed the supply-chain statute1 distinct publisher
leadership
A federal judge shields Anthropic's AI use-case limits from government retaliation1 distinct publisher
leadership
The chain of command survives AI; the judgment inside it may not1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
The order speaks at length; nobody else speaks at all
Almost every load of this story is carried by direct quotation from the decision, including administrative record cites for the Hegseth and Trump statements, so a reader can see the court's language rather than a paraphrase of it. What is missing is everything around the document: no case number, no ruling date, no judge, no Pentagon response, and no second newsroom that read the same order.
A docket, not a deployment record
Nothing in this reporting measures use. The only uptake-adjacent fact is a legal one: agencies and defense primes were ordered to stop, and that order is now void. Whether any agency actually removed Claude, what it ran instead, or whether anyone has switched back is unaddressed, and we will not fill that in by inference.
Hotter framing than the holding, but the holding is quoted
'Department Of Unconstitutional Revenge' and a dept line about the AI company being more principled than the government run well ahead of what a single district court decided, and the read that a federal exclusion 'evaporates' skips the appeal that goes unmentioned. The gap stays small because the substance underneath is the order's own words, and the court's own caveat — the Department may still pick whatever vendor it likes — survives into the reporting instead of being edited out.
Stance declared out loud, defendants left unquoted
Techdirt is not hiding anything — it announces its refusal to use the administration's name for the Department and files the story under a dept line taking Anthropic's side — and a declared bias is easier to correct for than a concealed one. The real distortion risk is structural: the losing side never speaks here, and Anthropic's own commercial stake in winning the safeguards argument is never examined.
Well-quoted, thinly sourced, and counted twice
We are confident about what the order says and much less confident about where the dispute now stands. Four separate grounds make the outcome harder to unwind, which raises our footing on the legal result; one publisher appearing twice, with no ruling date and no word on an appeal or on the parallel challenges, caps how far that footing extends.