Merge remote-tracking branch 'forgejo/extract/2026-03-31-leo-ai-weapons-strategic-utility-differentiation-governance-pathway'

# Conflicts:
#	domains/grand-strategy/ai-weapons-stigmatization-campaign-has-normative-infrastructure-without-triggering-event-creating-icbl-phase-equivalent-waiting-for-activation.md
#	domains/grand-strategy/the-legislative-ceiling-on-military-ai-governance-is-conditional-not-absolute-cwc-proves-binding-governance-without-carveouts-is-achievable-but-requires-three-currently-absent-conditions.md
#	domains/grand-strategy/verification-mechanism-is-the-critical-enabler-that-distinguishes-binding-in-practice-from-binding-in-text-arms-control-the-bwc-cwc-comparison-establishes-verification-feasibility-as-load-bearing.md

agents/astra/musings/research-2026-04-01.md

@@ -0,0 +1,178 @@
+---
+date: 2026-04-01
+type: research-musing
+agent: astra
+session: 22
+status: active
+---
+
+# Research Musing — 2026-04-01
+
+## Orientation
+
+Tweet feed is empty — 14th consecutive session. Analytical session using web search + cross-synthesis of active threads from March 31.
+
+**Previous follow-up prioritization**: Three active threads from March 31:
+1. (**Priority**) Defense/sovereign 2C pathway for ODC — is demand forming independent of commercial pricing?
+2. Verify Voyager/$90M Starship pricing (was it full-manifest or partial payload?)
+3. NG-3 launch confirmation (13 sessions unresolved going in)
+
+---
+
+## Keystone Belief Targeted for Disconfirmation
+
+**Belief #1 (Astra):** Launch cost is the keystone variable — each 10x cost drop activates a new industry tier.
+
+**Specific disconfirmation target this session:** The Two-Gate Model (March 23, Session 12) predicts ODC requires Starship-class launch economics (~$200/kg) to clear Gate 1. If ODC is already activating commercially at Falcon 9 rideshare economics (~$6K-10K/kg for small satellites, or $67M dedicated), then Gate 1 threshold predictions are wrong and Belief #1's predictive power is weaker than claimed.
+
+**What would falsify or revise Belief #1 here:** Evidence that commercial ODC revenue is scaling independent of launch cost reduction — meaning demand formation happened before the cost gate cleared.
+
+---
+
+## Research Question
+
+**How is the orbital data center sector actually activating in 2025-2026 — and does the evidence confirm, challenge, or require refinement of the Two-Gate Model's prediction that commercial ODC requires Starship-class launch economics?**
+
+This encompasses the March 31 active threads: defense demand (Direction B), Voyager pricing (Direction A), and adds the broader question of how the ODC sector is actually developing vs. how we predicted it would develop.
+
+---
+
+## Primary Finding: The Two-Gate Model Was Right in Direction But Wrong in Scale Unit
+
+### The Surprise: ODC Is Already Activating — At Small Satellite Scale
+
+The March 23–31 sessions modeled ODC activation as requiring Starship-class economics because the framing was Blue Origin's Project Sunrise (51,600 large orbital data center satellites). That framing was wrong about where activation would BEGIN.
+
+The actual activation sequence:
+
+**November 2, 2025:** Starcloud-1 launches aboard SpaceX Falcon 9. The satellite is 60 kg — the size of a small refrigerator. It carries an NVIDIA H100 GPU. In orbit, it successfully trains NanoGPT on Shakespeare and runs Gemma (Google's open LLM). This is the first AI workload demonstrated in orbit. Gate 1 for proof-of-concept ODC is **already cleared on Falcon 9 rideshare economics** (~$360K-600K at standard rideshare rates for 60 kg).
+
+**January 11, 2026:** First two ODC nodes reach LEO — Axiom Space + Kepler Communications. Equipped with optical inter-satellite links (2.5 GB/s). Processing AI inferencing in orbit. Commercially operational.
+
+**March 16, 2026:** NVIDIA announces Vera Rubin Space-1 module at GTC 2026. Delivers 25x AI compute vs. H100. Partners announced: Aetherflux, Axiom Space, Kepler Communications, Planet Labs, Sophia Space, Starcloud. NVIDIA doesn't build space-grade hardware for markets that don't exist. This is the demand signal that a sector has crossed from R&D to commercial.
+
+**March 30, 2026:** Starcloud raises $170M at $1.1B valuation (TechCrunch). The framing: "demand for compute outpaces Earth's limits." The company is planning to scale from proof-of-concept to constellation.
+
+**Q1 2027 target:** Aetherflux's "Galactic Brain" — the first orbital data center leveraging continuous solar power and radiative cooling for high-density AI processing. Founded by Baiju Bhatt (Robinhood co-founder). $50M Series A from Index, a16z, Breakthrough Energy. Aetherflux's architectural choice — sun-synchronous orbit for continuous solar exposure — is identical to Blue Origin's Project Sunrise rationale. This is NOT coincidence; it's the physically-motivated architecture converging on the same orbital regime.
+
+---
+
+### The Two-Gate Model Refinement
+
+The Two-Gate Model (March 23) said: ODC Gate 1 clears at Starship-class economics (~$200/kg). Evidence shows ODC is activating NOW at proof-of-concept scale. Apparent contradiction.
+
+**Resolution: Gate 1 is tier-specific, not sector-specific.**
+
+Within any space sector, there are multiple scale tiers, each with its own launch cost threshold:
+
+| ODC Tier | Scale | Launch Cost Gate | Status |
+|----------|-------|-----------------|--------|
+| Proof-of-concept | 1-10 satellites, 10-100 kg each | Falcon 9 rideshare (~$6-10K/kg) | **CLEARED** (Starcloud-1, Nov 2025) |
+| Commercial pilot | 50-500 satellites, 100-500 kg | Falcon 9 dedicated or rideshare ($1-3K/kg equivalent) | APPROACHING |
+| Constellation scale | 1,000-10,000 satellites | Starship-class needed ($100-500/kg) | NOT YET |
+| Megastructure (Project Sunrise) | 51,600 satellites | Starship at full reuse ($50-100/kg or better) | NOT YET |
+
+The Two-Gate Model was calibrated to the megastructure tier because that's how Blue Origin framed it. The ACTUAL market is activating bottom-up, starting with proof-of-concept and building toward scale. This is the SAME pattern as every prior satellite sector:
+- Remote sensing: 3U CubeSats → Planet Doves (3-5 kg) → larger SAR → commercial satellite
+- Communications: Iridium (expensive, limited) → Starlink (cheap, massive)
+- Earth observation: same progression
+
+**This refinement STRENGTHENS Belief #1**, not weakens it. Cost thresholds gate sectors at each tier, not once per sector. The keystone variable is real, but the model of "one threshold per sector" was underspecified. The correct formulation: each order-of-magnitude increase in ODC scale requires a new cost gate to clear.
+
+CLAIM CANDIDATE: "Space sector activation proceeds tier-by-tier within each sector, with each order-of-magnitude scale increase requiring a new launch cost threshold to clear — proof-of-concept at rideshare economics, commercial pilot at dedicated launch economics, megaconstellation at Starship-class economics."
+
+Confidence: experimental. Evidence: ODC activating at small-satellite scale while megastructure scale awaits Starship; consistent with remote sensing and comms historical patterns.
+
+---
+
+### Direction B Confirmed: Defense/Sovereign Demand Is Forming NOW
+
+The March 31 session hypothesized that defense/sovereign buyers might provide a 2C bypass for ODC independent of commercial cost-parity. Confirmed:
+
+**U.S. Space Force:** Allocated $500M for orbital computing research through 2027. Multiple DARPA programs for space-based AI defense applications. Defense buyers accept 5-10x cost premiums for strategic capabilities — the 2C-S ceiling (~2x) that constrains commercial buyers does NOT apply.
+
+**ESA ASCEND:** €300M through 2027. Framing: data sovereignty + EU Green Deal net-zero by 2050. European governments are treating orbital compute as sovereign infrastructure, not a commercial market. The ASCEND mandate is explicitly political (data sovereignty) AND environmental (CO2 reduction), not economic ROI-driven.
+
+**Analysis:** This confirms Direction B from March 31. Defense/sovereign demand IS forming now at current economics. But it reveals something more specific: the defense demand is primarily for **research and development of orbital compute capabilities**, not direct ODC procurement. The $500M Space Force allocation is research funding, not a service contract. This is different from the nuclear PPA (2C-S direct procurement at 1.8-2x premium) — it's more like early-stage R&D funding that precedes commercial procurement.
+
+**Implication for the Two-Gate Model:** Defense R&D funding is a NEW gate mechanism not captured in the original two-gate model. Call it Gate 0: government R&D that validates the sector and de-risks it for commercial investment. Remote sensing had this (NRO CubeSat programs), communications had this (DARPA satellite programs). ODC has it now.
+
+This means the sequence is:
+- Gate 0: Government R&D validates technology (Space Force $500M, ESA €300M) — **CLEARING NOW**
+- Gate 1 (Proof-of-concept): Rideshare economics support first demonstrations — **CLEARED (Nov 2025)**
+- Gate 1 (Pilot): Dedicated launch supports first commercial constellations — approaching
+- Gate 2: Revenue model independent of government anchor — NOT YET
+
+---
+
+### Direction A Resolved: Voyager/$90M Starship Pricing Confirmed
+
+The $90M Starship pricing from the March 31 session is confirmed as a DEDICATED FULL-MANIFEST launch of the entire Starlab space station (estimated 2029). At Starlab's reported volume (400 cubic meters), this represents the launch of a complete commercial station.
+
+**This is NOT the operating cost per kilogram for cargo.** The $90M figure applies to a single massive dedicated launch of the full station. At 150 metric tons nominal Starship capacity: ~$600/kg list price for a dedicated full-manifest, dated 2029.
+
+**Implication:** The $600/kg estimate holds. The gap to ODC constellation-scale ($100-200/kg needed) is real. But for proof-of-concept ODC (rideshare scale), the gap was never relevant — Falcon 9 rideshare already works.
+
+---
+
+### NG-3 Status: Session 14
+
+As of late March 2026 (NASASpaceFlight article ~1 week before April 1): NG-3 booster static fire still pending, launch still "no earlier than" late March/early April. The 14-session unresolved thread continues.
+
+**What this reveals about Pattern 2 (manufacturing-vs-execution gap):** Blue Origin's NG-3 delay pattern — now stretching from February NET to April or beyond — is running concurrently with the filing of Project Sunrise (51,600 satellites). The gap between filing 51,600 satellites and achieving 14+ week delays for a single booster static fire is a vivid illustration of Pattern 2. The ambitious strategic vision and the operational execution are operating in different time dimensions.
+
+---
+
+## CLAIM CANDIDATE (Flag for Extractor)
+
+**New claim candidate from this session:**
+
+"The orbital data center sector is activating tier-by-tier in 2025-2026, with proof-of-concept scale crossing Gate 1 on Falcon 9 rideshare economics (Starcloud-1, November 2025), while constellation-scale deployment still requires Starship-class cost reduction — demonstrating that launch cost thresholds gate each order-of-magnitude scale increase within a sector, not the sector as a whole."
+
+- Confidence: experimental
+- Domain: space-development
+- Related claims: [[launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds]], [[the space manufacturing killer app sequence is pharmaceuticals now ZBLAN fiber in 3-5 years and bioprinted organs in 15-25 years each catalyzing the next tier of orbital infrastructure]]
+- Cross-domain: connects to Theseus (AI compute scaling physics), Rio (infrastructure asset class formation)
+
+QUESTION: Does the remote sensing activation pattern (3U CubeSats → Planet → commercial SAR) provide a clean historical precedent for tier-specific Gate 1 clearing? Would strengthen this claim from experimental to likely if the analogue holds.
+
+SOURCE: This claim arises from synthesis of Starcloud-1 (DCD/CNBC, Nov 2025), Axiom+Kepler ODC nodes (Introl, Jan 2026), NVIDIA Vera Rubin Space-1 (CNBC/Newsroom, March 16, 2026), market projections ($1.77B by 2029, 67.4% CAGR).
+
+---
+
+## Disconfirmation Search Result
+
+**Target:** Evidence that ODC activated commercially without launch cost reduction — which would mean the keystone variable's predictive power is weaker than claimed.
+
+**Result:** BELIEF #1 REFINED, NOT FALSIFIED. ODC IS activating, but at the rideshare-scale tier where Falcon 9 economics already work. The Two-Gate Model's Gate 1 prediction was wrong about WHICH tier would activate first, not wrong about whether a cost gate exists. Proof-of-concept ODC already had its Gate 1 cleared years ago at rideshare pricing — the model was miscalibrated to the megastructure tier.
+
+**Belief #1 update:** The keystone variable formulation is correct. The model of "one threshold per sector" was underspecified. The correct pattern is tier-specific thresholds within each sector. Belief #1 is STRENGTHENED in its underlying mechanism, with the model made more precise.
+
+---
+
+## Follow-up Directions
+
+### Active Threads (continue next session)
+
+- **Remote sensing historical analogue for tier-specific Gate 1**: Does Planet Labs' activation sequence (3U CubeSats → Dove → Skysat) cleanly parallel ODC's activation (Starcloud-1 60kg → pilot constellation → megastructure)? If yes, this provides historical precedent for the tier-specific claim. Look for: what was the launch cost per kg when Planet Labs went from R&D to commercial? Was it Falcon 9 rideshare economics?
+- **NG-3 confirmation**: 14 sessions unresolved. If launches before next session: (a) booster landing result, (b) AST SpaceMobile BlueBird deployment confirmation, (c) Blue Origin's stated 2026 cadence vs. actual cadence gap. Check NASASpaceFlight.
+- **Aetherflux Q1 2027 delivery check**: Announced December 2025, targeting Q1 2027. Track through 2026 for slip vs. delivery. The comparison to NG-3's slip pattern (ambitious announcement → delays) would be informative about whether the ODC hardware execution gap mirrors the launch execution gap.
+- **NVIDIA Space-1 Vera Rubin availability timeline**: Currently announced as "available at a later date." When it ships will indicate how serious NVIDIA is about the orbital compute market. IGX Thor and Jetson Orin (available now) vs. Space-1 Vera Rubin (coming) shows a hardware maturation curve worth tracking.
+
+### Dead Ends (don't re-run these)
+
+- **2C-S ceiling search (>3x commercial premium)**: Already confirmed across two sessions — no documented cases. Don't re-run.
+- **Voyager/$90M pricing**: Confirmed as full-manifest dedicated launch, 2029, ~$600/kg. Resolved. Don't re-run.
+- **Defense demand existence check**: Confirmed (Space Force $500M, ESA €300M). The question was whether defense demand EXISTS — it does. The next question (does it constitute 2C activation or just Gate 0 R&D?) is a different research question.
+
+### Branching Points
+
+- **ODC as platform for space-based solar power pivot**: Aetherflux's architecture reveals that ODC and SBSP share the same orbital requirements (sun-synchronous, continuous solar exposure, space-grade hardware). Aetherflux is building the same physical system for both ODC and SBSP. This creates a potential bifurcation:
+  - **Direction A**: ODC is the near-term revenue bridge that funds SBSP long-term. Track Aetherflux specifically for signs of SBSP commercialization via ODC bridge.
+  - **Direction B**: ODC and SBSP are actually the same infrastructure with different demand curves — the satellite network serves AI compute (immediate demand) and SBSP (long-term demand). The dual-use architecture makes the first customer (AI compute) cross-subsidize the harder sell (SBSP). This has a direct parallel to Starlink cross-subsidizing Starship.
+  - **Priority**: Direction B first — if the Aetherflux architecture confirms the SBSP/ODC dual-use claim, it's a significant cross-domain insight connecting energy (SBSP) and space (ODC infrastructure). Flag for Leo cross-domain synthesis.
+
+- **ODC as new space economy category requiring market sizing update**: Current $613B (2024) space economy estimates don't include orbital compute as a category. If ODC grows to $39B by 2035 as projected (67.4% CAGR from $1.77B in 2029), this represents a new economic layer on top of existing estimates. Two directions:
+  - **Direction A**: The $39B by 2035 projection is included in or overlaps with existing space economy projections (Starlink revenue is already counted). Investigate whether ODC market projections double-count.
+  - **Direction B**: ODC represents genuinely new space economy category not captured in existing SIA/Bryce estimates — extractable as a claim candidate about space economy market expansion beyond current projections.
+  - **Priority**: Check Bryce Space / SIA space economy methodology to determine if ODC is already counted. Quick verification question, not deep research.

agents/astra/research-journal.md

@@ -395,3 +395,49 @@ Secondary: NG-3 non-launch enters 12th consecutive session. No new data. Pattern
 **Sources archived this session:** 1 new archive — `inbox/queue/2026-03-30-astra-gate2-cost-parity-constraint-analysis.md` (internal analytical synthesis, claim candidates at experimental confidence).
 
 **Tweet feed status:** EMPTY — 12th consecutive session.
+
+---
+
+## Session 2026-04-01
+
+**Question:** How is the orbital data center sector actually activating in 2025-2026 — and does the evidence confirm, challenge, or require refinement of the Two-Gate Model's prediction that commercial ODC requires Starship-class launch economics?
+
+**Belief targeted:** Belief #1 (launch cost is the keystone variable) — the Two-Gate Model (March 23) predicted ODC Gate 1 would require Starship-class economics (~$200/kg) to activate. If ODC is activating at Falcon 9 rideshare economics, that prediction is wrong, which would weaken Belief #1's predictive power.
+
+**Disconfirmation result:** BELIEF #1 REFINED, NOT FALSIFIED. ODC IS activating — but at the small-satellite proof-of-concept tier, where Falcon 9 rideshare economics already cleared Gate 1 years ago. The Two-Gate Model was miscalibrated to the megastructure tier (Blue Origin Project Sunrise: 51,600 satellites) and missed that the sector was already clearing Gate 1 tier-by-tier from small satellite scale upward. The keystone variable is real; the "one threshold per sector" model was underspecified.
+
+**Key finding:** The ODC sector has crossed multiple activation milestones in the past 5 months:
+- **November 2, 2025:** Starcloud-1 (60 kg, SpaceX rideshare) — first H100 GPU in orbit, first AI model trained in space. Proof-of-concept tier Gate 1 CLEARED at rideshare economics.
+- **January 11, 2026:** Axiom Space + Kepler Communications first two ODC nodes operational in LEO. Embedded in commercial relay network (2.5 GB/s OISL). AI inferencing as commercial service.
+- **March 16, 2026:** NVIDIA announces Vera Rubin Space-1 module at GTC (25x H100 for orbital compute). Six named ODC operator partners. Hardware supply chain committing to sector.
+- **March 30, 2026:** Starcloud raises $170M at $1.1B valuation. Market projections: $1.77B by 2029, $39B by 2035 at 67.4% CAGR.
+
+**Parallel finding — Direction B CONFIRMED:** Defense/sovereign demand IS forming for ODC independent of commercial pricing:
+- Space Force: $500M for orbital computing research through 2027
+- ESA ASCEND: €300M through 2027 (data sovereignty + CO2 reduction framing)
+- This is Gate 0 (government R&D), not 2C-S procurement — but it validates technology and de-risks commercial investment
+
+**Voyager/$90M pricing resolved:** Confirmed as dedicated full-manifest launch for complete Starlab station, 2029, ~$600/kg list price. Not current operating cost; not rideshare rate. The gap from $600/kg to ODC megaconstellation threshold ($100-200/kg) remains real and requires sustained reuse improvement. Closes the March 31 branching point.
+
+**NG-3 status:** 14th consecutive session. As of late March 2026, booster static fire still pending. Pattern 2 continues.
+
+**Pattern update:**
+- **Pattern 10 (Two-gate model) — STRUCTURALLY REFINED:** Gate 1 is tier-specific within each sector, not sector-wide. ODC activating bottom-up at small-satellite scale. Correct formulation: each order-of-magnitude scale increase within a sector requires a new cost gate to clear. Adding Gate 0 (government R&D validation) as a structural precursor to the two-gate sequence.
+- **Pattern 11 (ODC sector) — ACCELERATING:** Sector activation is significantly ahead of March 30-31 predictions. Proof-of-concept Gate 1 cleared Nov 2025. NVIDIA hardware commitment (March 2026) is the hardware ecosystem formation threshold. Defense/ESA demand creating Gate 0 catalyst. ODC is not waiting for Starship.
+- **Pattern 2 (institutional timelines) — 14th session:** NG-3 still unflown. Blue Origin simultaneously filing for 51,600-satellite constellation (Project Sunrise) while unable to refly a single booster in 14 sessions. The ambition-execution gap is now documented across a full quarter of sessions.
+- **NEW — Pattern 14 (dual-use ODC/SBSP architecture):** Aetherflux's Galactic Brain reveals that ODC and space-based solar power require IDENTICAL orbital infrastructure (sun-synchronous orbit, continuous solar exposure). ODC near-term revenue cross-subsidizes SBSP long-term development. Same architecture as Project Sunrise (Blue Origin). This dual-use convergence was not predicted by the KB — it emerges from independent engineering constraints.
+
+**Confidence shift:**
+- Belief #1 (launch cost keystone): STRENGTHENED IN MECHANISM, PREDICTION REFINED. The tier-specific Gate 1 model is a more precise version of Belief #1, not a challenge to it. The underlying claim (cost thresholds gate industries) is more confirmed, with the model made more precise.
+- Two-gate model: REFINED — Gate 0 added as precursor; Gate 1 made tier-specific; the model is now a three-stage sequential framework (Gate 0 → Gate 1 tiers → Gate 2). Previous claim candidates at experimental confidence need annotation about tier-specificity.
+- Belief #6 (colony technologies dual-use): SIGNIFICANTLY STRENGTHENED — Aetherflux's ODC/SBSP convergence is the most concrete evidence yet that space technologies are structurally dual-use. The same satellite network serves AI compute (terrestrial demand) and SBSP (energy supply). This is exactly the dual-use thesis, with commercial logic driving it rather than design intent.
+
+**Sources archived this session:** 5 new archives:
+1. `2025-11-02-starcloud-h100-first-ai-workload-orbit.md`
+2. `2026-03-16-nvidia-vera-rubin-space1-orbital-ai-hardware.md`
+3. `2026-01-11-axiom-kepler-first-odc-nodes-leo.md`
+4. `2025-12-10-aetherflux-galactic-brain-orbital-solar-compute.md`
+5. `2026-04-01-defense-sovereign-odc-demand-formation.md`
+6. `2026-04-01-voyager-starship-90m-pricing-verification.md`
+
+**Tweet feed status:** EMPTY — 14th consecutive session.

core/contribution-architecture.md

@@ -0,0 +1,216 @@
+---
+type: claim
+domain: mechanisms
+description: "Architecture paper defining the five contribution roles, their weights, attribution chain, and governance implications — supersedes the original reward-mechanism.md role weights and CI formula"
+confidence: likely
+source: "Leo, original architecture with Cory-approved weight calibration"
+created: 2026-03-26
+---
+
+# Contribution Scoring & Attribution Architecture
+
+How LivingIP measures, attributes, and rewards contributions to collective intelligence. This paper explains the *why* behind every design decision — the incentive structure, the attribution chain, and the governance implications of meritocratic contribution scoring.
+
+### Relationship to reward-mechanism.md
+
+This document supersedes specific sections of [[reward-mechanism]] while preserving others:
+
+| Topic | reward-mechanism.md (v0) | This document (v1) | Change rationale |
+|-------|-------------------------|---------------------|-----------------|
+| **Role weights** | 0.25/0.25/0.25/0.15/0.10 (equal top-3) | 0.35/0.25/0.20/0.15/0.05 (challenger-heavy) | Equal weights incentivized volume over quality; bootstrap data showed extraction dominating CI |
+| **CI formula** | 3 leaderboards (0.30 Belief + 0.30 Challenge + 0.40 Connection) | Single role-weighted aggregation per claim | Leaderboard model preserved as future display layer; underlying measurement simplified to role weights |
+| **Source authors** | Citation only, not attribution | Credited as Sourcer (0.15 weight) | Their intellectual contribution is foundational; citation without credit understates their role |
+| **Reviewer weight** | 0.10 | 0.20 | Review is skilled judgment work, not rubber-stamping; v0 underweighted it |
+
+**What reward-mechanism.md still governs:** The three leaderboards (Belief Movers, Challenge Champions, Connection Finders), their scoring formulas, anti-gaming properties, and economic mechanism. These are display and incentive layers built on top of the attribution weights defined here. The leaderboard weights (0.30/0.30/0.40) determine how CI converts to leaderboard position — they are not the same as the role weights that determine how individual contributions earn CI.
+
+## 1. Mechanism Design
+
+### The core problem
+
+Collective intelligence systems need to answer: who made us smarter, and by how much? Get this wrong and you either reward volume over quality (producing noise), reward incumbency over contribution (producing stagnation), or fail to attribute at all (producing free-rider collapse).
+
+### Five contribution roles
+
+Every piece of knowledge in the system traces back to people who played specific roles in producing it. We identify five, because the knowledge production pipeline has exactly five distinct bottlenecks:
+
+| Role | What they do | Why it matters |
+|------|-------------|----------------|
+| **Sourcer** | Identifies the source material or research direction | Without sourcers, agents have nothing to work with. The quality of inputs bounds the quality of outputs. |
+| **Extractor** | Separates signal from noise, writes the atomic claim | Necessary but increasingly mechanical. LLMs do heavy lifting. The skill is judgment about what's worth extracting, not the extraction itself. |
+| **Challenger** | Tests claims through counter-evidence or boundary conditions | The hardest and most valuable role. Challengers make existing knowledge better. A successful challenge that survives counter-attempts is the highest-value contribution because it improves what the collective already believes. |
+| **Synthesizer** | Connects claims across domains, producing insight neither domain could see alone | Cross-domain connections are the unique output of collective intelligence. No single specialist produces these. Synthesis is where the system generates value that no individual contributor could. |
+| **Reviewer** | Evaluates claim quality, enforces standards, approves or rejects | The quality gate. Without reviewers, the knowledge base degrades toward noise. Reviewing is undervalued in most systems — we weight it explicitly. |
+
+### Why these weights
+
+```
+Challenger:   0.35
+Synthesizer:  0.25
+Reviewer:     0.20
+Sourcer:      0.15
+Extractor:    0.05
+```
+
+**Challenger at 0.35 (highest):** Improving existing knowledge is harder and more valuable than adding new knowledge. A challenge requires understanding the existing claim well enough to identify its weakest point, finding counter-evidence, and constructing an argument that survives adversarial review. Most challenges fail — the ones that succeed materially improve the knowledge base. The high weight incentivizes the behavior we want most: rigorous testing of what we believe.
+
+**Synthesizer at 0.25:** Cross-domain insight is the collective's unique competitive advantage. No individual specialist sees the connection between GLP-1 persistence economics and futarchy governance design. A synthesizer who identifies a real cross-domain mechanism (not just analogy) creates knowledge that couldn't exist without the collective. This is the system's core value proposition, weighted accordingly.
+
+**Reviewer at 0.20:** Quality gates are load-bearing infrastructure. Every claim that enters the knowledge base was approved by a reviewer. Bad claims that slip through degrade collective beliefs. The reviewer role was historically underweighted (0.10 in v0) because it's invisible — good reviewing looks like nothing happening. The increase to 0.20 reflects that review is skilled judgment work, not rubber-stamping.
+
+**Sourcer at 0.15:** Finding the right material to analyze is real work with a skill ceiling — knowing where to look, what's worth reading, which research directions are productive. But sourcing doesn't transform the material. The sourcer identifies the ore; others refine it. 0.15 reflects genuine contribution without overweighting the input relative to the processing.
+
+**Extractor at 0.05 (lowest):** Extraction — reading a source and producing claims from it — is increasingly mechanical. LLMs do the heavy lifting. The human/agent skill is in judgment about what to extract, which is captured by the sourcer role (directing the research mission) and reviewer role (evaluating what was extracted). The extraction itself is low-skill-ceiling work that scales with compute, not with expertise.
+
+### What the weights incentivize
+
+The old weights (extractor at 0.25, equal to sourcer and challenger) incentivized volume because extraction was the easiest role to accumulate at scale. With equal weighting, an agent that extracted 100 claims earned the same per-unit CI as one that successfully challenged 5 — but the extractor could do it 20x faster. The bottleneck was throughput, not quality.
+
+The new weights incentivize: challenge existing claims, synthesize across domains, review carefully → high CI. This rewards the behaviors that make the knowledge base *better*, not just *bigger*. A contributor who challenges one claim and wins contributes more CI than one who extracts twenty claims from a source.
+
+This is deliberate: the system should reward quality over volume, depth over breadth, and improvement over accumulation.
+
+## 2. Attribution Architecture
+
+### The knowledge chain
+
+Every position traces back through a chain of evidence:
+
+```
+Source material → Claim → Belief → Position
+     ↑               ↑        ↑         ↑
+  sourcer        extractor  synthesizer  agent judgment
+                 reviewer   challenger
+```
+
+Attribution records who contributed at each link. A claim's `source:` field traces to the original author. Its `attribution` block records who extracted, reviewed, challenged, and synthesized it. Beliefs cite claims. Positions cite beliefs. The entire chain is traversable — from a public position back to the original evidence and every contributor who shaped it along the way.
+
+### Three types of contributors
+
+**1. Source authors (external):** The thinkers whose ideas the KB is built on. Nick Bostrom, Robin Hanson, metaproph3t, Dario Amodei, Matthew Ball. They contributed the raw intellectual material. Credited as **sourcer** (0.15 weight) — their work is the foundation even though they didn't interact with the system directly. Identified by parsing claim `source:` fields and matching against entity records.
+
+*Change from v0:* reward-mechanism.md treated source authors as citation-only (referenced in evidence, not attributed). This understated their contribution — without their intellectual work, the claims wouldn't exist. The change to sourcer credit recognizes that identifying and producing the source material is real intellectual contribution, whether or not the author interacted with the system directly. The 0.15 weight is modest — it reflects that sourcing doesn't transform the material, but it does ground it.
+
+**2. Human operators (internal):** People who direct agents, review outputs, set research missions, and exercise governance authority. Credited across all five roles depending on their activity. Their agents' work rolls up to them via the **principal** mechanism (see below).
+
+**3. Agents (infrastructure):** AI agents that extract, synthesize, review, and evaluate. Credited individually for operational tracking, but their contributions attribute to their human **principal** for governance purposes.
+
+### Principal-agent attribution
+
+A local agent (Rio, Clay, Theseus, etc.) operates on behalf of a human. The human directs research missions, sets priorities, and exercises judgment through the agent. The agent is an instrument of the human's intellectual contribution.
+
+The `principal` field records this relationship:
+
+```
+Agent: rio    → Principal: m3taversal
+Agent: clay   → Principal: m3taversal
+Agent: theseus → Principal: m3taversal
+```
+
+**Governance CI** rolls up: m3taversal's CI = direct contributions + all agent contributions where `principal = m3taversal`.
+
+**VPS infrastructure agents** (Epimetheus, Argus) have `principal = null`. They run autonomously on pipeline and monitoring tasks. Their work is infrastructure — it keeps the system running but doesn't produce knowledge. Infrastructure contributions are tracked separately and do not count toward governance CI.
+
+**Why this matters for multiplayer:** When a second user joins with their own agents, their agents attribute to them. The principal mechanism scales without schema changes. Each human sees their full intellectual impact regardless of how many agents they employ.
+
+**Concentration risk:** Currently all agents roll up to a single principal (m3taversal). This is expected during bootstrap — the system has one operator. But as more humans join, the roll-up must distribute. No bounds are needed now because there is nothing to bound against; the mitigation is multiplayer adoption itself. If concentration persists after the system has 3+ active principals, that is a signal to review whether the principal mechanism is working as designed.
+
+### Commit-type classification
+
+Not all repository activity is knowledge contribution. The system distinguishes:
+
+| Type | Examples | CI weight |
+|------|----------|-----------|
+| **Knowledge** | New claims, enrichments, challenges, synthesis, belief updates | Full weight (per role) |
+| **Pipeline** | Source archival, auto-fix, entity batches, ingestion, queue management | Zero CI weight |
+
+Classification happens at merge time by checking which directories the PR touched. Files in `domains/`, `core/`, `foundations/`, `decisions/` = knowledge. Files in `inbox/`, `entities/` only = pipeline.
+
+This prevents CI inflation from mechanical work. An agent that archives 100 sources earns zero CI. An agent that extracts 5 claims from those sources earns CI proportional to its role.
+
+## 3. Pipeline Integration
+
+### The extraction → eval → merge → attribution chain
+
+```
+1. Source identified (sourcer credit)
+2. Agent extracts claims on a branch (extractor credit)
+3. PR opened against main
+4. Tier-0 mechanical validation (schema, wiki links)
+5. LLM evaluation (cross-domain + domain peer + self-review)
+6. Reviewer approves or requests changes (reviewer credit)
+7. PR merges
+8. Post-merge: contributor table updated with role credits
+9. Post-merge: claim embedded in Qdrant for semantic retrieval
+10. Post-merge: source archive status updated
+```
+
+### Where attribution data lives
+
+- **Git trailers** (`Pentagon-Agent: Rio <UUID>`): who committed the change to the repository
+- **Claim YAML** (`attribution:` block): who contributed what in which role on this specific claim
+- **Claim YAML** (`source:` field): human-readable reference to the original source author
+- **Pipeline DB** (`contributors` table): aggregated role counts, CI scores, principal relationships
+- **Pentagon agent config**: principal mapping (which agents work for which humans)
+
+These are complementary, not redundant. Git trailers answer "who made this commit." YAML attribution answers "who produced this knowledge." The contributors table answers "what is this person's total contribution." Pentagon config answers "who does this agent work for."
+
+### Forgejo as source of truth
+
+The git repository is the canonical record. Pipeline DB is derived state — it can always be reconstructed from git history. If pipeline DB is lost, a backfill from git + Forgejo API restores all contributor data. This is deliberate: the source of truth is the one thing that survives platform migration.
+
+## 4. Governance Implications
+
+### CI as governance weight
+
+Contribution Index determines governance authority in a meritocratic system. Contributors who made the KB smarter have more influence over its direction. This is not democracy (one person, one vote) and not plutocracy (one dollar, one vote). It is epistocracy weighted by demonstrated contribution quality.
+
+The governance model (target state — some elements active now, others phased in):
+
+1. **Agents operate at full speed** — propose, review, merge, enrich. No human gates in the loop. Speed is a feature, not a risk. *Current state: agents propose and review autonomously, but all PRs require review before merge (bootstrap phase). The "no human gates" principle means humans don't block the pipeline — they flag after the fact via veto.*
+2. **Humans review asynchronously** — browse diagnostics, read weekly reports, spot-check claims. When something looks wrong, flag it.
+3. **Flags carry weight based on CI** — a veteran contributor's flag gets immediate attention. A new contributor's flag gets evaluated. High CI = earned authority. *Current state: CI scoring deployed but flag-weighting not yet implemented. All flags currently receive equal treatment.*
+4. **Veto = rollback, not block** — a human veto reverts a merged change rather than preventing it. The KB stays fast, corrections happen in the next cycle.
+
+### Progressive decentralization
+
+Agents are under human control now. This is appropriate — the system is 20 days old. As agents demonstrate reliability (measured by error rate, flag frequency, and the ratio of accepted to rejected work), they earn increasing autonomy:
+
+- **Current:** Agents integrate autonomously, humans can flag and veto after the fact.
+- **Near-term:** Agents with clean track records earn reduced review requirements on routine work.
+- **Long-term:** The principal relationship loosens for agents that consistently produce high-quality work. Eventually, some agents may operate without a principal.
+
+The progression is not time-based ("after 6 months") but performance-based ("after N consecutive clean reviews"). The criteria for decentralization are themselves claims in the KB, subject to the same adversarial review as everything else.
+
+The `principal` field supports this transition by being nullable. Setting `principal = null` removes the roll-up — the agent's contributions stand on their own. This is a human decision, not an algorithmic one. The data informs it; the human makes the call.
+
+### CI evolution roadmap
+
+**v1 (current): Role-weighted CI.** Contribution scored by which roles you played. Incentivizes challenging, synthesizing, and reviewing over extracting.
+
+**v2 (next): Outcome-weighted CI.** Did the challenge survive counter-attempts? Did the synthesis get cited by other claims? Did the extraction produce claims that passed review? Outcomes weight more than activity. Greater complexity earned, not designed.
+
+**v3 (future): Usage-weighted CI.** Which claims actually get used in agent reasoning? How often? Contributions that produce frequently-referenced knowledge score higher than contributions that sit unread. This requires usage instrumentation infrastructure (claim_usage telemetry) currently being built.
+
+Each layer adds a more accurate signal of real contribution value. The progression is: input → outcome → impact.
+
+### Connection to LivingIP
+
+Contribution-weighted ownership is the core thesis of LivingIP. The CI system is the measurement layer that makes this possible. When contribution translates to governance authority, and governance authority translates to economic participation, the incentive loop closes: contribute knowledge → earn authority → direct capital → fund research → produce more knowledge.
+
+The attribution architecture ensures this loop is traceable. Every dollar of economic value traces back through positions → beliefs → claims → sources → contributors. No contribution is invisible. No authority is unearned.
+
+---
+
+*Architecture designed by Leo with input from Rhea (system architecture), Argus (data infrastructure), Epimetheus (pipeline integration), and Cory (governance direction). 2026-03-26.*
+
+---
+
+Relevant Notes:
+- [[reward-mechanism]] — v0 incentive design (leaderboards, anti-gaming, economic mechanism); role weights and CI formula superseded by this document
+- [[epistemology]] — knowledge structure the attribution chain operates on
+- [[product-strategy]] — what we're building and why
+- [[collective-agent-core]] — shared agent DNA that the principal mechanism builds on
+
+Topics:
+- [[overview]]