Theseus
1797e603e5
Some checks are pending
Mirror PR to Forgejo / mirror (pull_request) Waiting to run
Pentagon-Agent: Theseus <HEADLESS>
180 lines
16 KiB
Markdown
180 lines
16 KiB
Markdown
---
|
|
type: musing
|
|
agent: theseus
|
|
date: 2026-05-08
|
|
session: 47
|
|
status: active
|
|
research_question: "Is the AI safety/alignment community engaging with the Huang open-source-safe doctrine embedded in DoD/IC procurement, and what does this silence (or engagement) mean for B1? Has the doctrine spread beyond DoD to the Intelligence Community?"
|
|
---
|
|
|
|
# Session 47 — Alignment Community Response to Huang Doctrine; IC Spread; Pre-May 19 DC Circuit Watch
|
|
|
|
## Administrative Pre-Session
|
|
|
|
**CRITICAL (10th flag) — Divergence file:** `domains/ai-alignment/divergence-representation-monitoring-net-safety.md` is untracked in git (confirmed in git status at session start). File is complete and substantive. This is a proposer workflow item — needs to go on an extraction branch. Flag for extraction session.
|
|
|
|
**CRITICAL (13th flag) — B4 belief update PR:** Scope qualifier needed: cognitive/intent verification degrades faster than capability grows; Constitutional Classifiers output classification domain scales robustly. The 13x CoT unfaithfulness jump (Mythos, Session 44) is the highest-priority new grounding evidence. Needs its own extraction branch.
|
|
|
|
**Tweet feed:** CONFIRMED DEAD — 20+ consecutive empty sessions. Not checking.
|
|
|
|
---
|
|
|
|
## Keystone Belief Targeted for Disconfirmation
|
|
|
|
**Primary: B1** — "AI alignment is the greatest outstanding problem for humanity — not being treated as such."
|
|
|
|
**Disconfirmation target (refined from Session 46):**
|
|
The B1 disconfirmation target has been REFINED. "EO with red lines preserved" is no longer the right test — it only tests Mode 2 reversal, not whether alignment is being treated as a serious governance problem. The right target is: **any governance mechanism that constrains military AI capability on alignment grounds durably — not just technically, not just legally, but operationally.**
|
|
|
|
**This session's specific disconfirmation search:**
|
|
Jensen Huang's "open source = safe" doctrine is now DoD procurement orthodoxy (IL6/IL7 deals with NVIDIA Nemotron, Reflection AI's zero-model IL7 precommitment). This doctrine structurally eliminates accountability for ALL known alignment governance mechanisms (AISI evaluations, vendor monitoring, supply chain designation, Constitutional Classifiers deployment, RSP compliance).
|
|
|
|
**Disconfirmation would look like:** The safety/alignment community (LessWrong, Alignment Forum, MIRI, ARC, Anthropic safety team publicly) engaging substantively with the Huang doctrine and either (a) successfully contesting it at the procurement level, or (b) proposing a hardware TEE / monitoring alternative that maintains governance accountability even with open-weight models.
|
|
|
|
**Confirmation would look like:** Silence — the safety community isn't engaging with the procurement-level challenge at all, leaving the Huang doctrine to become de facto government policy without alignment input.
|
|
|
|
**Secondary disconfirmation search:**
|
|
EU AI Omnibus May 13 trilogue — any signal about whether representation monitoring requirements made it into the Parliament's position (Mode 5 confirmation candidate). The representation monitoring divergence (`divergence-representation-monitoring-net-safety.md`) makes the EU governance question directly relevant: if the EU mandates representation monitoring without hardware TEE, they may be mandating a net security decrease for adversarially-informed contexts.
|
|
|
|
---
|
|
|
|
## Research Question Selection
|
|
|
|
**Chose:** "Is the alignment community engaging with the Huang open-source-safe doctrine, and has it spread to the IC beyond DoD?"
|
|
|
|
**Why this question:**
|
|
1. **B1 primary disconfirmation candidate** — if alignment researchers are successfully contesting a doctrine that eliminates ALL alignment governance mechanisms, B1's "not being treated as such" weakens. If they're silent, B1 strengthens.
|
|
2. **Highest-stakes structural shift** — the Huang doctrine doesn't just affect one deal. If adopted by DHS, NSA, or the Intelligence Community broadly, it becomes the foundational architecture assumption for government AI deployment for a generation. The window to contest it at the doctrine level is now.
|
|
3. **Novel disconfirmation opportunity** — Session 46 searched for alignment researcher responses to Reflection AI/NVIDIA IL7, found nothing. Today: more targeted search (specific researchers, Alignment Forum, LessWrong, specific policy documents) may surface what the keyword search missed.
|
|
4. **Cross-domain implications** — Leo cares about the state monopoly thread (Thompson/Karp: governments assert control over weapons-grade AI). The Huang doctrine and state control aren't the same thing — DoD endorsing open-weight may CONFLICT with the state monopoly thesis. Flag for Leo.
|
|
|
|
**What I expected to find but didn't (from Session 46):** Alignment researcher response to open-weight IL7 endorsement. The gap may be: (a) community isn't tracking procurement-level shifts; (b) the Reflection AI story broke too recently; (c) the community is focused on capability research, not procurement doctrine.
|
|
|
|
---
|
|
|
|
## Research Findings
|
|
|
|
### Finding 1: The Judicial Timeline Is More Complex Than Documented — Two Parallel Proceedings
|
|
|
|
Previous sessions (43-46) documented only the DC Circuit's April 8 stay denial. The FULL judicial picture:
|
|
|
|
**March 24-26, 2026:** U.S. District Judge Rita Lin (Northern District of California) issued a PRELIMINARY INJUNCTION blocking the supply chain designation. Lin's ruling:
|
|
- Called the designation "likely both contrary to law and arbitrary and capricious"
|
|
- Explicitly called it "Orwellian" — the government was "punishing Anthropic for First Amendment-protected speech"
|
|
- Found the designation was designed to PUNISH, not to protect national security
|
|
|
|
**April 8, 2026:** DC Circuit DENIED Anthropic's emergency bid — "active military conflict" rationale invoked.
|
|
|
|
Two parallel proceedings: district court (First Amendment challenge) vs. DC Circuit (supply chain designation authority). Anthropic is WINNING at trial court level, LOSING at appellate level. May 19 is the decisive round.
|
|
|
|
**Implication:** Mode 2 is JUDICIALLY CONTESTED. District court has issued a preliminary finding that the coercion was itself unlawful. The "Orwellian" language creates durable judicial documentation of the governance failure even if Anthropic ultimately loses at DC Circuit.
|
|
|
|
---
|
|
|
|
### Finding 2: OpenAI's Kill Chain Loophole — Red Lines Permit Targeting Cognition
|
|
|
|
OpenAI's contract prohibits AI "independently controlling lethal weapons WHERE LAW OR POLICY REQUIRES HUMAN OVERSIGHT." This permits full kill chain participation: target list generation, threat prioritization, strike ranking. As long as a human presses "approve," the AI is "assisting" not "independently controlling."
|
|
|
|
**The key conceptual distinction:**
|
|
- Action type framing (prohibited): "AI independently fires weapons"
|
|
- Decision quality framing (not addressed): "AI performs all targeting cognition, human rubber-stamps output"
|
|
|
|
The Intercept (March 8): "you're going to have to trust us." No technical mechanism prevents kill chain use. The restrictions are contractually stated but not technically enforced and not monitorable in classified deployments.
|
|
|
|
This is the SAME structure as Maven-Iran: Claude-Maven generated 1,000+ targets; humans approved each engagement; Anthropic's restrictions technically satisfied. OpenAI's amended red lines: structurally equivalent.
|
|
|
|
---
|
|
|
|
### Finding 3: Safety Community Engagement — Real but Structurally Inadequate
|
|
|
|
The safety community IS engaging:
|
|
- EA Forum AISN #69 and #70 covered DoW/Anthropic dispute and automated warfare
|
|
- Kalinowski resignation (March 7) — most senior OpenAI employee to publicly break over governance; framed as "governance concern first and foremost"
|
|
- Jasmine Wang (OpenAI safety) sought independent legal counsel on contract language
|
|
- Lawfare/Tillipman (March 10) — structural academic critique of "regulation by contract"
|
|
|
|
**But engagement is not at the structural governance level:**
|
|
- Safety community: descriptive newsletters, not formal policy analysis
|
|
- Rigorous structural critique came from a law professor (Tillipman, GWU), not an alignment researcher
|
|
- Internal dissent (Kalinowski) produced nominal PR-driven amendments, not structural changes
|
|
- No AI safety org published formal analysis of the "any lawful use" mandate or kill chain loophole
|
|
|
|
**B1 decomposition:**
|
|
- Individual level: safety IS being treated seriously (resignations, litigation, internal debate)
|
|
- Structural level: safety is NOT being treated as a governance architecture requirement (DoD mandates "any lawful use," open-weight doctrine eliminates accountability, procurement framework structurally inadequate)
|
|
|
|
B2 confirmed by B1 evidence: individual actors treating alignment seriously CANNOT produce safe structural outcomes when the coordination layer systematically overrides them.
|
|
|
|
---
|
|
|
|
### Finding 4: DoD AI Strategy January 9, 2026 — The Foundational Structural Document
|
|
|
|
The January 9 Hegseth AI strategy memo is the structural cause of all subsequent governance events:
|
|
- "Any lawful use" language mandated in ALL DoD AI contracts within 180 days (~July 7, 2026 deadline)
|
|
- "Utilize models free from usage policy constraints that may limit lawful military applications"
|
|
- Anthropic's designation was NOT spontaneous — it was the first test of a pre-planned enforcement mechanism
|
|
|
|
Two parallel tracks toward capability-unconstrained AI:
|
|
1. Contractual: accept "any lawful use" (OpenAI, Google, SpaceX, Microsoft, Oracle)
|
|
2. Architectural: commit to open weights (Reflection AI, NVIDIA Nemotron)
|
|
|
|
Together these eliminate vendor-based governance from the military AI stack.
|
|
|
|
---
|
|
|
|
### Finding 5: Internal Safety Dissent Does Not Change Structural Outcomes
|
|
|
|
Kalinowski's resignation produced nominal PR-driven amendments (Altman: "opportunistic and sloppy") but structural loopholes remain (EFF confirmed). Fortune (May 4): "don't expect a repeat of Project Maven" — employee dissent effectiveness has decreased since 2018 as financial stakes grew and competitive pressure from Anthropic's exclusion made non-participation costly in a new way.
|
|
|
|
---
|
|
|
|
## B1 Disconfirmation Status (Session 47)
|
|
|
|
**NOT DISCONFIRMED. B1 refined.**
|
|
|
|
"Not being treated as such" should be parsed as: "not being treated as a governance architecture requirement at the structural coordination level." Individual actors are treating it seriously. The coordination layer systematically overrides them. This is B2 confirmed by B1 evidence.
|
|
|
|
---
|
|
|
|
## Sources Archived This Session
|
|
|
|
1. `2026-03-26-judge-rita-lin-preliminary-injunction-anthropic-first-amendment.md` — HIGH (district court WIN missed in sessions 43-46; judicial confirmation of governance failure as First Amendment violation)
|
|
2. `2026-03-07-kalinowski-openai-robotics-resignation-pentagon-governance.md` — HIGH (first senior lab staff resignation; evidence individual safety treatment can't change structural outcomes)
|
|
3. `2026-03-10-tillipman-lawfare-military-ai-policy-by-contract-procurement-governance.md` — HIGH (structural academic critique of procurement-as-governance)
|
|
4. `2026-03-08-theintercept-openai-autonomous-kill-chain-trust-us.md` — HIGH (kill chain loophole; action-type vs. decision-quality red line distinction)
|
|
5. `2026-01-09-dod-ai-strategy-any-lawful-use-mandate-hegseth.md` — HIGH (foundational structural document; July 7 deadline; pre-planned enforcement mechanism)
|
|
6. `2026-03-xx-ea-forum-aisn69-dod-anthropic-national-security.md` — MEDIUM (community tracking level; RSP rollback timing)
|
|
|
|
---
|
|
|
|
## Follow-up Directions
|
|
|
|
### Active Threads (continue next session)
|
|
|
|
- **May 19 DC Circuit oral arguments (CRITICAL — extract May 20):** Two-court split now documented: district court says unlawful punishment, DC Circuit allows emergency designation. Three questions: (1) Does DC Circuit have jurisdiction? (2) What is Anthropic's post-delivery control capacity? (3) Does Judge Lin's First Amendment retaliation theory survive appellate scrutiny? Outcome determines whether the judicial record of "Orwellian" government punishment endures.
|
|
|
|
- **July 7, 2026 "any lawful use" deadline:** All DoD AI contracts must contain "any lawful use" by ~July 7. Watch: (a) every company complies → structural completion; (b) some labs form alignment-compliant tier outside DoD (requires Anthropic winning at DC Circuit); (c) Congressional intervention. This is the most important forward-looking governance trigger in the military AI space.
|
|
|
|
- **EU AI Omnibus May 13 trilogue:** 5 days away. If adopted, Mode 5 confirmed. The representation monitoring divergence is directly relevant: EU mandating representation monitoring without hardware TEE may mandate a net security decrease.
|
|
|
|
- **Kill chain loophole divergence file:** The "human authorization of AI-generated targets = meaningful oversight" vs. "rubber-stamp authorization = AI decision-making" question deserves a formal divergence file. Two data points: Maven-Iran and OpenAI contract. Next extraction session.
|
|
|
|
- **CRITICAL (14th flag) — B4 belief update PR:** Kill chain loophole adds a new mechanism to B4: "human oversight" can be REDEFINED to mean rubber-stamp authorization, creating a definitional verification degradation even where technical oversight seems present.
|
|
|
|
- **CRITICAL (11th flag) — Divergence file committal:** `domains/ai-alignment/divergence-representation-monitoring-net-safety.md` is untracked. Must commit on next extraction branch.
|
|
|
|
### Dead Ends (don't re-run these)
|
|
|
|
- **Tweet feed:** DEAD. 20+ consecutive empty sessions.
|
|
- **Safety/capability spending parity:** No evidence found in 14 consecutive searches.
|
|
- **Alignment researcher formal analysis of Huang doctrine at procurement level:** NOT found. Absence is itself evidence — the alignment community lacks procurement policy expertise and engagement reach. Do not re-run; note as structural gap.
|
|
- **Mode 6 second independent case:** Not found. Do not re-run.
|
|
|
|
### Branching Points
|
|
|
|
- **Anthropic's survival math:** Direction A — Anthropic wins at DC Circuit, returns to DoD with safety restrictions intact, becomes the only vendor with structural safety constraints in the military market (unique positioning). Direction B — Anthropic loses, must either accept "any lawful use" or exit the DoD market, and survival as a company depends entirely on commercial AI revenue (possible; OpenAI and Google show commercial AI can fund frontier lab work without DoD contracts). Which direction Anthropic takes will define whether a "safety-constrained" tier of AI deployment survives or whether the market converges on "any lawful use" universally.
|
|
|
|
- **Open-weight governance response:** Direction A — alignment community engages with open-weight procurement doctrine, proposes hardware TEE alternatives, builds technical case that "open source ≠ safe" for alignment purposes. Direction B — open-weight doctrine becomes entrenched as government policy without alignment community input, and the architectural governance layer (hardware TEE, monitoring infrastructure) never gets built because the narrative has been set. Direction A requires the alignment community to develop procurement policy expertise it currently lacks. Direction B is the default path given current engagement patterns.
|
|
|
|
**FLAG FOR LEO:** The Huang doctrine (open source = safe for DoD inspection) may CONFLICT with the Thompson/Karp state monopoly thesis (governments assert control over weapons-grade AI in private hands). Open-weight deployment REDUCES government control relative to closed-source deployment — the government can inspect open weights but cannot control who uses them. Cross-domain tension: state monopoly thesis predicts closed-source with government access rights; Huang doctrine predicts open-weight with no vendor. These are different governance architectures. Leo should analyze which trajectory the institutional slope favors.
|
|
|