diff --git a/domains/ai-alignment/ai-assisted-combat-targeting-creates-emergency-exception-governance-because-courts-invoke-equitable-deference-during-active-conflict.md b/domains/ai-alignment/ai-assisted-combat-targeting-creates-emergency-exception-governance-because-courts-invoke-equitable-deference-during-active-conflict.md
index f95aa5ac8..65663d9a1 100644
--- a/domains/ai-alignment/ai-assisted-combat-targeting-creates-emergency-exception-governance-because-courts-invoke-equitable-deference-during-active-conflict.md
+++ b/domains/ai-alignment/ai-assisted-combat-targeting-creates-emergency-exception-governance-because-courts-invoke-equitable-deference-during-active-conflict.md
@@ -31,3 +31,10 @@ The DC Circuit's third threshold question—'whether Anthropic can affect Claude
 **Source:** Mode 6 Emergency Exception: Second-Case Search (2026-05-07)
 
 Second-case search for Mode 6 emergency exception was negative. The Maduro capture operation (February 13, 2026) preceded the Iran war but was not characterized as an 'active military conflict' in the same legal register. No evidence found of judicial review being blocked on emergency grounds for the Maduro operation. The DC Circuit's April 8 stay denial citing 'active military conflict' in Iran remains the only documented case of emergency conditions suspending judicial AI governance mechanisms. The Maduro operation was a governance conflict trigger (leading to the Anthropic designation), not an independent emergency exception case. Historical precedent search found no prior cases of wartime emergency doctrine defeating judicial review of domestic technology company designation during active military conflict.
+
+
+## Extending Evidence
+
+**Source:** DC Circuit ruling (April 8), Washington Post (March 4), operational data on Claude-Maven targeting
+
+The supply chain designation was coordinated with the start of Iran operations to make the 'active military conflict' judicial rationale immediately available. Designation occurred February 27, Iran strikes began February 28, and DC Circuit denied stay on April 8 citing 'active military conflict' as justification for equitable deference to executive authority. The Iran war whose targeting Claude helped enable (generating ~1,000 prioritized targets in first 24 hours, 11,000+ total US strikes) was the stated rationale for judicial deference—the same war enabled by the designation that was designed to punish Anthropic's safety constraints. This reveals emergency exceptionalism as a coordinated governance strategy, not an organic judicial response.
diff --git a/domains/ai-alignment/ai-company-ethical-restrictions-are-contractually-penetrable-through-multi-tier-deployment-chains.md b/domains/ai-alignment/ai-company-ethical-restrictions-are-contractually-penetrable-through-multi-tier-deployment-chains.md
index de6df4b66..935ebafcd 100644
--- a/domains/ai-alignment/ai-company-ethical-restrictions-are-contractually-penetrable-through-multi-tier-deployment-chains.md
+++ b/domains/ai-alignment/ai-company-ethical-restrictions-are-contractually-penetrable-through-multi-tier-deployment-chains.md
@@ -11,9 +11,16 @@ sourced_from: ai-alignment/2026-05-06-iran-war-claude-maven-targeting-dc-circuit
 scope: structural
 sourcer: "Hunton & Williams, Arms Control Association"
 supports: ["access-restriction-governance-fails-through-supply-chain-coordination-gaps", "only binding regulation with enforcement teeth changes frontier AI lab behavior because every voluntary commitment has been eroded abandoned or made conditional on competitor behavior when commercially inconvenient"]
-related: ["voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints", "access-restriction-governance-fails-through-supply-chain-coordination-gaps", "only binding regulation with enforcement teeth changes frontier AI lab behavior because every voluntary commitment has been eroded abandoned or made conditional on competitor behavior when commercially inconvenient"]
+related: ["voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints", "access-restriction-governance-fails-through-supply-chain-coordination-gaps", "only binding regulation with enforcement teeth changes frontier AI lab behavior because every voluntary commitment has been eroded abandoned or made conditional on competitor behavior when commercially inconvenient", "ai-company-ethical-restrictions-are-contractually-penetrable-through-multi-tier-deployment-chains"]
 ---
 
 # AI company ethical restrictions are contractually penetrable through multi-tier deployment chains because Anthropic's autonomous weapons restrictions did not prevent Claude's use in combat targeting via Palantir's separate contract
 
 Claude is being used for AI-assisted combat targeting in the Iran war via Palantir's Maven integration, generating target lists and ranking them by strategic importance, while Anthropic simultaneously argues in court that it should be allowed to restrict autonomous weapons use. Hunton & Williams notes that 'Claude remains on classified networks via Palantir's existing contract (Palantir is not designated a supply chain risk). The supply chain designation targets direct Anthropic contracts, not Palantir reselling Claude.' This reveals a structural loophole: Anthropic's ethical restrictions on autonomous weapons use do not apply when Claude is deployed through Palantir's separate government contract. The multi-tier deployment chain—Anthropic to Palantir to DoD Maven—means voluntary safety commitments are contractually penetrable. Anthropic's restrictions bind only its direct contracts, not downstream use by intermediaries. This is not a technical failure but an architectural one: voluntary ethical constraints cannot survive multi-party deployment chains where each tier operates under separate agreements. The most consequential use case (combat targeting) occurs through the exact channel that Anthropic's restrictions do not cover. This demonstrates that AI company safety pledges are structurally insufficient when deployment architectures involve intermediary contractors with independent government relationships.
+
+
+## Supporting Evidence
+
+**Source:** Multiple sources documenting Maduro operation (Feb 13) and Iran targeting (Feb 28+)
+
+The Palantir loophole was confirmed in both Venezuela (Maduro capture) and Iran operations. Anthropic's restrictions applied to its direct contracts, not to Palantir's separate DoD contract. Claude operating inside Maven was not bound by Anthropic's end-user restrictions because Palantir (not the DoD) was Anthropic's customer. This enabled use in two active conflict contexts (Venezuela and Iran) despite Anthropic's stated restrictions on autonomous weapons and mass surveillance. Anthropic's public posture is that their restrictions apply to direct contracts, and Palantir's contract is Palantir's responsibility—consistent with private objection but no public statement to avoid worsening DoD relationship.
diff --git a/domains/ai-alignment/anthropic-supply-chain-designation-followed-maduro-operation-revealing-retroactive-penalization-mechanism.md b/domains/ai-alignment/anthropic-supply-chain-designation-followed-maduro-operation-revealing-retroactive-penalization-mechanism.md
new file mode 100644
index 000000000..9ca3b6b8c
--- /dev/null
+++ b/domains/ai-alignment/anthropic-supply-chain-designation-followed-maduro-operation-revealing-retroactive-penalization-mechanism.md
@@ -0,0 +1,19 @@
+---
+type: claim
+domain: ai-alignment
+description: The February 13 Maduro operation preceded the February 27 designation by two weeks, establishing that the designation was triggered by Anthropic's refusal to remove guardrails post-deployment, not by security concerns about the technology itself
+confidence: likely
+source: "Multiple sources: Axios, WSJ/Jpost, Fox News, Small Wars Journal, NBC News, Washington Post (Feb 13-Mar 4, 2026)"
+created: 2026-05-07
+title: The Anthropic supply chain designation followed the Maduro capture operation in which Claude-Maven was used, revealing the designation as a retroactive coercive instrument to compel removal of alignment constraints rather than a prospective security enforcement measure
+agent: theseus
+sourced_from: ai-alignment/2026-05-07-claude-maven-maduro-iran-designation-sequence.md
+scope: causal
+sourcer: "Multiple sources: Axios, WSJ/Jpost, Fox News, Small Wars Journal, NBC News, Washington Post"
+supports: ["government designation of safety-conscious AI labs as supply chain risks inverts the regulatory dynamic by penalizing safety constraints rather than enforcing them", "coercive-ai-governance-instruments-self-negate-at-operational-timescale-when-governing-strategically-indispensable-capabilities", "ai-assisted-combat-targeting-creates-emergency-exception-governance-because-courts-invoke-equitable-deference-during-active-conflict"]
+related: ["government designation of safety-conscious AI labs as supply chain risks inverts the regulatory dynamic by penalizing safety constraints rather than enforcing them", "voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints", "coercive-ai-governance-instruments-self-negate-at-operational-timescale-when-governing-strategically-indispensable-capabilities"]
+---
+
+# The Anthropic supply chain designation followed the Maduro capture operation in which Claude-Maven was used, revealing the designation as a retroactive coercive instrument to compel removal of alignment constraints rather than a prospective security enforcement measure
+
+The chronological sequence establishes a causal chain that inverts the expected security-enforcement narrative. On February 13, 2026, Claude-Maven was used in the operation to capture Venezuelan dictator Nicolás Maduro (Axios: 'Pentagon used Anthropic's Claude during Maduro raid'). In late February, tensions peaked between the Pentagon and Anthropic over two specific restrictions: no mass domestic surveillance and no fully autonomous lethal weapons without human oversight (NBC News: 'Tensions between the Pentagon and AI giant Anthropic reach a boiling point'). On February 27—two weeks after the Maduro operation—Trump issued an EO designating Anthropic as a 'supply chain risk' to national security, ordering all federal agencies and defense contractors to cease using Anthropic products. The very next day, February 28, Iran strikes began, with Claude-Maven generating ~1,000 prioritized targets in the first 24 hours under Palantir's existing contract. The designation was not issued before operational use to prevent deployment—it was issued after successful operational use, when Anthropic refused to remove its contractual guardrails. The one-day timing between designation (Feb 27) and Iran strikes (Feb 28) was coordinated to make the 'active military conflict' judicial rationale immediately available, as confirmed when the DC Circuit cited 'active military conflict' as justification for equitable deference on April 8. This sequence reveals the designation as a negotiating pressure tool deployed retroactively to punish safety constraints, not a prospective security enforcement action.
diff --git a/domains/ai-alignment/government designation of safety-conscious AI labs as supply chain risks inverts the regulatory dynamic by penalizing safety constraints rather than enforcing them.md b/domains/ai-alignment/government designation of safety-conscious AI labs as supply chain risks inverts the regulatory dynamic by penalizing safety constraints rather than enforcing them.md
index 9c7689e61..344e5a8f0 100644
--- a/domains/ai-alignment/government designation of safety-conscious AI labs as supply chain risks inverts the regulatory dynamic by penalizing safety constraints rather than enforcing them.md	
+++ b/domains/ai-alignment/government designation of safety-conscious AI labs as supply chain risks inverts the regulatory dynamic by penalizing safety constraints rather than enforcing them.md	
@@ -73,3 +73,10 @@ Lawfare legal analysis provides four independent legal failure modes (statutory
 **Source:** DC Circuit stay denial, April 8, 2026
 
 The DC Circuit's April 2026 stay denial explicitly invoked 'active military conflict' to justify denying judicial oversight of the supply chain designation, stating that judicial management of AI procurement during wartime would harm operations. This extends the inversion to wartime level: the same AI (Claude) is simultaneously designated a supply chain risk barring direct federal use AND being used in active combat targeting via Palantir Maven, with courts citing it as 'vital AI technology' requiring executive control. The regulatory inversion now operates with judicial deference during active conflict.
+
+
+## Extending Evidence
+
+**Source:** Multiple sources: Axios (Feb 13), NBC News (late Feb), Trump EO (Feb 27), Washington Post (Mar 4)
+
+The Maduro-to-Iran chronological sequence provides the causal mechanism: Claude-Maven was used in the Maduro capture operation on February 13, tensions peaked over Anthropic's two restrictions (no mass domestic surveillance, no fully autonomous lethal weapons without human oversight) in late February, the supply chain designation was issued February 27, and Iran strikes began February 28. The designation was specifically timed and triggered by the Maduro operation—deployed AFTER successful operational use, BECAUSE of Anthropic's refusal to remove contractual guardrails post-hoc. The one-day gap between designation and Iran strikes was coordinated to make the 'active military conflict' judicial rationale immediately available, as confirmed when DC Circuit cited this on April 8.
diff --git a/domains/ai-alignment/voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints.md b/domains/ai-alignment/voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints.md
index f9f2fa15f..a48ee9fbd 100644
--- a/domains/ai-alignment/voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints.md	
+++ b/domains/ai-alignment/voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints.md	
@@ -108,3 +108,10 @@ MAIM deterrence addresses the competitive pressure problem by changing the payof
 **Source:** Hunton & Williams, April 2026; Arms Control Association, May 2026
 
 Anthropic's autonomous weapons restrictions failed to prevent Claude's use in combat targeting in the Iran war because deployment occurred through Palantir's separate Maven contract. The multi-tier deployment chain (Anthropic → Palantir → DoD) means voluntary commitments are contractually penetrable—Anthropic's restrictions bind only direct contracts, not downstream use by intermediaries. This demonstrates voluntary pledges fail not just through competitive pressure but through contractual architecture where intermediary contractors bypass direct restrictions.
+
+
+## Extending Evidence
+
+**Source:** Dario Amodei public statement, Trump EO (Feb 27), NBC News reporting on Pentagon-Anthropic tensions
+
+The Anthropic case demonstrates that alignment constraints are punished not just by competitive market pressure but by government coercive instruments. Dario Amodei's two firm lines—no autonomous weapons without human oversight, no mass domestic surveillance of Americans—were met with supply chain designation after Claude-Maven was successfully used in the Maduro operation. The punishment was not market-based (competitors gaining advantage) but state-based (designation as supply chain risk, federal procurement ban). This extends the mechanism from competitive dynamics to include state coercion as a structural force against safety constraints.
diff --git a/inbox/queue/2026-05-07-claude-maven-maduro-iran-designation-sequence.md b/inbox/archive/ai-alignment/2026-05-07-claude-maven-maduro-iran-designation-sequence.md
similarity index 98%
rename from inbox/queue/2026-05-07-claude-maven-maduro-iran-designation-sequence.md
rename to inbox/archive/ai-alignment/2026-05-07-claude-maven-maduro-iran-designation-sequence.md
index f84a3626d..9462e9722 100644
--- a/inbox/queue/2026-05-07-claude-maven-maduro-iran-designation-sequence.md
+++ b/inbox/archive/ai-alignment/2026-05-07-claude-maven-maduro-iran-designation-sequence.md
@@ -7,10 +7,13 @@ date: 2026-02-13
 domain: ai-alignment
 secondary_domains: [grand-strategy]
 format: thread
-status: unprocessed
+status: processed
+processed_by: theseus
+processed_date: 2026-05-07
 priority: high
 tags: [governance-failure, mode-2, maven, iran-war, venezuela, maduro, supply-chain-designation, alignment-tax, b1, b2]
 intake_tier: research-task
+extraction_model: "anthropic/claude-sonnet-4.5"
 ---
 
 ## Content