Every private citizen or corporation gets to do business (or not) with the military on their own terms. This is the difference between totalitarianism and a free country.

Anthropic’s position is also known as “having terms of service”.

To be clear the existing, signed ToS terms that Trump balked at were:

1. No mass surveillance of US civilians - illegal but we have all read the Snowden papers.

2. Fully unmanned kill chains on autonomous weapons - Anthropic have even stated they will support this eventually, they just didn’t think their models were ready and didn’t want the obvious, inevitable blowback.

The DoD is within its rights to cancel the contract if it doesn’t like the terms that it previously signed.

▲

andrewla 3 hours ago | parent [-]

The concern, I think, in its most generous terms, is that they can't buy Anthropic's service the way the could, say, a wrench, because Anthropic can decide at any point to disable the military's ability (even transitively, through other vendors) to use their models if they determined that they do not like what the military is doing with that or if it violates their interpretation of the terms of service.

This seems like a definitional supply chain risk.

▲

Firaxus 3 hours ago | parent | next [-]

By that expansive definition, any cloud software provider can do the same thing and so should also be a supply chain risk.

This whole fiasco is happening because the defense dept wanted to use anthropic models in a way not allowed in the existing contract. Anthropic stuck to the contract, and the def dept tried to be punitive about it.

If they can’t get what they want from the seller, fine go to a different seller, but the supply chain risk is just government overreach.

	▲	andrewla 2 hours ago \| parent [-]
		I think I mostly agree here -- any cloud provider or frankly SaaS system carries a similar risk. The question is whether they want to explicitly make that part of their terms of service, and in addition have made public statements about their willingness to apply those terms of service. AWS GovCloud I believe promises the opposite. They could still do it, in terms of the capability itself, but then they'd be subject to both civil, criminal, and possibly even military consequences. Whereas Anthropic would be shielded from those consequences by the terms of their agreement (presumably; I'm not up to speed on the specifics of their contractual demands. This is just based on the context from this article and the previous appeals case that ruled against the government).

▲

theptip an hour ago | parent | prev [-]

That is not the definition of a supply chain risk, this is:

> FASCSA definition (41 U.S.C. § 4713(k)(6)): "Supply chain risk" means the risk that any person may sabotage, maliciously introduce unwanted function, extract data, or otherwise manipulate the design, integrity, manufacturing, production, distribution, installation, operation, maintenance, disposition, or retirement of covered articles so as to surveil, deny, disrupt, or otherwise manipulate the function, use, or operation of the covered articles or information stored or transmitted on the covered articles.

This topic is a mind-killer, lots of uninformed opinion swamping the news, and it's hard to get actual signal on the technical questions at hand. (And, I think it's naive to believe that the government is actually concerned about the precise legal definitions; remember Hegseth decreed that no government sub-contractors would be allowed to transact with Anthropic, despite there being no legal basis for this?)

> Anthropic can decide at any point to disable the military's ability

If you're referring to the claims of a killswitch, Anthropic testified under oath that they don't have one. This has been thoroughly covered, e.g. https://www.axios.com/2026/04/22/anthropic-no-kill-switch-ai.... Anthropic provides the weights, they get run in DoD's secure enclave. There's no "phone home".

If you mean more generally, that DoD might breach a contract and then have that contract cancelled going forwards, then yes - this is literally how all SaaS contracts work. And it's very clearly not what the quoted text above refers to.

The way this works in a non-totalitarian country is, the government says "I want new terms and you won't give them to me; instead I will take my business elsewhere". And indeed this is what happened, DoD now has contracts with Google and OpenAI for equivalent capabilities.

Just to engage on your terms, with the actual concern you're raising; I would say rather than "FASCSA supply chain risk" a better way of thinking about it is "vendor lock-in". DoD absolutely should not rely on a single vendor for these kinds of capabilities. And most defense spending explicitly contemplates this already. This should be and has been solved through basic procurement practices.