The Dawn Raid
Before dawn on January 3, Caracas was jolted awake by the sounds of war. Explosions rippled across the Venezuelan capital. Residents reported low-flying aircraft, smoke near key military and transport sites, and neighborhoods swallowed by darkness as power failed across large parts of the city. By morning, the Trump Administration was claiming an extraordinary prize: Nicolás Maduro and his wife, Cilia Flores, had been seized.
At 4 AM ET, President Donald Trump announced the raid and added a flourish: “It was dark, the lights of Caracas were largely turned off due to a certain expertise that we have, it was dark, and it was deadly.”1
Joint Chiefs of Staff General Dan Caine then offered a more precise account: “The word integration does not explain the sheer complexity of such a mission, an extraction so precise it involved more than 150 aircraft launching across the Western Hemisphere in close coordination, all coming together in time and place to layer effects for a single purpose, to get an interdiction force into downtown Caracas while maintaining the element of tactical surprise.”2
But the statements from Trump and Caine were specific enough that anyone at Anthropic paying attention would have had good reason to ask whether their technology had been part of the operation, and if so, how it had been used.
On January 9th, the Department of War (DoW) moved to secure this tech in a memo that directed “the Under Secretary of War for Acquisition and Sustainment to incorporate standard ‘any lawful use’ language into any DoW contract through which AI services are procured within 180 days.”3 That memo formally opened renegotiation with Anthropic. By February, negotiations had broken down. Then Secretary Pete Hegseth gave Anthropic an ultimatum. Accept our terms, or face contract cancellation, a supply chain risk designation, or compelled cooperation under the Defense Production Act.
Eventually Anthropic was labeled a supply chain risk. The event was unprecedented. It was the first American company ever slapped with that mark, which was meant to apply to foreign adversaries.
The Pentagon needs the best tools it can acquire to fight wars and keep Americans safe. That is especially true now, as artificial intelligence is integrated and foundational to defense systems in Iran. But assembling this history has made clear that the Department’s process had serious procedural and strategic failures, even if its underlying concerns were fundamentally legitimate.
To take just one example, the memo gave the DoW 180 days to renegotiate the contracts but Anthropic was designated a risk in merely 53 days. DoW leadership chided Anthropic for being woke, which is a valid criticism in some ways, but then got rid of testing and evaluation requirements that could have uncovered these biases. The timing only made the move look more contradictory. The day after the ultimatum, the Iran operation began, and it depended heavily on Anthropic’s technology. And now, the White House is trying to figure out ways to get Anthropic back into government.4
The Anthropic-DoW fight touches on many aspects of AI, but the account I have assembled focuses on three core tensions:
The DC–SF political divide — The Pentagon speaks in the language of command, law, sovereignty, and mission. Anthropic speaks in the language of alignment, evals, misuse, and technical uncertainty. Each side interprets the other’s vocabulary as bad faith. That cultural divide helps explain why the dispute became so emotionally charged.
State sovereignty over AI tech — The fight is not just about wokeness or contract fine print even though those things do matter. Instead, the Pentagon’s position is that lawful military use should be determined by the state, not by the internal values or usage policies of a private company. That’s a fine and reasonable first step. But the DoW cannot take a second step by retaliating against a company that refuses the new deal. It’s the second move that turns a procurement dispute into a deeper fight over sovereignty, authority, and the proper limits of private discretion in national security.
Paper authority versus state capacity — Vendor limits are not necessarily good in themselves, but stripping them away does not magically create government competence. The Pentagon treated contractual freedom as a substitute for technical understanding. It wanted broader rights with less testing and fewer constraints, all while rejecting the opportunity to build in-house expertise through joint R&D and evaluation. This feels like a self-inflicted wound. In the name of control, it passed up the chance to learn.