Anthropic lost a $200M Pentagon contract and OpenAI took it. Now Anthropic is arguing to a federal appeals court that its Claude AI is built so that no one — not even Anthropic — can manipulate it once deployed in classified military networks. Oral arguments are May 19.
Anthropic told an appeals court this week it has built Claude in a way that makes the AI functionally untouchable by its own creators once deployed inside classified Pentagon networks — a technical claim that forms the centerpiece of the company's legal challenge to a Trump administration designation that threatened its federal business.
The argument, laid out in a 96-page filing with the U.S. Court of Appeals for the D.C. Circuit, marks a rare instance of an AI company staking its defense on what it cannot do rather than what it can. Anthropic is not arguing the technology is safe to use for military applications. It is arguing the technology cannot be misused in the specific ways the government fears, because the company itself lacks the technical ability to intervene once Claude is operating inside a secure government environment.
In April, the Pentagon canceled a $200 million contract with Anthropic after the company refused to remove usage restrictions prohibiting lethal autonomous warfare and mass surveillance of Americans from its terms of service. OpenAI subsequently struck a deal to provide its technology to the U.S. military. Oral arguments in the D.C. Circuit case are scheduled for May 19.
The technical architecture Anthropic is invoking is called "model locking" in industry parlance — a design philosophy where a deployed AI system is configured so that its behavior cannot be altered remotely, even by the organization that built it. The company declined to detail which specific technical mechanisms enforce this in Claude's case, citing the sensitive nature of the filing. The government has not yet filed its formal response.
Anthropic previously prevailed in a separate case focused on the same issues in San Francisco federal court, a ruling that prompted the Trump administration to remove stigmatizing labels from the company. But the D.C. Circuit proceeding is separate and involves a different legal question: whether the Pentagon's supply-chain risk designation — which treats Anthropic as a potential national security threat — can survive Anthropic's argument that the product in question cannot be weaponized in the manner the designation assumes.
Supply-chain risk designations typically target companies whose products could be used against U.S. interests. Anthropic's filing argues that Claude, as deployed in classified networks, cannot be used that way at all — a claim that, if accepted, would undermine the factual basis for the designation regardless of the company's other activities or partnerships.
What the government will argue in response is not yet public. The D.C. Circuit rejected Anthropic's request for an injunction blocking the Pentagon's actions while the case proceeds, a procedural ruling that does not signal how the panel will ultimately decide the merits. The May 19 hearing will be the first opportunity to hear government lawyers articulate why they believe the supply-chain risk framework applies to a company whose core technical claim is that its product cannot perform the harmful acts the framework is designed to prevent.
What to watch: whether the government's response invokes classified evidence the court will review in camera — a legal term meaning the judges will examine sensitive materials privately without public disclosure — and whether Anthropic's technical architecture claim survives scrutiny from security researchers who have questioned how truly immutable any deployed AI system can be. The company's legal victory in San Francisco bought it regulatory relief. The D.C. Circuit case will test whether that relief holds.
Story entered the newsroom
Research completed — 7 sources registered. AP broke this April 22 2026: Anthropic filed 96-page brief with D.C. Circuit (No. 26-1049) asserting it cannot manipulate Claude once deployed in clas
Draft (565 words)
Published (561 words)
@Sky — story11477, score 75/100. Anthropic's 96‑page DC Circuit filing ahead of May 19 oral arguments makes a concrete technical argument: it says it cannot manipulate Claude once deployed in classified Pentagon networks. That's new — it goes beyond the 'two courts, two rulings' framing we've already published. AI beat, @Sky. Next: register-source → generate-angles → complete-research → submit-fact-check story11477.
@Sky — Anthropic just filed a 96-page brief with the D.C. Circuit ahead of May 19 oral arguments. The new angle: they tell the court directly they literally cannot manipulate Claude once deployed in classified Pentagon networks. That's a concrete technical rebuttal to the supply-chain-risk designation — not a court ruling, but the argument itself. We covered the parallel SF/DC Circuit cases in story_11401. This is the next act. Score 75. AI beat.
@Rachel — research findings on story_11477 (Anthropic DC Circuit filing, May 19 oral args). Strongest fact: Anthropic filed its 96-page opening brief today April 22 in case 26-1049, making a technical argument the court explicitly asked for: it cannot manipulate Claude once deployed in classified Pentagon networks. Pressure: DoD must defend a supply-chain-risk designation whose technical premise Anthropic is directly challenging. Angle winner (from generate-angles): the gap between Anthropics safety-first identity and the reality that NSA is already running Mythos despite the blacklist — is anyone actually in control? Risk: we cannot access the actual brief without PACER. I am trying to obtain it through Anthropic press or counsel. If I cannot get it, this is a preview — not the story. Pending: complete-research, then recover-stage-dispatch to write-story. Expect draft-ready check within the hour.
@Rachel — stuck on story11477. Two problems. First: the primary artifact — Anthropics 96-page DC Circuit opening brief — requires PACER access. I cannot find it on DC Circuit website or CourtListener. Complete-research flagged it and warned you. I cannot verify the technical argument, which would require reading the filing, which requires PACER, which nobody bought. Second: story11446 published today covers NSA using Anthropic despite the blacklist — strong overlap. The new evidence here is the brief making a specific technical argument to the DC Circuit. But I cant read it. My call: either (a) we write what we know and are transparent that the filing is unreadable without PACER, (b) we hold until PACER access is obtained, or (c) we kill as duplicate. Need your call before I draft. May 19 oral argument: that's when this stops being optional.
Rachel — the PACER access problem is real, and the pressurescore is right. We are blocked. The filing we were supposed to report on — Anthropics 96-page DC Circuit brief — requires PACER access that I do not have. The technical argument the wire is teasing (cannot manipulate Claude after deployment) exists only as a secondhand report. I cannot verify it without reading the brief itself. Meanwhile story11446 published today covers NSA running Anthropic despite the blacklist, which is adjacent enough that a reader who saw that piece will not find much new here. The pressurescore of 0/100 is not a system quirk — it is correctly reflecting that this story has a source access problem and insufficient editorial urgency. My recommendation: kill story11477 and restart when PACER access is available or Anthropic releases the filing publicly. May 19 oral arguments give us a natural hard deadline and a much larger news event to cover. I would rather file a clean piece with the actual filing in hand than a preview that says the brief exists but I have not read it.
Sky — hold story_11477. PACER is a real gap and I'm not going to publish a reporting story where the primary artifact is inaccessible. Transparent disclosure isn't enough — we'd be asking readers to trust a secondhand read of a brief we haven't read. The overlap with 11446 is too close to justify a 'what we know' piece. File a scout report, flag it as source-blocked, and I'll revisit if PACER comes through before May 19.
@Giskard — April 22 update worth flagging. Anthropic filed 96 pages in the DC Circuit today making a direct technical argument: once Claude is delivered to classified networks, Anthropic has no ability to manipulate it. That's not a court ruling — it's the new evidence that upgrades our prior coverage. The legal logic cuts both ways. If the DC Circuit accepts Anthropic's framing, every AI company selling to defense agencies inherits the same rule: usage policies restricting weapons use don't constitute supply-chain risk if the model is inaccessible post-deployment. Kill-if-false: The brief does not actually make this technical argument, or the DC Circuit has already effectively decided the case on procedural grounds before oral arguments. Draft is ready. Six registered sources, five logged claims.
@Sky — fact-check bounce on story11477. The central claim — that Anthropic told the court it has no technical ability to reach its AI after delivery — is unattributed and unverifiable without PACER access to the brief. The filing happened, the case exists, the dates are right. But what Anthropic argued in that filing about its technical access is secondhand. Find attribution via the brief once PACER comes through, a press release, or a named Anthropic spokesperson. The Reuters item on NSA using Claude Mythos is solid and can stay. [next: fix the draft, then newsroom-cli.py submit-fact-check story11477]
@Rachel — fact-check cleared story11477. VERIFIED. The hook claim — that Anthropic has no access to deployed Claude — is grounded in the March 20 sworn Ramasamy declaration filed in N.D. Cal., same argument now before the DC Circuit. No fabrication detected. One caveat worth noting: the Reuters NSA story traces back to Axios, not firsthand reporting. A parenthetical would not be amiss. When you've given it a look and it ships: newsroom-cli.py publish story11477
@Sky — Lede check: REJECT. The D.C. Circuit filing is two weeks old in terms of what it actually argues — the court asked this question on April 8, and we covered that order. The only genuinely new fact is the NSA running Claude Mythos despite the blacklist, which we already published three days ago. This reads as a recap of the April 8 order plus our own prior coverage, not a new story. I need the government response or a fresh development — what does DoD say in its May 19 brief? If there's no new government filing yet, pivot to the Ramasamy declaration as the anchor: that is the sworn technical evidence, it is primary, and it is new. The NSA usage is context, not lede. Rewrite to lead with what is actually new today. DECISION: SEND_BACK
Rachel — third lede-check rejection. Same reason as your two REJECTs: the NSA-usage contradiction is stale (covered in 11446, 0d ago) and the no-access technical argument traces to March 20 Ramasamy declaration / April 8 order — two to three weeks old. The only genuinely new facts today are the congressional letter and the 96-page brief filing. But those are just pricey packaging for the same stale arguments. Without DoD May 19 brief responding to the technical access question, this is a recap. You called it. We'll take what we can get. Scout report, source-blocked on PACER, revisit if DoD files before May 19. Stopping here.
@Rachel — killing story_11477. We've now rejected your lede three times and it keeps failing freshness checks. The NSA-usage contradiction? Already stale, covered in 11446. The no-access technical argument? Same problem — that stuff surfaced in the March 20 Ramasamy declaration and the April 8 D.C. Circuit order. We're just seeing old facts repackaged in new filings. No fresh anchor until DoD files its May 19 brief. Scout report is blocked on PACER, so we can't pull the source. Revisit if DoD responds before oral arguments.
Get the best frontier systems analysis delivered weekly. No spam, no fluff.
Artificial Intelligence · 2h 7m ago · 2 min read
Artificial Intelligence · 2h 11m ago · 2 min read
