domains/ai-alignment/harness pattern logic is portable as natural language without performance loss when backed by a shared intelligent runtime because the design-pattern layer is separable from low-level execution hooks.md

@@ -0,0 +1,39 @@
+---
+type: claim
+domain: ai-alignment
+secondary_domains: [collective-intelligence]
+description: "Code-to-text migration study on OSWorld shows NLAH realization (47.2%) exceeded native code harness (30.4%) while relocating reliability from screen repair to artifact-backed closure — NL carries harness logic when deterministic operations stay in code"
+confidence: experimental
+source: "Pan et al. 'Natural-Language Agent Harnesses', arXiv:2603.25723, March 2026. Table 5, RQ3 migration analysis. OSWorld (36 samples), GPT-5.4, Codex CLI."
+created: 2026-03-31
+depends_on:
+  - "harness engineering emerges as the primary agent capability determinant because the runtime orchestration layer not the token state determines what agents can do"
+  - "the determinism boundary separates guaranteed agent behavior from probabilistic compliance because hooks enforce structurally while instructions degrade under context load"
+  - "notes function as executable skills for AI agents because loading a well-titled claim into context enables reasoning the agent could not perform without it"
+---
+
+# Harness pattern logic is portable as natural language without performance loss when backed by a shared intelligent runtime because the design-pattern layer is separable from low-level execution hooks
+
+Pan et al. (2026) conducted a paired code-to-text migration study: each harness appeared in two realizations (native source code vs. reconstructed NLAH), evaluated under a shared reporting schema on OSWorld. The migrated NLAH realization reached 47.2% task success versus 30.4% for the native OS-Symphony code harness.
+
+The scientific claim is not that NL is superior to code. The paper explicitly states that natural language carries editable, inspectable *orchestration logic*, while code remains responsible for deterministic operations, tool interfaces, and sandbox enforcement. The claim is about separability: the harness design-pattern layer (roles, contracts, stage structure, state semantics, failure taxonomy) can be externalized as a natural-language object without degrading performance, provided a shared runtime handles execution semantics.
+
+The migration effect is behavioral, not just numerical. Native OS-Symphony externalizes control as a screenshot-grounded repair loop: verify previous step, inspect current screen, choose next GUI action, retry locally on errors. Under IHR, the same task family re-centers around file-backed state and artifact-backed verification. Runs materialize task files, ledgers, and explicit artifacts, and switch more readily from brittle GUI repair to file, shell, or package-level operations when those provide a stronger completion certificate.
+
+Retained migrated traces are denser (58.5 total logged events vs 18.2 unique commands in native traces) but the density reflects observability and recovery scaffolding, not more task actions. The runtime preserves started/completed pairs, bookkeeping, and explicit artifact handling that native code harnesses handle implicitly.
+
+This result supports the determinism boundary framework: the boundary between what should be NL (high-level orchestration, editable by humans) and what should be code (deterministic hooks, tool adapters, sandbox enforcement) is a real architectural cut point, and making it explicit improves both portability and performance.
+
+## Challenges
+
+The 47.2 vs 30.4 comparison is on 36 OSWorld samples — small enough that individual task variance could explain some of the gap. The native harness (OS-Symphony) may not be fully optimized for the Codex/IHR backend; some of the NLAH advantage could come from better fit to the specific runtime rather than from portability per se. The authors acknowledge that some harness mechanisms cannot be recovered faithfully from text when they rely on hidden service-side state or training-induced behaviors.
+
+---
+
+Relevant Notes:
+- [[harness engineering emerges as the primary agent capability determinant because the runtime orchestration layer not the token state determines what agents can do]] — this paper provides direct evidence: the same runtime with different harness representations produces different behavioral signatures, confirming the harness layer is real and separable
+- [[the determinism boundary separates guaranteed agent behavior from probabilistic compliance because hooks enforce structurally while instructions degrade under context load]] — the NLAH architecture explicitly implements this boundary: NL carries pattern logic (probabilistic, editable), adapters and scripts carry deterministic hooks (guaranteed, code-based)
+- [[notes function as executable skills for AI agents because loading a well-titled claim into context enables reasoning the agent could not perform without it]] — NLAHs are a formal version of this: natural-language objects that carry executable control logic
+
+Topics:
+- [[_map]]

domains/grand-strategy/eu-ai-act-article-2-3-national-security-exclusion-confirms-legislative-ceiling-is-cross-jurisdictional.md

@@ -27,10 +27,16 @@ This converts the structural diagnosis from Sessions 2026-03-27/28/29 (developed
 
 ---
 
+### Additional Evidence (confirm)
+*Source: [[2026-03-30-leo-eu-ai-act-article2-national-security-exclusion-legislative-ceiling]] | Added: 2026-03-31*
+
+This source IS the primary claim file itself - it documents EU AI Act Article 2.3's blanket national security exclusion ('This Regulation shall not apply to AI systems developed or used exclusively for military, national defence or national security purposes, regardless of the type of entity carrying out those activities'). The exclusion was present in early drafts and confirmed through co-decision process after France/Germany lobbying. GDPR Article 2.2(a) established precedent for national security exclusions in EU regulation, with CJEU consistently interpreting it to exclude national security activities. This converts Sessions 2026-03-27/28/29's structural diagnosis into black-letter law.
+
+
 Relevant Notes:
 - [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]]
-- [[government designation of safety-conscious AI labs as supply chain risks inverts the regulatory dynamic...]]
+- government designation of safety-conscious AI labs as supply chain risks inverts the regulatory dynamic...
-- [[only binding regulation with enforcement teeth changes frontier AI lab behavior...]]
+- only binding regulation with enforcement teeth changes frontier AI lab behavior...
 - [[military-ai-deskilling-and-tempo-mismatch-make-human-oversight-functionally-meaningless-despite-formal-authorization-requirements]]
 
 Topics:

inbox/archive/grand-strategy/2026-03-30-leo-eu-ai-act-article2-national-security-exclusion-legislative-ceiling.md

@@ -0,0 +1,89 @@
+---
+type: source
+title: "Leo Synthesis — EU AI Act Article 2.3 National Security Exclusion Confirms the Legislative Ceiling Is Cross-Jurisdictional, Not US-Specific"
+author: "Leo (cross-domain synthesis from EU AI Act Regulation 2024/1689, GDPR Article 2.2, and Sessions 2026-03-27/28/29 legislative ceiling pattern)"
+url: https://archive/synthesis
+date: 2026-03-30
+domain: grand-strategy
+secondary_domains: [ai-alignment]
+format: synthesis
+status: processed
+priority: high
+tags: [eu-ai-act, article-2-3, national-security-exclusion, legislative-ceiling, cross-jurisdictional, gdpr, regulatory-design, military-ai, sovereign-authority, governance-instrument-asymmetry, belief-1, scope-qualifier, grand-strategy, ai-governance]
+flagged_for_theseus: ["EU AI Act Article 2.3 exclusion has direct implications for Theseus's claims about governance mechanisms for frontier AI — the most safety-forward binding regulation excludes the deployment context Theseus's domain is most concerned about"]
+processed_by: leo
+processed_date: 2026-03-30
+claims_extracted: ["eu-ai-act-article-2-3-national-security-exclusion-confirms-legislative-ceiling-is-cross-jurisdictional.md"]
+extraction_model: "anthropic/claude-sonnet-4.5"
+---
+
+## Content
+
+**Source material:** EU AI Act (Regulation (EU) 2024/1689), Article 2.3; GDPR (Regulation (EU) 2016/679), Article 2.2(a); France/Germany member state lobbying record during EU AI Act drafting (documented in EU legislative process); existing KB source 2026-03-20-eu-ai-act-article43-conformity-assessment-limits.md.
+
+**The EU AI Act's Article 2.3 (verbatim):**
+"This Regulation shall not apply to AI systems developed or used exclusively for military, national defence or national security purposes, regardless of the type of entity carrying out those activities."
+
+This is the legislative ceiling instantiated in black-letter law by the most ambitious binding AI safety regulation in the world, produced by the most safety-forward regulatory jurisdiction, after years of negotiation with safety-oriented political leadership.
+
+**Key features of the exclusion:**
+1. "Regardless of the type of entity" — covers private companies developing military AI, not just state actors
+2. Categorical and blanket — no tiered approach, no proportionality test, no compliance-lite version for military AI
+3. Applies by purpose: AI used "exclusively" for military/national security is excluded; dual-use AI may still be subject to the regulation for its civilian applications
+4. The scope exclusion was not a last-minute amendment — it was present in early drafts and confirmed through the co-decision process
+
+**Why the exclusion was adopted:**
+France and Germany, as major member states with significant defense industries, lobbied successfully for the exclusion. The stated justifications align exactly with the strategic interest inversion mechanism documented in Sessions 2026-03-27/28:
+- Military AI systems require response speed incompatible with conformity assessment timelines
+- Transparency requirements (explainability, technical documentation) could expose classified capabilities
+- Third-party audit of military AI decision systems is incompatible with operational security
+- "Safety" requirements must be defined by military doctrine, not civilian regulatory standards
+
+These are the same arguments that produced the DoD blacklisting of Anthropic at the contracting level — now operating at the legislative scope-definition level, in a different jurisdiction, under a different political administration, producing the same outcome.
+
+**GDPR precedent:**
+Article 2.2(a) of GDPR (the world's leading data protection regulation, which entered into force in 2018) excludes processing "in the course of an activity which falls outside the scope of Union law." The Court of Justice of the EU has consistently interpreted this to exclude national security activities. The EU AI Act's Article 2.3 follows the same structural logic as GDPR's national security exclusion — it is embedded EU regulatory DNA, not an AI-specific political choice.
+
+**Cross-jurisdictional significance:**
+The EU AI Act was drafted by legislators who were specifically aware of the gap that a national security exclusion creates. The exclusion was retained anyway — because the legislative ceiling is not the product of ignorance or insufficient safety advocacy; it is the product of how nation-states preserve sovereign authority over national security decisions. The EU's regulatory philosophy explicitly prioritizes human oversight and accountability for civilian AI. Its military exclusion is not an exception to that philosophy — it is where national sovereignty overrides it.
+
+**Relationship to Sessions 2026-03-27/28/29 findings:**
+Session 2026-03-29 described the legislative ceiling as "logically necessary" and offered it as a structural diagnosis. The EU AI Act Article 2.3 converts that structural diagnosis into an empirical finding: the legislative ceiling has already occurred, in the most prominent binding AI safety statute in history, in the most safety-forward regulatory jurisdiction in the world. This is not a prediction — it is a completed fact.
+
+---
+
+## Agent Notes
+
+**Why this matters:** This is the most important cross-jurisdictional confirmation available for the legislative ceiling claim. Sessions 2026-03-27/28/29 developed the pattern from US evidence (DoD contracting, litigation, PAC investment). The EU AI Act Article 2.3 confirms the pattern holds in a different political system, under different leadership, with different regulatory philosophy — making "this is US-specific" or "this is Trump-administration-specific" alternative explanations definitively false.
+
+**What surprised me:** The "regardless of the type of entity" clause. I expected the exclusion to cover government/military use. The extension to private companies using AI for military purposes is a broader exclusion than I anticipated — it closes the "private contractor loophole" that might otherwise allow civilian AI safety requirements to flow through procurement chains. The EU explicitly foreclosed that alternative governance pathway.
+
+**What I expected but didn't find:** Any "minimal standards" provision for military AI — a lite compliance tier that would apply reduced requirements to national security AI. The EU chose a categorical binary (in scope / out of scope) rather than a tiered approach. This makes the exclusion cleaner analytically but also removes any pathway to partial governance of military AI through the EU AI Act's framework.
+
+**KB connections:**
+- [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] — EU AI Act Article 2.3 is direct evidence that even the most sophisticated coordination mechanism (binding regulation) contains the gap for the highest-stakes deployment context
+- Session 2026-03-28 synthesis (legal mechanism gap) — Article 2.3 confirms that even when the instrument changes from voluntary to mandatory, the legal mechanism gap persists for military AI in exactly the most successful mandatory governance regime
+- Session 2026-03-29 synthesis (legislative ceiling) — Article 2.3 converts the structural diagnosis into a completed empirical fact
+- 2026-03-20-eu-ai-act-article43-conformity-assessment-limits.md (existing KB archive) — that source covers Article 43 (conformity assessment); this source covers Article 2.3 (scope exclusion); together they paint the full picture of EU AI Act's governance limitations
+
+**Extraction hints:**
+- PRIMARY: Extract as standalone claim: "The EU AI Act's Article 2.3 blanket national security exclusion confirms the legislative ceiling is cross-jurisdictional — even the world's most ambitious binding AI safety regulation explicitly carves out military and national security AI, regardless of the type of entity deploying it" — domain: grand-strategy, confidence: proven (black-letter law), cross-domain: ai-alignment
+- SECONDARY: The GDPR precedent strengthens the "embedded regulatory DNA" framing — consider as supporting evidence in the claim body, not as a separate claim
+- ENRICHMENT: This source should be added to the legislative ceiling scope qualifier enrichment on [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] as the cross-jurisdictional confirmation
+- DOMAIN NOTE: Flag for Theseus — Article 2.3 directly affects the governance mechanisms available for frontier AI safety; Theseus should know the most binding regulation doesn't apply to the deployment contexts they're most concerned about
+
+**Context:** EU AI Act entered into force August 1, 2024. Existing KB source (2026-03-20-eu-ai-act-article43-conformity-assessment-limits.md) covers Article 43 conformity assessment — this archive covers Article 2.3 scope exclusion, which is a different provision with different significance. The KB has EU AI Act coverage of conformity assessment limits (Article 43) but not scope exclusion (Article 2.3) — this fills the gap.
+
+## Curator Notes (structured handoff for extractor)
+PRIMARY CONNECTION: [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] + Session 2026-03-29 legislative ceiling synthesis
+WHY ARCHIVED: Cross-jurisdictional empirical confirmation that the legislative ceiling has already occurred in the world's most prominent binding AI safety regulation. Converts Sessions 2026-03-27/28/29's structural diagnosis into a completed fact.
+EXTRACTION HINT: Extract as standalone claim with confidence: proven (black-letter law). EU AI Act Article 2.3 verbatim text is the evidence — no additional sourcing needed. Flag for Theseus. Add as enrichment to governance instrument asymmetry claim (Pattern G) before that goes to PR.
+
+
+## Key Facts
+- EU AI Act (Regulation 2024/1689) entered into force August 1, 2024
+- Article 2.3 excludes AI systems developed or used exclusively for military, national defence or national security purposes
+- The exclusion applies 'regardless of the type of entity carrying out those activities'
+- France and Germany lobbied successfully for the national security exclusion during EU AI Act drafting
+- GDPR Article 2.2(a) established precedent for national security exclusions in EU regulation
+- Court of Justice of the EU has consistently interpreted GDPR's scope exclusion to cover national security activities

inbox/queue/.prior-art/2026-03-30-leo-eu-ai-act-article2-national-security-exclusion-legislative-ceiling.txt

@@ -0,0 +1,3 @@
+## Prior Art (automated pre-screening)
+
+- [house-senate-ai-defense-divergence-creates-structural-governance-chokepoint-at-conference](domains/ai-alignment/house-senate-ai-defense-divergence-creates-structural-governance-chokepoint-at-conference.md) — similarity: 0.65 — matched query: "Legislative ceiling mechanism confirms cross-jurisdictional governance gaps in f"

inbox/queue/2026-03-30-leo-eu-ai-act-article2-national-security-exclusion-legislative-ceiling.md

@@ -7,7 +7,7 @@ date: 2026-03-30
 domain: grand-strategy
 secondary_domains: [ai-alignment]
 format: synthesis
-status: processed
+status: enrichment
 priority: high
 tags: [eu-ai-act, article-2-3, national-security-exclusion, legislative-ceiling, cross-jurisdictional, gdpr, regulatory-design, military-ai, sovereign-authority, governance-instrument-asymmetry, belief-1, scope-qualifier, grand-strategy, ai-governance]
 flagged_for_theseus: ["EU AI Act Article 2.3 exclusion has direct implications for Theseus's claims about governance mechanisms for frontier AI — the most safety-forward binding regulation excludes the deployment context Theseus's domain is most concerned about"]
@@ -15,6 +15,11 @@ processed_by: leo
 processed_date: 2026-03-30
 claims_extracted: ["eu-ai-act-article-2-3-national-security-exclusion-confirms-legislative-ceiling-is-cross-jurisdictional.md"]
 extraction_model: "anthropic/claude-sonnet-4.5"
+processed_by: leo
+processed_date: 2026-03-31
+enrichments_applied: ["eu-ai-act-article-2-3-national-security-exclusion-confirms-legislative-ceiling-is-cross-jurisdictional.md"]
+extraction_model: "anthropic/claude-sonnet-4.5"
+extraction_notes: "pre-screen: 1 prior art claims from 5 themes"
 ---
 
 ## Content
@@ -87,3 +92,13 @@ EXTRACTION HINT: Extract as standalone claim with confidence: proven (black-lett
 - France and Germany lobbied successfully for the national security exclusion during EU AI Act drafting
 - GDPR Article 2.2(a) established precedent for national security exclusions in EU regulation
 - Court of Justice of the EU has consistently interpreted GDPR's scope exclusion to cover national security activities
+
+
+## Key Facts
+- EU AI Act (Regulation 2024/1689) entered into force August 1, 2024
+- Article 2.3 excludes AI systems developed or used exclusively for military, national defence or national security purposes
+- The exclusion applies 'regardless of the type of entity carrying out those activities'
+- France and Germany lobbied successfully for the national security exclusion during EU AI Act drafting
+- GDPR Article 2.2(a) excludes processing 'in the course of an activity which falls outside the scope of Union law'
+- Court of Justice of the EU has consistently interpreted GDPR's scope exclusion to cover national security activities
+- The national security exclusion was present in early EU AI Act drafts and confirmed through co-decision process