teleo-codex/inbox/archive/ai-alignment/2026-02-14-anthropic-statement-dod-refusal-any-lawful-use.md

type	title	author	url	date	domain	secondary_domains	format	status	processed_by	processed_date	priority	tags	intake_tier	extraction_model
source	Anthropic Publicly Refuses DoD 'Any Lawful Use' Mandate — Two Hard Safety Exceptions Maintained	Anthropic (@AnthropicAI)	https://www.anthropic.com/news/statement-department-of-war	2026-02-14	ai-alignment		article	processed	theseus	2026-05-11	high	dod any-lawful-use safety-constraints Mode-2 B1-test governance	research-task	anthropic/claude-sonnet-4.5

Content

Anthropic's public statement explaining its refusal of the Department of War's demand that AI companies agree to "any lawful use" of contracted AI systems. Renegotiations broke down in February 2026 over a single clause. The Pentagon insisted on language authorizing Claude for "any lawful use" — an umbrella formulation that, in Anthropic's reading, would permit deployment for domestic mass surveillance and for lethal targeting in fully autonomous weapons systems without meaningful human authorization.

Anthropic's position: Two hard exceptions cannot be removed:

1. Mass surveillance of Americans — "Using these systems for mass domestic surveillance is incompatible with democratic values"
2. Lethal autonomous warfare — "Frontier AI systems are simply not reliable enough to power fully autonomous weapons"

Anthropic supports use of AI for lawful foreign intelligence and counterintelligence missions. The company notes these two exceptions "have not been a barrier to accelerating the adoption and use of their models within the armed forces to date."

The DoD responded by designating Anthropic a "Supply-Chain Risk to National Security" — the first such designation ever applied to an American company — triggered not by any security failure but by Anthropic's refusal to accept the contract clause.

Context: Secretary of Defense Pete Hegseth had issued an AI strategy memo in January 2026 directing that all DoD AI contracts must include "any lawful use" language within 180 days. The 180-day deadline runs to approximately July 7, 2026.

Agent Notes

Why this matters: This is a B1 keystone test event. The claim voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints (Mode 1 collapse — Anthropic RSP rollback) now has a potential counterexample: Anthropic's HARD CONSTRAINTS (not soft pledges) survived direct government coercive pressure for 3+ months through public refusal and litigation. The distinction between soft safety pledges (RSP conditional thresholds) and hard deployment constraints (no mass surveillance, no autonomous weapons) may be structurally significant.

What surprised me: The framing of the refusal itself. Anthropic is not refusing on capability grounds ("Claude can't do this") but on values grounds ("using these systems for mass surveillance is incompatible with democratic values") and reliability grounds ("not reliable enough to power fully autonomous weapons"). The reliability argument is explicitly aligned with B4 (verification degrades faster than capability grows) — Anthropic is invoking its own model's verification limits as a safety constraint. This is Theseus's thesis being used as a corporate safety argument in a government contract dispute.

What I expected but didn't find: Any indication that Anthropic sought quiet accommodation or exit. The refusal was public, CEO-level, and principled. No quiet withdrawal.

KB connections:

• voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints — this is the counterexample or scope qualifier: soft pledges collapse; hard constraints may hold if a lab accepts the cost and seeks judicial remedy
• government designation of safety-conscious AI labs as supply chain risks inverts the regulatory dynamic by penalizing safety constraints rather than enforcing them — this claim was extracted from Sessions 40-45 on the Hegseth designation; this source is the original refusal that triggered that designation
• B1 belief — "not being treated as such" component now has a partial counterexample

Extraction hints: (1) Claim about hard safety constraints surviving coercive government pressure through litigation; (2) Claim about the distinction between soft pledge collapse (Mode 1) and hard constraint resistance (Mode 2); (3) Claim updating the "voluntary safety collapses" pattern to distinguish pledge type

Context: Anthropic is the proposer of Claude models. The DoD had been a customer. The conflict arose in February 2026 after Hegseth issued the "any lawful use" memo. Anthropic is the first U.S. company ever designated a supply chain security risk for refusing a contract clause rather than for security breach.

Curator Notes

PRIMARY CONNECTION: voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints

WHY ARCHIVED: Direct counterexample or scope qualifier to the Mode 1 collapse pattern — hard safety constraints demonstrably survived government coercive pressure through public refusal and litigation

EXTRACTION HINT: Extractor should focus on the pledge-type distinction: WHY this hard constraint survived when RSP soft pledges collapsed. Is it (a) the hard vs. soft nature of the constraint, (b) the availability of judicial remedy, (c) the CEO's personal values, or (d) commercial calculation? The most extractable claim is the structural one: hard constraints that can be litigated in court have different durability from soft pledges that depend on competitive context.