placeholder

Introduction: A Contractor Punished for Its Own Product Rules

On March 9, 2026, Anthropic PBC filed suit in the Northern District of California against the U.S. Department of War, fifteen other federal agencies, and the officials who head them, seeking to set aside a presidential directive, a "Supply-Chain Risk to National Security" designation, and the wave of contract terminations that followed.1 What makes the case interesting is not that a government contractor lost a contract, but Anthropic's argument: it declined to strip two use restrictions from Claude's Usage Policy, a prohibition on lethal autonomous warfare without human oversight and a prohibition on the mass surveillance of Americans, after the Department demanded "all lawful use" language in its contracts.2 The following analysis discusses the complaint's five counts, situates the case within First Amendment retaliation doctrine and the Youngstown separation-of-powers framework. Everything attributed to the parties below is drawn from Anthropic's complaint and public statements; the government defendants have not yet answered.

The Chronology

Anthropic had supplied Claude to the Department of War since 2023, including a custom fine-tuned version deployed on classified networks, and had been negotiating an "any lawful use" contract addendum for a new "GenAI.mil" deployment through late 2025 and early 2026.3 On February 24, 2026, Secretary of War Pete Hegseth met with Anthropic CEO Dario Amodei and gave the company until 5:01 p.m. Eastern on February 27 to abandon its two restrictions or face either commandeering under the Defense Production Act or exclusion as a "supply chain risk."4 On February 26, Amodei issued a public statement reaffirming that the two restrictions address uses "simply outside the bounds of what today's technology can safely and reliably do" and that Anthropic "cannot in good conscience accede to" the Department's request — the statement Anthropic itself now attaches as evidence of its protected speech.5 The next day, before its own deadline had run, the government moved: President Trump posted on Truth Social directing "EVERY Federal Agency" to "IMMEDIATELY CEASE all use of Anthropic's technology," and Secretary Hegseth followed within hours with a post directing the Department to designate Anthropic a "Supply-Chain Risk to National Security" and barring "any contractor, supplier, or partner that does business with the United States military" from conducting "any commercial activity with Anthropic."6 A formal two-page letter invoking 10 U.S.C. § 3252 arrived by email at 8:48 p.m. Eastern on March 4, nearly a week after the designation had already been announced on social media.7

I. The Statutory Claim: Supply-Chain-Risk Authority Stretched Past Its Terms

Count I is built on 10 U.S.C. § 3252, the statute Congress enacted to let the Department exclude a "source" from covered procurements where necessary to protect against the risk that a foreign adversary will "sabotage . . . or otherwise subvert" a covered information system.8 The provision is not a general-purpose contracting remedy; it is tethered to sabotage and subversion risk, defines "covered articles" and procedures with some specificity, and - critically - requires the Secretary to consult with relevant officials, make a written determination that exclusion is necessary and that less intrusive measures are unavailable, and notify the appropriate congressional committees before acting.9

Anthropic's complaint argues the Secretarial Order fails on both the substantive and procedural axes of Section 3252. Substantively, the "adversary" concept in the statute and its implementing authorities has historically meant designated foreign threats - China, Russia, Iran, North Korea, Cuba, and Venezuela under Executive Order 13,873 - not a Delaware public benefit corporation headquartered in San Francisco that holds an active facility security clearance and has, according to the complaint, taken affirmative steps to keep its models out of the hands of state-sponsored cyber operators.10 Procedurally, the complaint alleges no interagency consultation occurred, no written necessity determination was made before the February 27 announcement, and Congress was never notified - omissions that, if borne out, would place the designation outside "observance of procedure required by law" under 5 U.S.C. § 706(2)(D).

The complaint's strongest arbitrary-and-capricious argument, drawn from Motor Vehicle Manufacturers Ass'n v. State Farm, may be the internal contradiction it identifies: the same Secretarial Order that brands Anthropic's products a sabotage-and-subversion risk also directs that "Anthropic will continue to provide the Department of War its services for a period of no more than six months."11 An agency that genuinely believed a contractor's technology could be subverted by a foreign adversary would not, in the same breath, order six more months of continued reliance on that technology for national-security missions. State Farm requires an agency to "articulate a satisfactory explanation for its action including a rational connection between the facts found and the choice made"; an unreconciled six-month carve-out sitting alongside a sabotage-risk finding is the kind of "unexplained inconsistency" reviewing courts have treated as evidence of arbitrariness rather than reasoned decision-making.

II. Constitutional Retaliation: The First Amendment Claim

Count II reframes the same facts as a First Amendment retaliation claim, and it is here that the case moves from ordinary procurement law into more consequential constitutional territory. The Supreme Court's retaliation framework, most recently restated in National Rifle Ass'n of America v. Vullo and Nieves v. Bartlett, requires a plaintiff to show it engaged in constitutionally protected activity, that the government's action would chill a person of ordinary firmness from continuing that activity, and that the protected activity was a substantial or motivating factor in the government's conduct.12

Anthropic's complaint identifies several layers of protected expression: its lobbying and legislative advocacy on AI-safety bills; its published Usage Policy, which the complaint characterises as public speech embodying the company's "foundational commitment to the safe and responsible use of AI"; Amodei's public statements, including a June 2025 New York Times op-ed opposing a federal moratorium on state AI regulation and the February 26, 2026 statement described above; and Anthropic's direct petitioning of the Department during contract negotiations, which the complaint grounds in the First Amendment's Petition Clause rather than treating as ordinary commercial back-and-forth.13

What distinguishes this case from the run of retaliation litigation, where motive must typically be inferred from timing and pretext, is that the complaint can point to direct statements from the alleged retaliators. President Trump's Truth Social post derided Anthropic as a "RADICAL LEFT, WOKE COMPANY" engaged in "selfishness"; Secretary Hegseth's own post accused the company of "corporate virtue-signaling," "defective altruism," and being insufficiently "patriotic," and declared that "Anthropic's stance is fundamentally incompatible with American principles."14 Retaliatory-motive cases rarely come with this degree of contemporaneous, on-the-record explanation from the decision-makers themselves - which is precisely why the complaint treats causation as effectively conceded rather than merely inferable.

Because the retaliation is alleged to target Anthropic's viewpoint on a matter of public concern - the safe and responsible use of frontier AI - the complaint argues strict scrutiny applies, and that the government cannot satisfy the "least restrictive means" requirement of McCullen v. Coakley when an unrestrictive alternative was sitting in plain view: simply declining to renew the contract and procuring from a different vendor, an option Anthropic says it repeatedly offered to facilitate.15 If terminating the relationship without the designation, the blacklist language, and the public denunciations would have served the government's stated interest just as well, the additional punitive measures become difficult to justify as narrowly tailored to anything other than punishing Anthropic's expression.

III. Ultra Vires Executive Action and the Youngstown Framework

Count III proceeds independently of the First Amendment, arguing that the Presidential Directive exceeds any authority the Constitution or Congress has conferred on the President. The complaint invokes Justice Jackson's tripartite framework from Youngstown Sheet & Tube Co. v. Sawyer: presidential power "must stem either from an act of Congress or from the Constitution itself," and here Anthropic says there is neither.18 No statute authorizes a directive ordering every federal agency to cease using a single company's products because that company declined to alter its own product's usage restrictions in contract negotiations, and the complaint catalogs the detailed procurement framework in Titles 10 and 41 of the U.S. Code — including the specific, procedurally bounded debarment regime in 48 C.F.R. Subpart 9.4, which is "not a remedy for mere contract failure" and "may never be used for purposes of punishment" — as evidence that Congress has already occupied this field with safeguards the Directive bypassed entirely.19

The complaint goes further, characterizing the Directive as functionally resembling a bill of attainder: a "prepared and proclaimed government blacklist" naming one company and imposing consequences on it without investigation, trial, or process, language borrowed from Justice Black's concurrence in Anti-Fascist Refugee Committee v. McGrath.20 Because the Bill of Attainder Clause of Article I formally constrains Congress rather than the President, this is pled as an ultra vires and due process theory rather than a freestanding attainder claim — but the analogy does useful work, framing the Directive's central defect as its individualized, punitive, process-free character rather than any generally applicable rule.

V. Due Process and the De Facto Debarment Problem

Counts IV and V of the complaint concern due process and debarment. The Fifth Amendment due process claim rests on two protected interests: a liberty interest in Anthropic's reputation, harmed by the "Supply-Chain Risk to National Security" label itself, and a property interest in its existing government contracts and business relationships.21 The most concrete argument here is that the designation operates as a de facto 'debarment' (i.e. excluding Anthropic from federal contracting government-wide) without any of the procedural protections that formal debarment under FAR Subpart 9.4 would otherwise require, including notice, an opportunity to respond, and a reasoned written determination. Courts including the D.C. Circuit in Trifax Corp. v. District of Columbia have recognized that debarring a corporation from government contracting implicates a liberty interest triggering due process guarantees; the complaint argues the government cannot evade those guarantees simply by declining to call the exclusion "debarment."22

Count V applies 5 U.S.C. § 558(b) to the non-Department agencies - GSA, Treasury, the Federal Housing Finance Agency, State, and HHS - that terminated or restricted Anthropic's access following the Presidential Directive. Section 558(b) prohibits imposing a "sanction" or substantive order "except within jurisdiction delegated to the agency and as authorized by law," and the complaint argues that none of these agencies has independent statutory authority for blacklisting a specific commercial vendor in response to a presidential social-media post - they simply followed the Directive's lead without their own legal basis for doing so.

VI. What the Case Means for Speech-Conditioned Government Contracting

Anthropic is not the first Trump-administration target to frame retaliatory government action as a First Amendment violation; the complaint itself cites Perkins Coie LLP v. U.S. Department of Justice, in which a court held an executive order retaliating against a law firm unconstitutional because its text made "clear that President Trump and his administration disfavor the specific messages conveyed by plaintiff."23 What sets this case apart is the setting: a frontier AI developer that, by its own account, is the Department of War's most widely deployed model and the only frontier system authorized on its classified networks - a company the government simultaneously calls a national-security asset it "need[s] . . . now" and a sabotage risk requiring exclusion.24 That tension is the throughline of every count in the complaint, and it is likely to be the government's most difficult fact to explain away, however the legal theories ultimately fare.

Anthropic has been careful to frame its position as narrow rather than obstructionist. In Anthropic's public statement on the dispute, Amodei emphasized that the company continues to support the Department's "lawful foreign intelligence" work and partially autonomous weapons systems already fielded in Ukraine, and that its objection is limited to two applications - fully autonomous lethal targeting without human oversight, and mass domestic surveillance of Americans - that Anthropic says exceed what "today's technology can safely and reliably do." Whether that framing is legally sufficient to establish protected, non-obstructive speech, or whether a court instead treats Anthropic's refusal as an ordinary contract dispute dressed in constitutional language, will likely turn less on doctrine than on the factual record the parties develop: what, precisely, was said in the February 24 meeting, what alternatives were genuinely available to the Department, and whether the "supply chain risk" rationale can survive scrutiny once tested against the government's own six-month continued-use concession.

Conclusion

Anthropic v. Department of War compresses three distinct bodies of law - procurement and supply-chain-risk statutes, First Amendment retaliation doctrine, and the separation-of-powers limits on unilateral executive action - into a single dispute. For now, the complaint's more modest claim - that the government may not use procurement leverage and a repurposed supply-chain-risk statute to punish a contractor for maintaining safety restrictions it has publicly defended - is likely to be the terrain on which the case is actually decided.

Footnotes

  1. Complaint for Declaratory and Injunctive Relief ¶¶ 1, 11, 17,Anthropic PBC v. U.S. Dep't of War, No. 3:26-cv-01996-RFL (N.D. Cal. filed Mar. 9, 2026).
  2. Id. ¶¶ 3-5, 75-79.
  3. Id. ¶¶ 65-77.
  4. Id. ¶¶ 85-86 (quoting a senior Pentagon official's account, reported in Dave Lawler & Maria Curi,Exclusive: Hegseth gives Anthropic until Friday to back down on AI safeguards, Axios (Feb. 24, 2026)).
  5. Id. ¶ 87 (quoting Statement from Dario Amodei on our discussions with the Department of War, Anthropic (Feb. 26, 2026)).
  6. Id. ¶¶ 88-91 (Exhibit 1, Donald J. Trump (@realDonaldTrump), TruthSocial (Feb. 27, 2026, 12:47 PM PT); Exhibit 2, Secretary of War Pete Hegseth (@SecWar), X (Feb. 27, 2026, 2:14 PM PT)).
  7. Id. ¶¶ 104-06 (Exhibit 3, March 3, 2026 Letter).
  8. 10 U.S.C. § 3252(b)(2)(A), (d)(4)-(5); Complaint ¶ 121.
  9. 10 U.S.C. § 3252(b)(1), (b)(2)(A)-(B), (b)(3); Complaint ¶ 123.
  10. Complaint ¶ 122 (citing Exec. Order No. 13,873, 84 Fed. Reg. 22689 (May 15, 2019); 15 C.F.R. § 791.4(a)).
  11. Motor Vehicle Mfrs. Ass'n v. State Farm Mut. Auto. Ins. Co., 463 U.S. 29, 43 (1983); Complaint ¶¶ 125-28 (quoting Dist. Hosp. Partners, L.P. v. Burwell, 786 F.3d 46, 59 (D.C. Cir. 2015)).
  12. Nat'l Rifle Ass'n of Am. v. Vullo, 602 U.S. 175, 188 (2024);Nieves v. Bartlett, 587 U.S. 391, 398 (2019); Complaint ¶¶ 136-38 (quotingO'Brien v. Welty, 818 F.3d 920, 932 (9th Cir. 2016)).
  13. Complaint ¶¶ 140-45 (citing BE & K Constr. Co. v. NLRB, 536 U.S. 516, 525 (2002)).
  14. Complaint ¶¶ 6-8, 91 (quoting Exhibit 1 and Exhibit 2).
  15. McCullen v. Coakley, 573 U.S. 464, 478 (2014); Complaint ¶¶ 155-58 (citingVidal v. Elster, 602 U.S. 286, 293 (2024)).
  16. Youngstown Sheet & Tube Co. v. Sawyer, 343 U.S. 579, 585 (1952); Complaint ¶ 161.
  17. Complaint ¶¶ 164, 166 (quoting 48 C.F.R. § 9.402(b)).
  18. Complaint ¶ 166 (quotingAnti-Fascist Refugee Comm. v. McGrath, 341 U.S. 123, 143-44 (1951) (Black, J., concurring)).
  19. Complaint ¶¶ 171-72 (citingWisconsin v. Constantineau, 400 U.S. 433, 437 (1971);Ulrich v. City & Cnty. of San Francisco, 308 F.3d 968, 976 (9th Cir. 2002)).
  20. Trifax Corp. v. District of Columbia, 314 F.3d 641, 643-44 (D.C. Cir. 2003); Complaint ¶ 172.
  21. Perkins Coie LLP v. U.S. Dep't of Justice, 783 F. Supp. 3d 105 (D.D.C. 2025); Complaint ¶ 150.
  22. Complaint ¶¶ 68, 99-101, 125 (quoting an unnamed Department official, reported in Dave Lawler & Maria Curi,Exclusive: Hegseth gives Anthropic until Friday to back down on AI safeguards, Axios (Feb. 24, 2026)).