\n<\/p>\n
Anthropic submitted two sworn declarations to a California federal court late Friday afternoon, pushing back on the Pentagon\u2019s assertion that the AI company poses an \u201cunacceptable risk to national security\u201d and arguing that the government\u2019s case relies on technical misunderstandings and claims that were never actually raised during the months of negotiations that preceded the dispute.<\/p>\n
The declarations were filed alongside Anthropic\u2019s reply brief in its lawsuit against the Department of Defense and come ahead of a hearing this coming Tuesday, March 24, before Judge Rita Lin in San Francisco.<\/p>\n
The dispute traces back to late February, when President Trump and Defense Secretary Pete Hegseth publicly declared they were cutting ties with Anthropic after the company refused to allow unrestricted military use of its AI technology.<\/p>\n
The two people who submitted the declarations are Sarah Heck, Anthropic\u2019s Head of Policy, and Thiyagu Ramasamy, the company\u2019s Head of Public Sector.<\/p>\n
Heck is a former National Security Council official who worked at the White House under the Obama administration before moving to Stripe and then Anthropic, where she runs the company\u2019s government relationships and policy work. She was personally present at the February 24 meeting where CEO Dario Amodei sat down with Defense Secretary Hegseth and the Pentagon\u2019s Under Secretary Emil Michael.<\/p>\n
In her declaration<\/a>, Heck calls out what she describes as a central falsehood in the government\u2019s filings: that Anthropic demanded some kind of approval role over military operations. That claim, she says, simply isn\u2019t true. \u201cAt no time during Anthropic\u2019s negotiations with the Department did I or any other Anthropic employee state that the company wanted that kind of role,\u201d she wrote.<\/p>\n She also claims that the Pentagon\u2019s concern about Anthropic potentially disabling or altering its technology mid-operation was never raised during negotiations. Instead, she says, it appeared for the first time in the government\u2019s court filings, which gave Anthropic no opportunity to respond.<\/p>\n Techcrunch event<\/p>\n \n\t\t\t\t\t\t\t\t\tSan Francisco, CA<\/span> Another detail in Heck\u2019s declaration sure to draw attention is that on March 4 \u2014 the day after the Pentagon formally finalized its supply-chain risk designation against Anthropic \u2014 Under Secretary Michael emailed Amodei to say the two sides were \u201cvery close\u201d on the two issues the government now cites as evidence that Anthropic is a national security threat: its positions on autonomous weapons and mass surveillance of Americans.<\/p>\n The email, which Heck attaches as an exhibit to her declaration, is worth reading alongside what Michael said publicly in the days afterward. On March 5, Amodei published a statement saying the company had been having \u201cproductive conversations<\/a>\u201d with the Pentagon. The day after that, Michael posted on X<\/a> that \u201cthere is no active Department of War negotiation with Anthropic.\u201d A week after that, he told CNBC there was \u201cno chance\u201d of renewed talks.<\/p>\n Heck\u2019s point appears to be: If Anthropic\u2019s stance on those two issues is what makes it a national security threat, why was the Pentagon\u2019s own official saying the two sides were nearly aligned on exactly those issues right after the designation was finalized? (She stops short of saying the government used the designation as a bargaining chip, but the timeline she lays out leaves the question hanging.)<\/p>\n Ramasamy brings a different kind of expertise to the case. Before joining Anthropic in 2025, he spent six years at Amazon Web Services managing AI deployments for government customers, including classified environments. At Anthropic, he\u2019s credited with building the team that brought its Claude models into national security and defense settings, including the $200 million contract<\/a> with the Pentagon announced last summer.<\/p>\n His declaration<\/a> takes on the government\u2019s claim that Anthropic could theoretically interfere with military operations by disabling the technology or otherwise altering how it behaves, which Ramasamy says isn\u2019t technically possible. Per his telling, once Claude is deployed inside a government-secured, \u201cair-gapped\u201d system operated by a third-party contractor, Anthropic has no access to it; there is no remote kill switch, no backdoor, and no mechanism to push unauthorized updates. Any kind of \u201coperational veto\u201d is a fiction, he suggests, explaining that a change to the model would require the Pentagon\u2019s explicit approval and action to install.<\/p>\n Anthropic, he says, can\u2019t even see what government users are typing into the system, let alone extract that data.<\/p>\n Ramasamy also disputes the government\u2019s claim that Anthropic\u2019s hiring of foreign nationals makes the company a security risk. He notes that Anthropic employees have undergone U.S. government security clearance vetting \u2014 the same background check process required for access to classified information \u2014 adding in his declaration that \u201cto my knowledge,\u201d Anthropic is the only AI company where cleared personnel actually built the AI models designed to run in classified environments.<\/p>\n Anthropic\u2019s lawsuit argues that the supply-chain risk designation \u2014 the first ever applied to an American company \u2014 amounts to government retaliation for the company\u2019s publicly stated views on AI safety, in violation of the First Amendment.<\/p>\n The government, in a 40-page filing earlier this week, rejected that framing entirely<\/a>, saying that Anthropic\u2019s refusal to allow all lawful military uses of its technology was a business decision, not protected speech, and that the designation was a straightforward national security call and not punishment for the company\u2019s views.<\/p>\n<\/div>\n
\n\t\t\t\t\t\t\t\t\t\t\t\t\t|<\/span>
\n\t\t\t\t\t\t\t\t\t\t\t\t\tOctober 13-15, 2026<\/span>\n\t\t\t\t\t\t\t<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/div>\n