Comment by satvikpendem
5 hours ago
I feel like in this thread no one is understanding what supply chain risk designation is. The government can just not use Anthropic, and that's exactly what they're doing, and they are not using it so much that they don't want Anthropic anywhere in their chain of supply. It's not necessarily punitive, the government is just covering their tracks so that if somewhere in their supply chain Anthropic exists, they want to remove them. They are complying with Anthropic's demands to not be used in war and the DoD says, okay, we won't use you anywhere and also enforce that we won't use you, just like you wanted.
Designating Anthropic a supply-chain risk means that no one in the federal government can use Anthropic's products for anything. Outside of the military, there are tons of places where Anthropic's products are a good fit for the needs of many other federal government agencies.
The DoD is perfectly free to say "no one in the DoD can use Anthropic products because we believe their products are not fit for our needs". That would 100% solve the problem.
Designating them a supply-chain risk is just political retribution for not caving to the DoD's contract negotiation demands. That's all. It's not necessary to ensure the integrity of the US military's goals and objectives. It's just punitive, elementary school grade bullying.
> They are complying with Anthropic's demands to not be used in war
There was no such demand from Anthropic. Why are you making things up?
EDIT: Honestly, the rest of your comment is even stranger. You're starting from a false premise, a strange belief about what the designation is meant for, but you do end up providing a wonderful demonstration of your opening sentence for yourself at least. You definitely don't know what you're talking about.
> It's not necessarily punitive, the government is just covering their tracks so that if somewhere in their supply chain Anthropic exists, they want to remove them.
This reminds me of an old comment here where some idiot claimed that suicide is illegal so police are allowed to stop people from killing themselves. No, if Anthropic doesn't want their systems involved in war (that's a thing you made up, again, just to be clear) then they do not need to be designated a supply chain risk to "protect them" or whatever drivel you come up with next.
The correct response from the DOD would be to terminate contracts with Anthropic, and that's it. Then Anthropic would be responsible for ensuring that any contracts with other parties keep them out of war (again, not a thing they said they want, just your fiction). This is how it works for all other software systems where people don't want their work involved in wars or used by the police or whatever.
Designating them a supply chain risk was punitive. Only fools think otherwise.
> I feel like in this thread no one is understanding what supply chain risk designation is.
I wouldn't say "no one" understands, but you certainly don't.
Again with the lack of understanding why it matters. The DoD does not want Anthropic anywhere near any system they'd use! Because it's, well, a risk to their supply chain if Anthropic were to somehow find out and then e.g. crash a rocket if the DoD was using a third party rocket provider that used Anthropic models. This is the correct response by the DoD, they simply do not want Anthropic in their supply chain. The DoD don't care what Anthropic comes up as reasoning, they want to maintain control of their systems without any (even potential) meddling.
And thus, every supplier of the DoD is prohibited from asking Claude to tweak the CSS on their website.
5 replies →
You failed to address my initial question.
Why did you make up false claims about Anthropic not wanting their systems to be used for war? They're clearly fine with it, but they wanted human-in-the-loop on decision making. They never asked to not have their systems used for war.
> Again with the lack of understanding why it matters.
It's cool that you were able to open this with at least one sentence containing some useful wisdom. A lack of understanding does, in fact, matter.
> The DoD does not want Anthropic anywhere near any system they'd use!
Nah, the DOD is punishing Anthropic for not agreeing to change the terms of the contract and allow them to use Anthropic's systems to determine, without a human-in-the-loop, who to kill or what to target and to use their systems for mass surveillance.
> Because it's, well, a risk to their supply chain if Anthropic were to somehow find out and then e.g. crash a rocket if the DoD was using a third party rocket provider that used Anthropic models.
What the fuck man. You went from (in your first comment) the DOD is helping Anthropic out by designating them a supply chain risk because it'll keep them out of war (again, a fiction, that isn't what the dispute was over), to now the DOD is worried that Anthropic might throw a tantrum and start crashing rockets if they find out.
Again, Anthropic does not mind their systems being used for war. They sold their systems to be used for war. They have specific, already existing (not changed later) contractual statements about how they can be used for war. That's it. That's the fucking dispute.
> This is the correct response by the DoD, they simply do not want Anthropic in their supply chain.
No. Just like Anthropic wanted (or were fine with) their systems being used to conduct war, the DOD actually does want Anthropic's systems in their supply chain. But they want it without restrictions. Stop making shit up.
> The DoD don't care what Anthropic comes up as reasoning, they want to maintain control of their systems without any (even potential) meddling.
Now this is a true sentence. The DOD does not care as long as they can access the systems without restrictions. I can't believe you wrote that sentence and the one before, though. They are entirely incompatible. It cannot be the case that DOD does not want Anthropic in their supply chain and that they do want it in their supply chain.
3 replies →
It's going to make things complicated w.r.t. software used anywhere within and by the DoD:
1. the linux kernel has patches created by and security vulnerabilities identified by Claude/Anthropic;
2. same with other software like SQLite and rsync.
Humans are 100% in the loop with software patches and there are many people in the chain so that provenance is maintained. It’s not that Claude could never look at the source code
Correct, anthropic's requirement was human-in-the-loop.
The DoD's response was to ban anthropic from all DoD facing activity and supply chains, whether or not there is a human in the loop. This does in fact run into exactly GP's issue. (or as I suggest elsewhere, can Boeing use Claude Code for software development?)
5 replies →
Anthropic said "we don't want to be used as part of kill chain decision-making" (actually it may have been even more specifically autonomous/unmanned kill chain decision making)
The DoD responded not by saying "alright, we will use OpenAI for our kill-chain uses" but by saying "Boeing is no longer allowed to use Claude Code".
Correct, they do not want “Boeing” to use Claude models to write software for airplanes for example
Yes, and this is not (and cannot be!) a supply chain risk in any reasonable interpretation.
6 replies →
No. They can do that with an order covering the specific parameters under which they care about it. Supply chain risk definition is about adversaries and sabotage, not companies dictating contract terms.
They don't want Anthropic to be able to sabotage any operations the DoD has. Anthropic already has a history of trying to sabotage others like during the Fable release when they said they'd subtly wreck your code if you were working on cutting edge AI.
Who said Anthropic will sabotage the DoD? Why are you taking the governments made up crap honestly?
1 reply →