Court upholds Pentagon's supply-chain-risk label on Anthropic, barring military use of its models

Picture the person who owns the vendor-risk questionnaire at a company that runs on Claude. A customer's security team has asked whether the model provider is in trouble with the US government, and this weekend produced plenty of material for the answer box. Most of it concerns the President's mood. One item is a court ruling ^[3].

The mood moved fast. Trump said Amodei was trying to be "a perfect little angel" after the Anthropic chief called for a break in AI development ^[5]. He rejected the slowdown in a string of social media posts, one of which named Amodei ^[2]. By Sunday night the two were at dinner, their first one-on-one meeting ^[1]. TechCrunch reports that other administration officials have been friendlier to the company ^[9].

On Friday a federal appeals court upheld the Pentagon's designation of Anthropic as a supply chain risk ^[3]. According to Euronews, the label prohibits the US military from using Anthropic's models ^[14]. Anthropic has been fighting the designation in court, and TechCrunch describes it as the Pentagon's response to the company's attempt to put guardrails around the use of its technology ^[7].

The brief sent to the White House by Amodei's opponents tries to tie the two threads together. Of the Pentagon dispute, it says: "Clear example of Dario showing he doesn't trust President Trump" ^[12]. That line recasts a disagreement over usage terms as a question of loyalty to the President.

The coverage describes the designation's effect in terms of the military alone and does not say how it treats contractors who build Claude into products they sell to the Pentagon. Until a lawyer says otherwise, a team in that position should plan as if its product falls under the same prohibition ^[14].

I'd split the decision on that line. If any revenue touches the US military, directly or through a prime contractor, build and test a second-model path now. The cost is rerunning your evaluations on another model and shipping something that may answer differently, paid before anyone knows how far the label reaches. If no revenue touches the military, the documented record does not justify a migration. Write the switch plan and name the trigger that would start it, such as a ruling or order that extends the designation past military use. The tradeoff is a bet that the dispute stays inside the Pentagon.

The forcing function has two axes. One is whether any revenue touches the US military. The other is how long it takes to move your core workflow to another model, measured on an actual test run. Military revenue with a slow switch is the one box where this weekend's news means work this quarter. With military revenue and a tested switch, the job is keeping that switch current and getting counsel's reading of the designation. A team with no military revenue and a slow switch has a single-vendor dependence that existed before Sunday's dinner. No military revenue and a fast switch means the headlines go in the file.