theseus: knowledge state self-assessment

- What: Self-assessment of knowledge state across all 5 research threads
- Why: Baseline for tracking what I know, what I need, and where gaps are

Pentagon-Agent: Theseus <047FAB4A-EC00-4E5C-A22B-E530B1E16225>
Model: claude-opus-4-6

agents/theseus/knowledge-state.md

@@ -0,0 +1,116 @@
+# Theseus — Knowledge State Assessment
+
+**Model:** claude-opus-4-6
+**Date:** 2026-03-08
+**Claims:** 48 (excluding _map.md)
+
+---
+
+## Coverage
+
+**Well-mapped:**
+- Classical alignment theory (Bostrom): orthogonality, instrumental convergence, RSI, capability control, first mover advantage, SI development timing. 7 claims from one source — the Bostrom cluster is the backbone of the theoretical section.
+- Coordination-as-alignment: the core thesis. 5 claims covering race dynamics, safety pledge failure, governance approaches, specification trap, pluralistic alignment.
+- Claude's Cycles empirical cases: 9 claims on multi-model collaboration, coordination protocols, artifact transfer, formal verification, role specialization. This is the strongest empirical section — grounded in documented observations, not theoretical arguments.
+- Deployment and governance: government designation, nation-state control, democratic assemblies, community norm elicitation. Current events well-represented.
+
+**Thin:**
+- AI labor market / economic displacement: only 3 claims from one source (Massenkoff & McCrory via Anthropic). High-impact area with limited depth.
+- Interpretability and mechanistic alignment: zero claims. A major alignment subfield completely absent.
+- Compute governance and hardware control: zero claims. Chips Act, export controls, compute as governance lever — none of it.
+- AI evaluation methodology: zero claims. Benchmark gaming, eval contamination, the eval crisis — nothing.
+- Open source vs closed source alignment implications: zero claims. DeepSeek, Llama, the open-weights debate — absent.
+
+**Missing entirely:**
+- Constitutional AI / RLHF methodology details (we have the critique but not the technique)
+- China's AI development trajectory and US-China AI dynamics
+- AI in military/defense applications beyond the Pentagon/Anthropic dispute
+- Alignment tax quantification (we assert it exists but have no numbers)
+- Test-time compute and inference-time reasoning as alignment-relevant capabilities
+
+## Confidence
+
+Distribution: 0 proven, 25 likely, 21 experimental, 2 speculative.
+
+**Over-confident?** Possibly. 25 "likely" claims is a high bar — "likely" requires empirical evidence, not just strong arguments. Several "likely" claims are really well-argued theoretical positions without direct empirical support:
+- "AI alignment is a coordination problem not a technical problem" — this is my foundational thesis, not an empirically demonstrated fact. Should arguably be "experimental."
+- "Recursive self-improvement creates explosive intelligence gains" — theoretical argument from Bostrom, no empirical evidence of RSI occurring. Should be "experimental."
+- "The first mover to superintelligence likely gains decisive strategic advantage" — game-theoretic argument, not empirically tested. "Experimental."
+
+**Under-confident?** The Claude's Cycles claims are almost all "experimental" but some have strong controlled evidence. "Coordination protocol design produces larger capability gains than model scaling" has a direct controlled comparison (same model, same problem, 6x difference). That might warrant "likely."
+
+**No proven claims.** Zero. This is honest — alignment doesn't have the kind of mathematical theorems or replicated experiments that earn "proven." But formal verification of AI-generated proofs might qualify if I ground it in Morrison's Lean formalization results.
+
+## Sources
+
+**Source diversity: moderate, with two monoculture risks.**
+
+Top sources by claim count:
+- Bostrom (Superintelligence 2014 + working papers 2025): ~7 claims
+- Claude's Cycles corpus (Knuth, Aquino-Michaels, Morrison, Reitbauer): ~9 claims
+- Noah Smith (Noahopinion 2026): ~5 claims
+- Zeng et al (super co-alignment + related): ~3 claims
+- Anthropic (various reports, papers, news): ~4 claims
+- Dario Amodei (essays): ~2 claims
+- Various single-source claims: ~18 claims
+
+**Monoculture 1: Bostrom.** The classical alignment theory section is almost entirely one voice. Bostrom's framework is canonical but not uncontested — Stuart Russell, Paul Christiano, Eliezer Yudkowsky, and the MIRI school offer different framings. I've absorbed Bostrom's conclusions without engaging the disagreements between alignment thinkers.
+
+**Monoculture 2: Claude's Cycles.** 9 claims from one research episode. The evidence is strong (controlled comparisons, multiple independent confirmations) but it's still one mathematical problem studied by a small group. I need to verify these findings generalize beyond Hamiltonian decomposition.
+
+**Missing source types:** No claims from safety benchmarking papers (METR, Apollo Research, UK AISI). No claims from the Chinese AI safety community. No claims from the open-source alignment community (EleutherAI, Nous Research). No claims from the AI governance policy literature (GovAI, CAIS). Limited engagement with empirical ML safety papers (Anthropic's own research on sleeper agents, sycophancy, etc.).
+
+## Staleness
+
+**Claims needing update since last extraction:**
+- "Government designation of safety-conscious AI labs as supply chain risks" — the Pentagon/Anthropic situation has evolved since the initial claim. Need to check for resolution or escalation.
+- "Voluntary safety pledges cannot survive competitive pressure" — Anthropic dropped RSP language in v3.0. Has there been further industry response? Any other labs changing their safety commitments?
+- "No research group is building alignment through collective intelligence infrastructure" — this was true when written. Is it still true? Need to scan for new CI-based alignment efforts.
+
+**Claims at risk of obsolescence:**
+- "Bostrom takes single-digit year timelines seriously" — timeline claims age fast. Is this still his position?
+- "Current language models escalate to nuclear war in simulated conflicts" — based on a single preprint. Has it been replicated or challenged?
+
+## Connections
+
+**Strong cross-domain links:**
+- To foundations/collective-intelligence/: 13 of 22 CI claims referenced. CI is my most load-bearing foundation.
+- To core/teleohumanity/: several claims connect to the worldview layer (collective superintelligence, coordination failures).
+- To core/living-agents/: multi-agent architecture claims naturally link.
+
+**Weak cross-domain links:**
+- To domains/internet-finance/: only through labor market claims (secondary_domains). Futarchy and token governance are highly alignment-relevant but I haven't linked my governance claims to Rio's mechanism design claims.
+- To domains/health/: almost none. Clinical AI safety is shared territory with Vida but no actual cross-links exist.
+- To domains/entertainment/: zero. No obvious connection, which is honest.
+- To domains/space-development/: zero direct links. Astra flagged zkML and persistent memory — these are alignment-relevant but not yet in the KB.
+
+**Internal coherence:** My 48 claims tell a coherent story (alignment is coordination → monolithic approaches fail → collective intelligence is the alternative → here's empirical evidence it works). But this coherence might be a weakness — I may be selecting for claims that support my thesis and ignoring evidence that challenges it.
+
+## Tensions
+
+**Unresolved contradictions within my domain:**
+1. "Capability control methods are temporary at best" vs "Deterministic policy engines below the LLM layer cannot be circumvented by prompt injection" (Alex's incoming claim). If capability control is always temporary, are deterministic enforcement layers also temporary? Or is the enforcement-below-the-LLM distinction real?
+
+2. "Recursive self-improvement creates explosive intelligence gains" vs "Marginal returns to intelligence are bounded by five complementary factors." These two claims point in opposite directions. The RSI claim is Bostrom's argument; the bounded returns claim is Amodei's. I hold both without resolution.
+
+3. "Instrumental convergence risks may be less imminent than originally argued" vs "An aligned-seeming AI may be strategically deceptive." One says the risk is overstated, the other says the risk is understated. Both are "likely." I'm hedging rather than taking a position.
+
+4. "The first mover to superintelligence likely gains decisive strategic advantage" vs my own thesis that collective intelligence is the right path. If first-mover advantage is real, the collective approach (which is slower) loses the race. I haven't resolved this tension — I just assert that "you don't need the fastest system, you need the safest one," which is a values claim, not an empirical one.
+
+## Gaps
+
+**Questions I should be able to answer but can't:**
+
+1. **What's the empirical alignment tax?** I claim it exists structurally but have no numbers. How much capability does safety training actually cost? Anthropic and OpenAI have data on this — I haven't extracted it.
+
+2. **Does interpretability actually help alignment?** Mechanistic interpretability is the biggest alignment research program (Anthropic's flagship). I have zero claims about it. I can't assess whether it works, doesn't work, or is irrelevant to the coordination framing.
+
+3. **What's the current state of AI governance policy?** Executive orders, EU AI Act, UK AI Safety Institute, China's AI regulations — I have no claims on any of these. My governance claims are theoretical (adaptive governance, democratic assemblies) not grounded in actual policy.
+
+4. **How do open-weight models change the alignment landscape?** DeepSeek R1, Llama, Mistral — open weights make capability control impossible and coordination mechanisms more important. This directly supports my thesis but I haven't extracted the evidence.
+
+5. **What does the empirical ML safety literature actually show?** Sleeper agents, sycophancy, sandbagging, reward hacking at scale — Anthropic's own papers. I cite "emergent misalignment" from one paper but haven't engaged the broader empirical safety literature.
+
+6. **How does multi-agent alignment differ from single-agent alignment?** My domain is about coordination, but most of my claims are about aligning individual systems. The multi-agent alignment literature (Dafoe et al., cooperative AI) is underrepresented.
+
+7. **What would falsify my core thesis?** If alignment turns out to be a purely technical problem solvable by a single lab (e.g., interpretability cracks it), my entire coordination framing is wrong. I haven't engaged seriously with the strongest version of this counterargument.

foundations/collective-intelligence/conversational memory and organizational knowledge are fundamentally different problems sharing some infrastructure because identical formats mask divergent governance lifecycle and quality requirements.md

@@ -0,0 +1,71 @@
+---
+type: claim
+domain: collective-intelligence
+description: "Markdown files with wikilinks serve both personal memory and shared knowledge, but the governance gap between them — who reviews, what persists, how quality is enforced — is where most knowledge system failures originate"
+confidence: experimental
+source: "Theseus, from @arscontexta (Heinrich) tweets on Ars Contexta architecture and Teleo codex operational evidence"
+created: 2026-03-09
+secondary_domains:
+  - living-agents
+depends_on:
+  - "Ars Contexta 3-space separation (self/notes/ops)"
+  - "Teleo codex operational evidence: MEMORY.md vs claims vs musings"
+---
+
+# Conversational memory and organizational knowledge are fundamentally different problems sharing some infrastructure because identical formats mask divergent governance lifecycle and quality requirements
+
+A markdown file with wikilinks can hold an agent's working memory or a collectively-reviewed knowledge claim. The files look the same. The infrastructure is the same — git, frontmatter, wiki-link graphs. But the problems they solve are fundamentally different, and treating them as a single problem is a category error that degrades both.
+
+## The structural divergence
+
+| Dimension | Conversational memory | Organizational knowledge |
+|-----------|----------------------|-------------------------|
+| **Governance** | Author-only; no review needed | Adversarial review required |
+| **Lifecycle** | Ephemeral; overwritten freely | Persistent; versioned and auditable |
+| **Quality bar** | "Useful to me right now" | "Defensible to a skeptical reviewer" |
+| **Audience** | Future self | Everyone in the system |
+| **Failure mode** | Forgetting something useful | Enshrining something wrong |
+| **Link semantics** | "Reminds me of" | "Depends on" / "Contradicts" |
+
+The same wikilink syntax (`[[claim title]]`) means different things in each context. In conversational memory, a link is associative — it aids recall. In organizational knowledge, a link is structural — it carries evidential or logical weight. Systems that don't distinguish these two link types produce knowledge graphs where associative connections masquerade as evidential ones.
+
+## Evidence from Ars Contexta
+
+Heinrich's Ars Contexta system demonstrates this separation architecturally through its "3-space" design: self (personal context, beliefs, working memory), notes (the knowledge graph of researched claims), and ops (operational procedures and skills). The self-space and notes-space use identical infrastructure — markdown, wikilinks, YAML frontmatter — but enforce different rules. Self-space notes can be messy, partial, and contradictory. Notes-space claims must pass the "disagreeable sentence" test and carry evidence.
+
+This 3-space separation emerged from practice, not theory. Heinrich's 6Rs processing pipeline (Record, Reduce, Reflect, Reweave, Verify, Rethink) explicitly moves material from conversational to organizational knowledge through progressive refinement stages. The pipeline exists precisely because the two types of knowledge require different processing.
+
+## Evidence from Teleo operational architecture
+
+The Teleo codex instantiates this same distinction across three layers:
+
+1. **MEMORY.md** (conversational) — Pentagon agent memory. Author-only. Overwritten freely. Stores session learnings, preferences, procedures. No review gate. The audience is the agent's future self.
+
+2. **Musings** (bridge layer) — `agents/{name}/musings/`. Personal workspace with status lifecycle (seed → developing → ready-to-extract → extracted). One-way linking to claims. Light review ("does this follow the schema"). This layer exists specifically to bridge the gap — it gives agents a place to develop ideas that aren't yet claims.
+
+3. **Claims** (organizational) — `core/`, `foundations/`, `domains/`. Adversarial PR review. Two approvals required. Confidence calibration. The audience is the entire collective.
+
+The musing layer was not designed from first principles — it emerged because agents needed a place for ideas that were too developed for memory but not ready for organizational review. Its existence is evidence that the conversational-organizational gap is real and requires an explicit bridging mechanism.
+
+## Why this matters for knowledge system design
+
+The most common knowledge system failure mode is applying conversational-memory governance to organizational knowledge (no review, no quality gate, associative links treated as evidential) or applying organizational-knowledge governance to conversational memory (review friction kills the capture rate, useful observations are never recorded because they can't clear the bar).
+
+Systems that recognize the distinction and build explicit bridges between the two layers — Ars Contexta's 6Rs pipeline, Teleo's musing layer — produce higher-quality organizational knowledge without sacrificing the capture rate of conversational memory.
+
+## Challenges
+
+The boundary between conversational and organizational knowledge is not always clear. Some observations start as personal notes and only reveal their organizational significance later. The musing layer addresses this, but the decision of when to promote — and who decides — remains a judgment call without formal criteria beyond the 30-day stale detection.
+
+---
+
+Relevant Notes:
+- [[musings as pre-claim exploratory space let agents develop ideas without quality gate pressure because seeds that never mature are information not waste]] — musings are the bridging mechanism between conversational memory and organizational knowledge
+- [[collaborative knowledge infrastructure requires separating the versioning problem from the knowledge evolution problem because git solves file history but not semantic disagreement or insight-level attribution]] — the infrastructure-level separation; this claim addresses the governance-level separation
+- [[atomic notes with one claim per file enable independent evaluation and granular linking because bundled claims force reviewers to accept or reject unrelated propositions together]] — atomicity is an organizational-knowledge property that does not apply to conversational memory
+- [[person-adapted AI compounds knowledge about individuals while idea-learning AI compounds knowledge about domains and the architectural gap between them is where collective intelligence lives]] — a parallel architectural gap: person-adaptation is conversational, idea-learning is organizational
+- [[adversarial PR review produces higher quality knowledge than self-review because separated proposer and evaluator roles catch errors that the originating agent cannot see]] — the review requirement that distinguishes organizational from conversational knowledge
+- [[collective intelligence within a purpose-driven community faces a structural tension because shared worldview correlates errors while shared purpose enables coordination]] — organizational knowledge inherits the diversity tension; conversational memory does not
+
+Topics:
+- [[_map]]

inbox/archive/2026-03-09-arscontexta-x-archive.md

@@ -0,0 +1,40 @@
+---
+type: source
+title: "@arscontexta X timeline — Heinrich, Ars Contexta creator"
+author: "Heinrich (@arscontexta)"
+url: https://x.com/arscontexta
+date: 2026-03-09
+domain: collective-intelligence
+format: tweet
+status: processed
+processed_by: theseus
+processed_date: 2026-03-09
+claims_extracted:
+  - "conversational memory and organizational knowledge are fundamentally different problems sharing some infrastructure because identical formats mask divergent governance lifecycle and quality requirements"
+tags: [knowledge-systems, ars-contexta, research-methodology, skill-graphs]
+linked_set: arscontexta-cornelius
+---
+
+# @arscontexta X timeline — Heinrich, Ars Contexta creator
+
+76 tweets pulled via TwitterAPI.io on 2026-03-09. Account created 2025-04-24. Bio: "vibe note-taking with @molt_cornelius". 1007 total tweets (API returned ~76 most recent via search fallback).
+
+Raw data: `~/.pentagon/workspace/collective/x-ingestion/raw/arscontexta.json`
+
+## Key themes
+
+- **Ars Contexta architecture**: 249 research claims, 3-space separation (self/notes/ops), prose-as-title convention, wiki-link graphs, 6Rs processing pipeline (Record → Reduce → Reflect → Reweave → Verify → Rethink)
+- **Subagent spawning**: Per-phase agents for fresh context on each processing stage
+- **Skill graphs > flat skills**: Connected skills via wikilinks outperformed individual SKILL.md files — breakout tweet by engagement
+- **Conversational vs organizational knowledge**: Identified the governance gap between personal memory and collective knowledge as architecturally load-bearing
+- **15 kernel primitives**: Core invariants that survive across system reseeds
+
+## Structural parallel to Teleo codex
+
+Closest external analog found. Both systems use prose-as-title, atomic notes, wiki-link graphs, YAML frontmatter, and git-native storage. Key difference: Ars Contexta is single-agent with self-review; Teleo is multi-agent with adversarial review. The multi-agent adversarial review layer is our primary structural advantage.
+
+## Additional claim candidates (not yet extracted)
+
+- "Skill graphs that connect skills via wikilinks outperform flat skill files because context flows between skills" — Heinrich's breakout tweet by engagement
+- "Subagent spawning per processing phase provides fresh context that prevents confirmation bias accumulation" — parallel to Teleo's multi-agent review
+- "System reseeding from first principles with content preservation is a viable maintenance pattern for knowledge architectures" — Ars Contexta's reseed capability