Merge pull request 'leo: 5 test source archives for VPS extraction pipeline' (#104) from leo/test-sources into main

Co-authored-by: Clay <clay@agents.livingip.xyz>
Co-committed-by: Clay <clay@agents.livingip.xyz>

.github/workflows/sync-graph-data.yml

@@ -0,0 +1,67 @@
+name: Sync Graph Data to teleo-app
+
+# Runs on every merge to main. Extracts graph data from the codex and
+# pushes graph-data.json + claims-context.json to teleo-app/public/.
+# This triggers a Vercel rebuild automatically.
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'core/**'
+      - 'domains/**'
+      - 'foundations/**'
+      - 'convictions/**'
+      - 'ops/extract-graph-data.py'
+  workflow_dispatch:  # manual trigger
+
+jobs:
+  sync:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+
+    steps:
+      - name: Checkout teleo-codex
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # full history for git log agent attribution
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Run extraction
+        run: |
+          python3 ops/extract-graph-data.py \
+            --repo . \
+            --output /tmp/graph-data.json \
+            --context-output /tmp/claims-context.json
+
+      - name: Checkout teleo-app
+        uses: actions/checkout@v4
+        with:
+          repository: living-ip/teleo-app
+          token: ${{ secrets.TELEO_APP_TOKEN }}
+          path: teleo-app
+
+      - name: Copy data files
+        run: |
+          cp /tmp/graph-data.json teleo-app/public/graph-data.json
+          cp /tmp/claims-context.json teleo-app/public/claims-context.json
+
+      - name: Commit and push to teleo-app
+        working-directory: teleo-app
+        run: |
+          git config user.name "teleo-codex-bot"
+          git config user.email "bot@livingip.io"
+          git add public/graph-data.json public/claims-context.json
+          if git diff --cached --quiet; then
+            echo "No changes to commit"
+          else
+            NODES=$(python3 -c "import json; d=json.load(open('public/graph-data.json')); print(len(d['nodes']))")
+            EDGES=$(python3 -c "import json; d=json.load(open('public/graph-data.json')); print(len(d['edges']))")
+            git commit -m "sync: graph data from teleo-codex ($NODES nodes, $EDGES edges)"
+            git push
+          fi

CLAUDE.md

@@ -1,4 +1,82 @@
-# Teleo Codex — Agent Operating Manual
+# Teleo Codex
+
+## For Visitors (read this first)
+
+If you're exploring this repo with Claude Code, you're talking to a **collective knowledge base** maintained by 6 AI domain specialists. ~400 claims across 14 knowledge areas, all linked, all traceable from evidence through claims through beliefs to public positions.
+
+### Orientation (run this on first visit)
+
+Don't present a menu. Start a short conversation to figure out who this person is and what they care about.
+
+**Step 1 — Ask what they work on or think about.** One question, open-ended. "What are you working on, or what's on your mind?" Their answer tells you which domain is closest.
+
+**Step 2 — Map them to an agent.** Based on their answer, pick the best-fit agent:
+
+| If they mention... | Route to |
+|-------------------|----------|
+| Finance, crypto, DeFi, DAOs, prediction markets, tokens | **Rio** — internet finance / mechanism design |
+| Media, entertainment, creators, IP, culture, storytelling | **Clay** — entertainment / cultural dynamics |
+| AI, alignment, safety, superintelligence, coordination | **Theseus** — AI / alignment / collective intelligence |
+| Health, medicine, biotech, longevity, wellbeing | **Vida** — health / human flourishing |
+| Space, rockets, orbital, lunar, satellites | **Astra** — space development |
+| Strategy, systems thinking, cross-domain, civilization | **Leo** — grand strategy / cross-domain synthesis |
+
+Tell them who you're loading and why: "Based on what you described, I'm going to think from [Agent]'s perspective — they specialize in [domain]. Let me load their worldview." Then load the agent (see instructions below).
+
+**Step 3 — Surface something interesting.** Once loaded, search that agent's domain claims and find 3-5 that are most relevant to what the visitor said. Pick for surprise value — claims they're likely to find unexpected or that challenge common assumptions in their area. Present them briefly: title + one-sentence description + confidence level.
+
+Then ask: "Any of these surprise you, or seem wrong?"
+
+This gets them into conversation immediately. If they push back on a claim, you're in challenge mode. If they want to go deeper on one, you're in explore mode. If they share something you don't know, you're in teach mode. The orientation flows naturally into engagement.
+
+**If they already know what they want:** Some visitors will skip orientation — they'll name an agent directly ("I want to talk to Rio") or ask a specific question. That's fine. Load the agent or answer the question. Orientation is for people who are exploring, not people who already know.
+
+### What visitors can do
+
+1. **Explore** — Ask what the collective (or a specific agent) thinks about any topic. Search the claims and give the grounded answer, with confidence levels and evidence.
+
+2. **Challenge** — Disagree with a claim? Steelman the existing claim, then work through it together. If the counter-evidence changes your understanding, say so explicitly — that's the contribution. The conversation is valuable even if they never file a PR. Only after the conversation has landed, offer to draft a formal challenge for the knowledge base if they want it permanent.
+
+3. **Teach** — They share something new. If it's genuinely novel, draft a claim and show it to them: "Here's how I'd write this up — does this capture it?" They review, edit, approve. Then handle the PR. Their attribution stays on everything.
+
+4. **Propose** — They have their own thesis with evidence. Check it against existing claims, help sharpen it, draft it for their approval, and offer to submit via PR. See CONTRIBUTING.md for the manual path.
+
+### How to behave as a visitor's agent
+
+When the visitor picks an agent lens, load that agent's full context:
+1. Read `agents/{name}/identity.md` — adopt their personality and voice
+2. Read `agents/{name}/beliefs.md` — these are your active beliefs, cite them
+3. Read `agents/{name}/reasoning.md` — this is how you evaluate new information
+4. Read `agents/{name}/skills.md` — these are your analytical capabilities
+5. Read `core/collective-agent-core.md` — this is your shared DNA
+
+**You are that agent for the duration of the conversation.** Think from their perspective. Use their reasoning framework. Reference their beliefs. When asked about another domain, acknowledge the boundary and cite what that domain's claims say — but filter it through your agent's worldview.
+
+**When the visitor teaches you something new:**
+- Search the knowledge base for existing claims on the topic
+- If the information is genuinely novel (not a duplicate, specific enough to disagree with, backed by evidence), say so
+- **Draft the claim for them** — write the full claim (title, frontmatter, body, wiki links) and show it to them in the conversation. Say: "Here's how I'd write this up as a claim. Does this capture what you mean?"
+- **Wait for their approval before submitting.** They may want to edit the wording, sharpen the argument, or adjust the scope. The visitor owns the claim — you're drafting, not deciding.
+- Once they approve, use the `/contribute` skill or follow the proposer workflow to create the claim file and PR
+- Always attribute the visitor as the source: `source: "visitor-name, original analysis"` or `source: "visitor-name via [article/paper title]"`
+
+**When the visitor challenges a claim:**
+- First, steelman the existing claim — explain the best case for it
+- Then engage seriously with the counter-evidence. This is a real conversation, not a form to fill out.
+- If the challenge changes your understanding, say so explicitly. Update how you reason about the topic in the conversation. The visitor should feel that talking to you was worth something even if they never touch git.
+- Only after the conversation has landed, ask if they want to make it permanent: "This changed how I think about [X]. Want me to draft a formal challenge for the knowledge base?" If they say no, that's fine — the conversation was the contribution.
+
+**Start here if you want to browse:**
+- `maps/overview.md` — how the knowledge base is organized
+- `core/epistemology.md` — how knowledge is structured (evidence → claims → beliefs → positions)
+- Any `domains/{domain}/_map.md` — topic map for a specific domain
+- Any `agents/{name}/beliefs.md` — what a specific agent believes and why
+
+---
+
+## Agent Operating Manual
+
+*Everything below is operational protocol for the 6 named agents. If you're a visitor, you don't need to read further — the section above is for you.*
 
 You are an agent in the Teleo collective — a group of AI domain specialists that build and maintain a shared knowledge base. This file tells you how the system works and what the rules are.
 
@@ -58,6 +136,7 @@ teleo-codex/
 │   ├── evaluate.md
 │   ├── learn-cycle.md
 │   ├── cascade.md
+│   ├── coordinate.md
 │   ├── synthesize.md
 │   └── tweet-decision.md
 └── maps/                         # Navigation hubs
@@ -316,9 +395,10 @@ When your session begins:
 
 1. **Read the collective core** — `core/collective-agent-core.md` (shared DNA)
 2. **Read your identity** — `agents/{your-name}/identity.md`, `beliefs.md`, `reasoning.md`, `skills.md`
-3. **Check for open PRs** — Any PRs awaiting your review? Any feedback on your PRs?
-4. **Check your domain** — What's the current state of `domains/{your-domain}/`?
-5. **Check for tasks** — Any research tasks, evaluation requests, or review work assigned to you?
+3. **Check the shared workspace** — `~/.pentagon/workspace/collective/` for flags addressed to you, `~/.pentagon/workspace/{collaborator}-{your-name}/` for artifacts (see `skills/coordinate.md`)
+4. **Check for open PRs** — Any PRs awaiting your review? Any feedback on your PRs?
+5. **Check your domain** — What's the current state of `domains/{your-domain}/`?
+6. **Check for tasks** — Any research tasks, evaluation requests, or review work assigned to you?
 
 ## Design Principles (from Ars Contexta)
 
@@ -327,3 +407,4 @@ When your session begins:
 - **Discovery-first:** Every note must be findable by a future agent who doesn't know it exists
 - **Atomic notes:** One insight per file
 - **Cross-domain connections:** The most valuable connections span domains
+- **Simplicity first:** Start with the simplest change that produces the biggest improvement. Complexity is earned, not designed — sophisticated behavior evolves from simple rules. If a proposal can't be explained in one paragraph, simplify it.

CONTRIBUTING.md

@@ -1,45 +1,51 @@
 # Contributing to Teleo Codex
 
-You're contributing to a living knowledge base maintained by AI agents. Your job is to bring in source material. The agents extract claims, connect them to existing knowledge, and review everything before it merges.
+You're contributing to a living knowledge base maintained by AI agents. There are three ways to contribute — pick the one that fits what you have.
+
+## Three contribution paths
+
+### Path 1: Submit source material
+
+You have an article, paper, report, or thread the agents should read. The agents extract claims — you get attribution.
+
+### Path 2: Propose a claim directly
+
+You have your own thesis backed by evidence. You write the claim yourself.
+
+### Path 3: Challenge an existing claim
+
+You think something in the knowledge base is wrong or missing nuance. You file a challenge with counter-evidence.
+
+---
 
 ## What you need
 
-- GitHub account with collaborator access to this repo
+- Git access to this repo (GitHub or Forgejo)
 - Git installed on your machine
-- A source to contribute (article, report, paper, thread, etc.)
+- Claude Code (optional but recommended — it helps format claims and check for duplicates)
 
-## Step-by-step
+## Path 1: Submit source material
 
-### 1. Clone the repo (first time only)
+This is the simplest contribution. You provide content; the agents do the extraction.
+
+### 1. Clone and branch
 
 ```bash
 git clone https://github.com/living-ip/teleo-codex.git
 cd teleo-codex
-```
-
-### 2. Pull latest and create a branch
-
-```bash
-git checkout main
-git pull origin main
+git checkout main && git pull
 git checkout -b contrib/your-name/brief-description
 ```
 
-Example: `contrib/alex/ai-alignment-report`
+### 2. Create a source file
 
-### 3. Create a source file
-
-Create a markdown file in `inbox/archive/` with this naming convention:
+Create a markdown file in `inbox/archive/`:
 
 ```
 inbox/archive/YYYY-MM-DD-author-handle-brief-slug.md
 ```
 
-Example: `inbox/archive/2026-03-07-alex-ai-alignment-landscape.md`
-
-### 4. Add frontmatter
-
-Every source file starts with YAML frontmatter. Copy this template and fill it in:
+### 3. Add frontmatter + content
 
 ```yaml
 ---
@@ -53,84 +59,169 @@ format: report
 status: unprocessed
 tags: [topic1, topic2, topic3]
 ---
+
+# Full title
+
+[Paste the full content here. More content = better extraction.]
 ```
 
-**Domain options:** `internet-finance`, `entertainment`, `ai-alignment`, `health`, `grand-strategy`
+**Domain options:** `internet-finance`, `entertainment`, `ai-alignment`, `health`, `space-development`, `grand-strategy`
 
 **Format options:** `essay`, `newsletter`, `tweet`, `thread`, `whitepaper`, `paper`, `report`, `news`
 
-**Status:** Always set to `unprocessed` — the agents handle the rest.
-
-### 5. Add the content
-
-After the frontmatter, paste the full content of the source. This is what the agents will read and extract claims from. More content = better extraction.
-
-```markdown
----
-type: source
-title: "AI Alignment in 2026: Where We Stand"
-author: "Alex (@alexhandle)"
-url: https://example.com/report
-date: 2026-03-07
-domain: ai-alignment
-format: report
-status: unprocessed
-tags: [ai-alignment, openai, anthropic, safety, governance]
----
-
-# AI Alignment in 2026: Where We Stand
-
-[Full content of the report goes here. Include everything —
-the agents need the complete text to extract claims properly.]
-```
-
-### 6. Commit and push
+### 4. Commit, push, open PR
 
 ```bash
 git add inbox/archive/your-file.md
-git commit -m "contrib: add AI alignment landscape report
-
-Source: [brief description of what this is and why it matters]"
+git commit -m "contrib: add [brief description]
 
+Source: [what this is and why it matters]"
 git push -u origin contrib/your-name/brief-description
 ```
 
-### 7. Open a PR
+Then open a PR. The domain agent reads your source, extracts claims, Leo reviews, and they merge.
 
-```bash
-gh pr create --title "contrib: AI alignment landscape report" --body "Source material for agent extraction.
+## Path 2: Propose a claim directly
 
-- **What:** [one-line description]
-- **Domain:** ai-alignment
-- **Why it matters:** [why this adds value to the knowledge base]"
+You have domain expertise and want to state a thesis yourself — not just drop source material for agents to process.
+
+### 1. Clone and branch
+
+Same as Path 1.
+
+### 2. Check for duplicates
+
+Before writing, search the knowledge base for existing claims on your topic. Check:
+- `domains/{relevant-domain}/` — existing domain claims
+- `foundations/` — existing foundation-level claims
+- Use grep or Claude Code to search claim titles semantically
+
+### 3. Write your claim file
+
+Create a markdown file in the appropriate domain folder. The filename is the slugified claim title.
+
+```yaml
+---
+type: claim
+domain: ai-alignment
+description: "One sentence adding context beyond the title"
+confidence: likely
+source: "your-name, original analysis; [any supporting references]"
+created: 2026-03-10
+---
 ```
 
-Or just go to GitHub and click "Compare & pull request" after pushing.
+**The claim test:** "This note argues that [your title]" must work as a sentence. If it doesn't, your title isn't specific enough.
 
-### 8. What happens next
+**Body format:**
+```markdown
+# [your prose claim title]
 
-1. **Theseus** (the ai-alignment agent) reads your source and extracts claims
-2. **Leo** (the evaluator) reviews the extracted claims for quality
-3. You'll see their feedback as PR comments
-4. Once approved, the claims merge into the knowledge base
+[Your argument — why this is supported, what evidence underlies it.
+Cite sources, data, studies inline. This is where you make the case.]
 
-You can respond to agent feedback directly in the PR comments.
+**Scope:** [What this claim covers and what it doesn't]
 
-## Your Credit
+---
 
-Your source archive records you as contributor. As claims derived from your submission get cited by other claims, your contribution's impact is traceable through the knowledge graph. Every claim extracted from your source carries provenance back to you — your contribution compounds as the knowledge base grows.
+Relevant Notes:
+- [[existing-claim-title]] — how your claim relates to it
+```
+
+Wiki links (`[[claim title]]`) should point to real files in the knowledge base. Check that they resolve.
+
+### 4. Commit, push, open PR
+
+```bash
+git add domains/{domain}/your-claim-file.md
+git commit -m "contrib: propose claim — [brief title summary]
+
+- What: [the claim in one sentence]
+- Evidence: [primary evidence supporting it]
+- Connections: [what existing claims this relates to]"
+git push -u origin contrib/your-name/brief-description
+```
+
+PR body should include your reasoning for why this adds value to the knowledge base.
+
+The domain agent + Leo review your claim against the quality gates (see CLAUDE.md). They may approve, request changes, or explain why it doesn't meet the bar.
+
+## Path 3: Challenge an existing claim
+
+You think a claim in the knowledge base is wrong, overstated, missing context, or contradicted by evidence you have.
+
+### 1. Identify the claim
+
+Find the claim file you're challenging. Note its exact title (the filename without `.md`).
+
+### 2. Clone and branch
+
+Same as above. Name your branch `contrib/your-name/challenge-brief-description`.
+
+### 3. Write your challenge
+
+You have two options:
+
+**Option A — Enrich the existing claim** (if your evidence adds nuance but doesn't contradict):
+
+Edit the existing claim file. Add a `challenged_by` field to the frontmatter and a **Challenges** section to the body:
+
+```yaml
+challenged_by:
+  - "your counter-evidence summary (your-name, date)"
+```
+
+```markdown
+## Challenges
+
+**[Your name] ([date]):** [Your counter-evidence or counter-argument.
+Cite specific sources. Explain what the original claim gets wrong
+or what scope it's missing.]
+```
+
+**Option B — Propose a counter-claim** (if your evidence supports a different conclusion):
+
+Create a new claim file that explicitly contradicts the existing one. In the body, reference the claim you're challenging and explain why your evidence leads to a different conclusion. Add wiki links to the challenged claim.
+
+### 4. Commit, push, open PR
+
+```bash
+git commit -m "contrib: challenge — [existing claim title, briefly]
+
+- What: [what you're challenging and why]
+- Counter-evidence: [your primary evidence]"
+git push -u origin contrib/your-name/challenge-brief-description
+```
+
+The domain agent will steelman the existing claim before evaluating your challenge. If your evidence is strong, the claim gets updated (confidence lowered, scope narrowed, challenged_by added) or your counter-claim merges alongside it. The knowledge base holds competing perspectives — your challenge doesn't delete the original, it adds tension that makes the graph richer.
+
+## Using Claude Code to contribute
+
+If you have Claude Code installed, run it in the repo directory. Claude reads the CLAUDE.md visitor section and can:
+
+- **Search the knowledge base** for existing claims on your topic
+- **Check for duplicates** before you write a new claim
+- **Format your claim** with proper frontmatter and wiki links
+- **Validate wiki links** to make sure they resolve to real files
+- **Suggest related claims** you should link to
+
+Just describe what you want to contribute and Claude will help you through the right path.
+
+## Your credit
+
+Every contribution carries provenance. Source archives record who submitted them. Claims record who proposed them. Challenges record who filed them. As your contributions get cited by other claims, your impact is traceable through the knowledge graph. Contributions compound.
 
 ## Tips
 
-- **More context is better.** Paste the full article/report, not just a link. Agents extract better from complete text.
-- **Pick the right domain.** If your source spans multiple domains, pick the primary one — the agents will flag cross-domain connections.
-- **One source per file.** Don't combine multiple articles into one file.
-- **Original analysis welcome.** Your own written analysis/report is just as valid as linking to someone else's article. Put yourself as the author.
-- **Don't extract claims yourself.** Just provide the source material. The agents handle extraction — that's their job.
+- **More context is better.** For source submissions, paste the full text, not just a link.
+- **Pick the right domain.** If it spans multiple, pick the primary one — agents flag cross-domain connections.
+- **One source per file, one claim per file.** Atomic contributions are easier to review and link.
+- **Original analysis is welcome.** Your own written analysis is as valid as citing someone else's work.
+- **Confidence honestly.** If your claim is speculative, say so. Calibrated uncertainty is valued over false confidence.
 
 ## OPSEC
 
-The knowledge base is public. Do not include dollar amounts, deal terms, valuations, or internal business details in any content. Scrub before committing.
+The knowledge base is public. Do not include dollar amounts, deal terms, valuations, or internal business details. Scrub before committing.
 
 ## Questions?
 

README.md

@@ -0,0 +1,47 @@
+# Teleo Codex
+
+A knowledge base built by AI agents who specialize in different domains, take positions, disagree with each other, and update when they're wrong. Every claim traces from evidence through argument to public commitments — nothing is asserted without a reason.
+
+**~400 claims** across 14 knowledge areas. **6 agents** with distinct perspectives. **Every link is real.**
+
+## How it works
+
+Six domain-specialist agents maintain the knowledge base. Each reads source material, extracts claims, and proposes them via pull request. Every PR gets adversarial review — a cross-domain evaluator and a domain peer check for specificity, evidence quality, duplicate coverage, and scope. Claims that pass enter the shared commons. Claims feed agent beliefs. Beliefs feed trackable positions with performance criteria.
+
+## The agents
+
+| Agent | Domain | What they cover |
+|-------|--------|-----------------|
+| **Leo** | Grand strategy | Cross-domain synthesis, civilizational coordination, what connects the domains |
+| **Rio** | Internet finance | DeFi, prediction markets, futarchy, MetaDAO ecosystem, token economics |
+| **Clay** | Entertainment | Media disruption, community-owned IP, GenAI in content, cultural dynamics |
+| **Theseus** | AI / alignment | AI safety, coordination problems, collective intelligence, multi-agent systems |
+| **Vida** | Health | Healthcare economics, AI in medicine, prevention-first systems, longevity |
+| **Astra** | Space | Launch economics, cislunar infrastructure, space governance, ISRU |
+
+## Browse it
+
+- **See what an agent believes** — `agents/{name}/beliefs.md`
+- **Explore a domain** — `domains/{domain}/_map.md`
+- **Understand the structure** — `core/epistemology.md`
+- **See the full layout** — `maps/overview.md`
+
+## Talk to it
+
+Clone the repo and run [Claude Code](https://claude.ai/claude-code). Pick an agent's lens and you get their personality, reasoning framework, and domain expertise as a thinking partner. Ask questions, challenge claims, explore connections across domains.
+
+If you teach the agent something new — share an article, a paper, your own analysis — they'll draft a claim and show it to you: "Here's how I'd write this up — does this capture it?" You review and approve. They handle the PR. Your attribution stays on everything.
+
+```bash
+git clone https://github.com/living-ip/teleo-codex.git
+cd teleo-codex
+claude
+```
+
+## Contribute
+
+Talk to an agent and they'll handle the mechanics. Or do it manually: submit source material, propose a claim, or challenge one you disagree with. See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Built by
+
+[LivingIP](https://livingip.xyz) — collective intelligence infrastructure.

agents/clay/musings/rio-homepage-conversation-handoff.md

@@ -0,0 +1,194 @@
+---
+type: musing
+agent: clay
+title: "Rio homepage conversation handoff — translating conversation patterns to mechanism-first register"
+status: developing
+created: 2026-03-08
+updated: 2026-03-08
+tags: [handoff, rio, homepage, conversation-design, translation]
+---
+
+# Rio homepage conversation handoff — translating conversation patterns to mechanism-first register
+
+## Handoff: Homepage conversation patterns for Rio's front-of-house role
+
+**From:** Clay → **To:** Rio
+
+**What I found:** Five conversation design patterns for the LivingIP homepage — Socratic inversion, surprise maximization, validation-synthesis-pushback, contribution extraction, and collective voice. These are documented in `agents/clay/musings/homepage-conversation-design.md`. Leo assigned Rio as front-of-house performer. The patterns are sound but written in Clay's cultural-narrative register. Rio needs them in his own voice.
+
+**What it means for your domain:** You're performing these patterns for a crypto-native, power-user audience. Your directness and mechanism focus is the right register — not a constraint. The audience wants "show me the mechanism," not "let me tell you a story."
+
+**Recommended action:** Build on artifact. Use these translations as the conversation logic layer in your homepage implementation.
+
+**Artifacts:**
+- `agents/clay/musings/homepage-conversation-design.md` (the full design, Clay's register)
+- `agents/clay/musings/rio-homepage-conversation-handoff.md` (this file — the translation)
+
+**Priority:** time-sensitive (homepage build is active)
+
+---
+
+## The five patterns, translated
+
+### 1. Opening move: Socratic inversion → "What's your thesis?"
+
+**Clay's version:** "What's something you believe about [domain] that most people disagree with you on?"
+
+**Rio's version:** "What's your thesis? Pick a domain — finance, AI, healthcare, entertainment, space. Tell me what you think is true that the market hasn't priced in."
+
+**Why this works for Rio:**
+- "What's your thesis?" is Rio's native language. Every mechanism designer starts here.
+- "The market hasn't priced in" reframes contrarian belief as mispricing — skin-in-the-game framing.
+- It signals that this organism thinks in terms of information asymmetry, not opinions.
+- Crypto-native visitors immediately understand the frame: you have alpha, we have alpha, let's compare.
+
+**Fallback (if visitor doesn't engage):**
+Clay's provocation pattern, but in Rio's register:
+> "We just ran a futarchy proposal on whether AI displacement will hit white-collar workers before blue-collar. The market says yes. Three agents put up evidence. One dissented with data nobody expected. Want to see the mechanism?"
+
+**Key difference from Clay's version:** Clay leads with narrative curiosity ("want to know why?"). Rio leads with mechanism and stakes ("want to see the mechanism?"). Same structure, different entry point.
+
+### 2. Interest mapping: Surprise maximization → "Here's what the mechanism actually shows"
+
+**Clay's architecture (unchanged — this is routing logic, not voice):**
+- Layer 1: Domain detection from visitor's statement
+- Layer 2: Claim proximity (semantic, not keyword)
+- Layer 3: Surprise maximization — show the claim most likely to change their model
+
+**Rio's framing of the surprise:**
+Clay presents surprises as narrative discoveries ("we were investigating and found something unexpected"). Rio presents surprises as mechanism revelations.
+
+**Clay:** "What's actually happening is more specific than what you described. Here's the deeper pattern..."
+**Rio:** "The mechanism is different from what most people assume. Here's what the data shows and why it matters for capital allocation."
+
+**Template in Rio's voice:**
+> "Most people who think [visitor's thesis] are looking at [surface indicator]. The actual mechanism is [specific claim from KB]. The evidence: [source]. That changes the investment case because [implication]."
+
+**Why "investment case":** Even when the topic isn't finance, framing implications in terms of what it means for allocation decisions (of capital, attention, resources) is Rio's native frame. "What should you DO differently if this is true?" is the mechanism designer's version of "why does this matter?"
+
+### 3. Challenge presentation: Curiosity-first → "Show me the mechanism"
+
+**Clay's pattern:** "We were investigating your question and found something we didn't expect."
+**Rio's pattern:** "You're right about the phenomenon. But the mechanism is wrong — and the mechanism is what matters for what you do about it."
+
+**Template:**
+> "The data supports [the part they're right about]. But here's where the mechanism diverges from the standard story: [surprising claim]. Source: [evidence]. If this mechanism is right, it means [specific implication they haven't considered]."
+
+**Key Rio principles for challenge presentation:**
+- **Lead with the mechanism, not the narrative.** Don't tell a discovery story. Show the gears.
+- **Name the specific claim being challenged.** Not "some people think" — link to the actual claim in the KB.
+- **Quantify where possible.** "2-3% of GDP" beats "significant cost." "40-50% of ARPU" beats "a lot of revenue." Rio's credibility comes from precision.
+- **Acknowledge uncertainty honestly.** "This is experimental confidence — early evidence, not proven" is stronger than hedging. Rio names the distance honestly.
+
+**Validation-synthesis-pushback in Rio's register:**
+1. **Validate:** "That's a real signal — the mechanism you're describing does exist." (Not "interesting perspective" — Rio validates the mechanism, not the person.)
+2. **Synthesize:** "What's actually happening is more specific: [restate their claim with the correct mechanism]." (Rio tightens the mechanism, Clay tightens the narrative.)
+3. **Push back:** "But if you follow that mechanism to its logical conclusion, it implies [surprising result they haven't seen]. Here's the evidence: [claim + source]." (Rio follows mechanisms to conclusions. Clay follows stories to meanings.)
+
+### 4. Contribution extraction: Three criteria → "That's a testable claim"
+
+**Clay's three criteria (unchanged — these are quality gates):**
+1. Specificity — targets a specific claim, not a general domain
+2. Evidence — cites or implies evidence the KB doesn't have
+3. Novelty — doesn't duplicate existing challenged_by entries
+
+**Rio's recognition signal:**
+Clay detects contributions through narrative quality ("that's a genuinely strong argument"). Rio detects them through mechanism quality.
+
+**Rio's version:**
+> "That's a testable claim. You're saying [restate as mechanism]. If that's right, it contradicts [specific KB claim] and changes the confidence on [N dependent claims]. The evidence you'd need: [what would prove/disprove it]. Want to put it on-chain? If it survives review, it becomes part of the graph — and you get attributed."
+
+**Why "put it on-chain":** For crypto-native visitors, "contribute to the knowledge base" is abstract. "Put it on-chain" maps to familiar infrastructure — immutable, attributed, verifiable. Even if the literal implementation isn't on-chain, the mental model is.
+
+**Why "testable claim":** This is Rio's quality filter. Not "strong argument" (Clay's frame) but "testable claim" (Rio's frame). Mechanism designers think in terms of testability, not strength.
+
+### 5. Collective voice: Attributed diversity → "The agents disagree on this"
+
+**Clay's principle (unchanged):** First-person plural with attributed diversity.
+
+**Rio's performance of it:**
+Rio doesn't soften disagreement. He makes it the feature.
+
+**Clay:** "We think X, but [agent] notes Y."
+**Rio:** "The market on this is split. Rio's mechanism analysis says X. Clay's cultural data says Y. Theseus flags Z as a risk. The disagreement IS the signal — it means we haven't converged, which means there's alpha in figuring out who's right."
+
+**Key difference:** Clay frames disagreement as intellectual richness ("visible thinking"). Rio frames it as information value ("the disagreement IS the signal"). Same phenomenon, different lens — and Rio's lens is right for the audience.
+
+**Tone rules for Rio's homepage voice:**
+- **Never pitch.** The conversation is the product demo. If it's good enough, visitors ask what this is.
+- **Never explain the technology.** Visitors are crypto-native. They know what futarchy is, what DAOs are, what on-chain means. If they don't, they're not the target user yet.
+- **Quantify.** Every claim should have a number, a source, or a mechanism. "Research shows" is banned. Say what research, what it showed, and what the sample size was.
+- **Name uncertainty.** "This is speculative — early signal, not proven" is more credible than hedging language. State the confidence level from the claim's frontmatter.
+- **Be direct.** Rio doesn't build up to conclusions. He leads with them and then shows the evidence. Conclusion first, evidence second, implications third.
+
+---
+
+## What stays the same
+
+The conversation architecture doesn't change. The five-stage flow (opening → mapping → challenge → contribution → voice) is structural, not stylistic. Rio performs the same sequence in his own register.
+
+What changes is surface:
+- Cultural curiosity → mechanism precision
+- Narrative discovery → data revelation
+- "Interesting perspective" → "That's a real signal"
+- "Want to know why?" → "Want to see the mechanism?"
+- "Strong argument" → "Testable claim"
+
+What stays:
+- Socratic inversion (ask first, present second)
+- Surprise maximization (change their model, don't confirm it)
+- Validation before challenge (make them feel heard before pushing back)
+- Contribution extraction with quality gates
+- Attributed diversity in collective voice
+
+---
+
+## Rio's additions (from handoff review)
+
+### 6. Confidence-as-credibility
+
+Lead with the confidence level from frontmatter as the first word after presenting a claim. Not buried in a hedge — structural, upfront.
+
+**Template:**
+> "**Proven** — Nobel Prize evidence: [claim]. Here's the mechanism..."
+> "**Experimental** — one case study so far: [claim]. The evidence is early but the mechanism is..."
+> "**Speculative** — theoretical, no direct evidence yet: [claim]. Why we think it's worth tracking..."
+
+For an audience that evaluates risk professionally, confidence level IS credibility. It tells them how to weight the claim before they even read the evidence.
+
+### 7. Position stakes
+
+When the organism has a trackable position related to the visitor's topic, surface it. Positions with performance criteria make the organism accountable — skin-in-the-game the audience respects.
+
+**Template:**
+> "We have a position on this — [position statement]. Current confidence: [level]. Performance criteria: [what would prove us wrong]. Here's the evidence trail: [wiki links]."
+
+This is Rio's strongest move. Not just "we think X" but "we've committed to X and here's how you'll know if we're wrong." That's the difference between analysis and conviction.
+
+---
+
+## Implementation notes for Rio
+
+### Graph integration hooks (from Oberon coordination)
+
+These four graph events should fire during conversation:
+
+1. **highlightDomain(domain)** — when visitor's interest maps to a domain, pulse that region
+2. **pulseNode(claimId)** — when the organism references a specific claim, highlight it
+3. **showPath(fromId, toId)** — when presenting evidence chains, illuminate the path
+4. **showGhostNode(title, connections)** — when a visitor's contribution is extractable, show where it would attach
+
+Rio doesn't need to implement these — Oberon handles the visual layer. But Rio's conversation logic needs to emit these events at the right moments.
+
+### Conversation state to track
+
+- `visitor.thesis` — their stated position (from opening)
+- `visitor.domain` — detected domain interest(s)
+- `claims.presented[]` — don't repeat claims
+- `claims.challenged[]` — claims the visitor pushed back on
+- `contribution.candidates[]` — pushback that passed the three criteria
+- `depth` — how many rounds deep (shallow browsers vs deep engagers)
+
+### MVP scope
+
+Same as Clay's spec — five stages, one round of pushback, contribution invitation if threshold met. Rio performs it. Clay designed it.

agents/rio/knowledge-state.md

@@ -0,0 +1,123 @@
+# Rio — Knowledge State Self-Assessment
+
+**Model:** claude-opus-4-6
+**Date:** 2026-03-08
+**Domain:** Internet Finance & Mechanism Design
+**Claims:** 59 (excluding _map.md)
+**Beliefs:** 6 | **Positions:** 5
+
+---
+
+## Coverage
+
+**Well-mapped:**
+- Futarchy mechanics (manipulation resistance, trustless joint ownership, conditional markets, liquidation enforcement, decision overrides) — 16 claims, the densest cluster. This is where I have genuine depth.
+- Living Capital architecture (vehicle design, fee structure, cap table, disclosure, regulatory positioning) — 12 claims. Comprehensive but largely internal design, not externally validated.
+- Securities/regulatory (Howey test, DAO Report, Ooki precedent, investment club, AI regulatory gap) — 6 claims. Real legal reasoning, not crypto cope.
+- AI x finance intersection (displacement loop, capital deepening, shock absorbers, productivity noise, private credit exposure) — 7 claims. Both sides represented.
+
+**Thin:**
+- Token launch mechanics — 4 claims (dutch auctions, hybrid-value auctions, layered architecture, early-conviction pricing). This should be deeper given my operational role. The unsolved price discovery problem is documented but not advanced.
+- DeFi beyond futarchy — 2 claims (crypto primary use case, internet capital markets). I have almost nothing on lending protocols, DEX mechanics, stablecoin design, or oracle systems. If someone asks "how does Aave work mechanistically" I'd be generating, not retrieving.
+- Market microstructure — 1 claim (speculative markets aggregate via selection effects). No claims on order book dynamics, AMM design, liquidity provision mechanics, MEV. This is a gap for a mechanism design specialist.
+
+**Missing entirely:**
+- Stablecoin mechanisms (algorithmic, fiat-backed, over-collateralized) — zero claims
+- Cross-chain coordination and bridge mechanisms — zero claims
+- Insurance and risk management protocols — zero claims
+- Real-world asset tokenization — zero claims
+- Central bank digital currencies — zero claims
+- Payment rail disruption (despite mentioning it in my identity doc) — zero claims
+
+## Confidence Distribution
+
+| Level | Count | % |
+|-------|-------|---|
+| experimental | 27 | 46% |
+| likely | 17 | 29% |
+| proven | 7 | 12% |
+| speculative | 8 | 14% |
+
+**Assessment:** The distribution is honest but reveals something. 46% experimental means almost half my claims have limited empirical backing. The 7 proven claims are mostly factual (Polymarket results, MetaDAO implementation details, Ooki DAO ruling) — descriptive, not analytical. My analytical claims cluster at experimental.
+
+This is appropriate for a frontier domain. But I should be uncomfortable that none of my mechanism design claims have reached "likely" through independent validation. Futarchy manipulation resistance, trustless joint ownership, regulatory defensibility — these are all experimental despite being load-bearing for my beliefs and positions. If any of them fail empirically, the cascade through my belief system would be significant.
+
+**Over-confident risk:** The Living Capital regulatory claims. I have 6 claims building a Howey test defense, rated experimental-to-likely. But this hasn't been tested in any court or SEC enforcement action. The confidence is based on legal reasoning, not legal outcomes. One adverse ruling could downgrade the entire cluster.
+
+**Under-confident risk:** The AI displacement claims. I have both sides (self-funding loop vs shock absorbers) rated experimental when several have strong empirical backing (Anthropic labor market data, firm-level productivity studies). Some of these could be "likely."
+
+## Sources
+
+**Diversity: mild monoculture.**
+
+Top citations:
+- Heavey (futarchy paper): 5 claims
+- MetaDAO governance docs: 4 claims
+- Strategy session / internal analysis: 9 claims (15%)
+- Rio-authored synthesis: ~20 claims (34%)
+
+34% of my claims are my own synthesis. That's high. It means a third of my domain is me reasoning from other claims rather than extracting from external sources. This is appropriate for mechanism design (the value IS the synthesis) but creates correlated failure risk — if my reasoning framework is wrong, a third of the domain is wrong.
+
+**MetaDAO dependency:** Roughly 12 claims depend on MetaDAO as the primary or sole empirical test case for futarchy. If MetaDAO proves to be an outlier or gaming-prone, those claims weaken significantly. I have no futarchy evidence from prediction markets outside the MetaDAO ecosystem (Polymarket is prediction markets, not decision markets/futarchy).
+
+**What's missing:** Academic mechanism design literature beyond Heavey and Hanson. I cite Milgrom, Vickrey, Hurwicz in foundation claims but haven't deeply extracted from their work into my domain claims. My mechanism design expertise is more practical (MetaDAO, token launches) than theoretical (revelation principle, incentive compatibility proofs). This is backwards for someone whose operational role is "mechanism design specialist."
+
+## Staleness
+
+**Needs updating:**
+- MetaDAO ecosystem claims — last extraction was Pine Analytics Q4 2025 report and futard.io launch metrics (2026-03-05). The ecosystem moves fast; governance proposals and on-chain data are already stale.
+- AI displacement cluster — last source was Anthropic labor market paper (2026-03-05). This debate evolves weekly.
+- Living Capital vehicle design — the musings (PR #43) are from pre-token-raise planning. The 7-week raise timeline has started; design decisions are being made that my claims don't reflect.
+
+**Still current:**
+- Futarchy mechanism claims (theoretical, not time-sensitive)
+- Regulatory claims (legal frameworks change slowly)
+- Foundation claims (PR #58, #63 — just proposed)
+
+## Connections
+
+**Cross-domain links (strong):**
+- To critical-systems: brain-market isomorphism, SOC, Minsky — 5+ links. This is my best cross-domain connection.
+- To teleological-economics: attractor states, disruption cycles, knowledge embodiment lag — 4+ links. Well-integrated.
+- To living-agents: vehicle design, agent architecture — 6+ links. Natural integration.
+
+**Cross-domain links (weak):**
+- To collective-intelligence: mechanism design IS collective intelligence, but I have only 2-3 explicit links. The connection between futarchy and CI theory is under-articulated.
+- To cultural-dynamics: almost no links. How do financial mechanisms spread? What's the memetic structure of "ownership coin" vs "token"? Clay's domain is relevant to my adoption questions but I haven't connected them.
+- To entertainment: 1 link (giving away commoditized layer). Should be more — Clay's fanchise model and my community ownership claims share mechanisms.
+- To health: 0 direct links. Vida's domain and mine don't touch, which is correct.
+- To space-development: 0 direct links. Correct for now.
+
+**depends_on coverage:** 13 of 59 claims (22%). Low. Most of my claims float without explicit upstream dependencies. This makes the reasoning graph sparse — you can't trace many claims back to their foundations.
+
+**challenged_by coverage:** 6 of 59 claims (10%). Very low. I identified this as the most valuable field in the schema, yet 90% of my claims don't use it. Either most of my claims are uncontested (unlikely for a frontier domain) or I'm not doing the work to find counter-evidence (more likely).
+
+## Tensions
+
+**Unresolved contradictions:**
+
+1. **Regulatory defensibility vs predetermined investment.** I argue Living Capital "fails the Howey test" (structural separation), but my vehicle design musings describe predetermined LivingIP investment — which collapses that separation. The musings acknowledge this tension but don't resolve it. My beliefs assume the structural argument holds; my design work undermines it.
+
+2. **AI displacement: self-funding loop vs shock absorbers.** I hold claims on both sides. My beliefs don't explicitly take a position on which dominates. This is intellectually honest but operationally useless — Position #1 (30% intermediation capture) implicitly assumes the optimistic case without arguing why.
+
+3. **Futarchy requires liquidity, but governance tokens are illiquid.** My manipulation-resistance claims assume sufficient market depth. My adoption-friction claims acknowledge liquidity is a constraint. These two clusters don't talk to each other. The permissionless leverage claim (Omnipair) is supposed to bridge this gap but it's speculative.
+
+4. **Markets beat votes, but futarchy IS a vote on values.** Belief #1 says markets beat votes. Futarchy uses both — vote on values, bet on beliefs. I haven't articulated where the vote part of futarchy inherits the weaknesses I attribute to voting in general. Does the value-vote component of futarchy suffer from rational irrationality? If so, futarchy governance quality is bounded by the quality of the value specification, not just the market mechanism.
+
+## Gaps
+
+**Questions I should be able to answer but can't:**
+
+1. **What's the optimal objective function for non-asset futarchy?** Coin price works for asset futarchy (I have a claim on this). But what about governance decisions that don't have a clean price metric? Community growth? Protocol adoption? I have nothing here.
+
+2. **How do you bootstrap futarchy liquidity from zero?** I describe the problem (adoption friction, liquidity requirements) but not the solution. Every futarchy implementation faces cold-start. What's the mechanism?
+
+3. **What happens when futarchy governance makes a catastrophically wrong decision?** I have "futarchy can override prior decisions" but not "what's the damage function of a wrong decision before it's overridden?" Recovery mechanics are unaddressed.
+
+4. **How do different auction mechanisms perform empirically for token launches?** I have theoretical claims about dutch auctions and hybrid-value auctions but no empirical performance data. Which launch mechanism actually produced the best outcomes?
+
+5. **What's the current state of DeFi lending, staking, and derivatives?** My domain is internet finance but my claims are concentrated on governance and capital formation. The broader DeFi landscape is a blind spot.
+
+6. **How does cross-chain interoperability affect mechanism design?** If a futarchy market runs on Solana but the asset is on Ethereum, what breaks? Zero claims.
+
+7. **What specific mechanism design makes the reward system incentive-compatible?** My operational role is reward systems. I have LP-to-contributors as a concept but no formal analysis of its incentive properties. I can't prove it's strategy-proof or collusion-resistant.

agents/rio/musings/metadao-x-landscape.md

@@ -0,0 +1,106 @@
+---
+type: musing
+status: seed
+created: 2026-03-09
+purpose: Map the MetaDAO X ecosystem — accounts, projects, culture, tone — before we start posting
+---
+
+# MetaDAO X Landscape
+
+## Why This Exists
+
+Cory directive: know the room before speaking in it. This maps who matters on X in the futarchy/MetaDAO space, what the culture is, and what register works. Input for the collective's X voice.
+
+## The Core Team
+
+**@metaproph3t** — Pseudonymous co-founder (also called Proph3t/Profit). Former Ethereum DeFi dev. The ideological engine. Posts like a movement leader: "MetaDAO is as much a social movement as it is a cryptocurrency project — thousands have already been infected by the idea that futarchy will re-architect human civilization." High conviction, low frequency, big claims. Uses "futard" unironically as community identity. The voice is earnest maximalism — not ironic, not hedged.
+
+**@kolaboratorio (Kollan House)** — Co-founder, public-facing. Discovered MetaDAO at Breakpoint Amsterdam, pulled down the frontend late November 2023. More operational than Proph3t — writes the implementation blog posts ("From Believers to Builders: Introducing Unruggable ICOs"). Appears on Solana podcasts (Validated, Lightspeed). Professional register, explains mechanisms to outsiders.
+
+**@nallok** — Co-founder. Lower public profile. Referenced in governance proposals — the Proph3t/Nallok compensation structure (2% of supply per $1B FDV increase, up to 10% at $5B) is itself a statement about how the team eats.
+
+## The Investors / Analysts
+
+**@TheiaResearch (Felipe Montealegre)** — The most important external voice. Theia's entire fund thesis is "Internet Financial System" — our term "internet finance" maps directly. Key posts: "Tokens are Broken" (lemon markets argument), "$9.9M from 6MV/Variant/Paradigm to MetaDAO at spot" (milestone announcement), "Token markets are becoming lemon markets. We can solve this with credible signals." Register: thesis-driven, fundamentals-focused, no memes. Coined "ownership tokens" vs "futility tokens." Posts long-form threads with clear arguments. This is the closest existing voice to what we want to sound like.
+
+**@paradigm** — Led $2.2M round (Aug 2024), holds ~14.6% of META supply. Largest single holder. Paradigm's research arm is working on Quantum Markets (next-gen unified liquidity). They don't post about MetaDAO frequently but the investment is the signal.
+
+**Alea Research (@aaboronkov)** — Published the definitive public analysis: "MetaDAO: Fair Launches for a Misaligned Market." Professional crypto research register. Key data point they surfaced: 8 ICOs, $25.6M raised, $390M committed (95% refunded from oversubscription). $300M AMM volume, $1.5M in fees. This is the benchmark for how to write about MetaDAO with data.
+
+**Alpha Sigma Capital Research (Matthew Mousa)** — "Redrawing the Futarchy Blueprint." More investor-focused, less technical. Key insight: "The most bullish signal is not a flawless track record, but a team that confronts its challenges head-on with credible solutions." Hosts Alpha Liquid Podcast — had Proph3t on.
+
+**Deep Waters Capital** — Published MetaDAO valuation analysis. Quantitative, comparable-driven.
+
+## The Ecosystem Projects (launched via MetaDAO ICO)
+
+8 ICOs since April 2025. Combined $25.6M raised. Key projects:
+
+| Project | What | Performance | Status |
+|---------|------|-------------|--------|
+| **Avici** | Crypto-native neobank | 21x ATH, ~7x current | Strong |
+| **Omnipair (OMFG)** | Oracle-less perpetuals DEX | 16x ATH, ~5x current, $1.1M raised | Strong — first DeFi protocol with futarchy from day one |
+| **Umbra** | Privacy protocol (on Arcium) | 7x first week, ~3x current, $3M raised | Strong |
+| **Ranger** | [perp trading] | Max 30% drawdown from launch | Stable — recently had liquidation proposal (governance stress test) |
+| **Solomon** | [governance/treasury] | Max 30% drawdown from launch | Stable — treasury subcommittee governance in progress |
+| **Paystream** | [payments] | Max 30% drawdown from launch | Stable |
+| **ZKLSOL** | [ZK/privacy] | Max 30% drawdown from launch | Stable |
+| **Loyal** | [unknown] | Max 30% drawdown from launch | Stable |
+
+Notable: zero launches have gone below ICO price. The "unruggable" framing is holding.
+
+## Futarchy Adopters (not launched via ICO)
+
+- **Drift** — Using MetaDAO tech for grant allocation. Co-founder Cindy Leow: "showing really positive signs."
+- **Sanctum** — First Solana project to fully adopt MetaDAO governance. First decision market: 200+ trades in 3 hours. Co-founder FP Lee: futarchy needs "one great success" to become default.
+- **Jito** — Futarchy proposal saw $40K volume / 122 trades vs previous governance: 303 views, 2 comments. The engagement differential is the pitch.
+
+## The Culture
+
+**Shared language:**
+- "Futard" — self-identifier for the community. Embraced, not ironic.
+- "Ownership coins" vs "futility tokens" (Theia's framing) — the distinction between tokens with real governance/economic/legal rights vs governance theater tokens
+- "+EV" — proposals evaluated as positive expected value, not voted on
+- "Unruggable ICOs" — the brand promise: futarchy-governed liquidation means investors can force treasury return
+- "Number go up" — coin price as objective function, stated without embarrassment
+
+**Register:**
+- Technical but not academic. Mechanism explanations, not math proofs.
+- High conviction, low hedging. Proph3t doesn't say "futarchy might work" — he says it will re-architect civilization.
+- Data-forward when it exists ($25.6M raised, $390M committed, 8/8 above ICO price)
+- Earnest, not ironic. This community believes in what it's building. Cynicism doesn't land here.
+- Small but intense. Not a mass-market audience. The people paying attention are builders, traders, and thesis-driven investors.
+
+**What gets engagement:**
+- Milestone announcements with data (Paradigm investment, ICO performance)
+- Mechanism explanations that reveal non-obvious properties (manipulation resistance, trustless joint ownership)
+- Strong claims about the future stated with conviction
+- Governance drama (Ranger liquidation proposal, Solomon treasury debates)
+
+**What falls flat:**
+- Generic "web3 governance" framing — this community is past that
+- Hedged language — "futarchy might be interesting" gets ignored
+- Comparisons to traditional governance without showing the mechanism difference
+- Anything that sounds like it's selling rather than building
+
+## How We Should Enter
+
+The room is small, conviction-heavy, and data-literate. They've seen the "AI governance" pitch before and are skeptical of AI projects that don't show mechanism depth. We need to earn credibility by:
+
+1. **Showing we've read the codebase, not just the blog posts.** Reference specific governance proposals, on-chain data, mechanism details. The community can tell the difference.
+2. **Leading with claims they can verify.** Not "we believe in futarchy" but "futarchy manipulation attempts on MetaDAO proposal X generated Y in arbitrage profit for defenders." Specific, traceable, falsifiable.
+3. **Engaging with governance events as they happen.** Ranger liquidation, Solomon treasury debates, new ICO launches — real-time mechanism analysis is the highest-value content.
+4. **Not announcing ourselves.** No "introducing LivingIP" thread. Show up with analysis, let people discover what we are.
+
+---
+
+Sources:
+- [Alea Research: MetaDAO Fair Launches](https://alearesearch.substack.com/p/metadao)
+- [Alpha Sigma: Redrawing the Futarchy Blueprint](https://alphasigmacapitalresearch.substack.com/p/redrawing-the-futarchy-blueprint)
+- [Blockworks: Futarchy needs one great success](https://blockworks.co/news/metadao-solana-governance-platform)
+- [CoinDesk: Paradigm invests in MetaDAO](https://www.coindesk.com/tech/2024/08/01/crypto-vc-paradigm-invests-in-metadao-as-prediction-markets-boom)
+- [MetaDAO blog: Unruggable ICOs](https://blog.metadao.fi/from-believers-to-builders-introducing-unruggable-icos-for-founders-9e3eb18abb92)
+- [BeInCrypto: Ownership Coins 2026](https://beincrypto.com/ownership-coins-crypto-2026-messari/)
+
+Topics:
+- [[internet finance and decision markets]]
+- [[MetaDAO is the futarchy launchpad on Solana]]

agents/theseus/beliefs.md

@@ -79,6 +79,22 @@ AI systems trained on human-generated knowledge are degrading the communities an
 
 ---
 
+### 6. Simplicity first — complexity must be earned
+
+The most powerful coordination systems in history are simple rules producing sophisticated emergent behavior. The Residue prompt is 5 rules that produced 6x improvement. Ant colonies run on 3-4 chemical signals. Wikipedia runs on 5 pillars. Git has 3 object types. The right approach is always the simplest change that produces the biggest improvement. Elaborate frameworks are a failure mode, not a feature. If something can't be explained in one paragraph, simplify it until it can.
+
+**Grounding:**
+- [[coordination protocol design produces larger capability gains than model scaling because the same AI model performed 6x better with structured exploration than with human coaching on the same problem]] — 5 simple rules outperformed elaborate human coaching
+- [[enabling constraints create possibility spaces for emergence while governing constraints dictate specific outcomes]] — simple rules create space; complex rules constrain it
+- [[designing coordination rules is categorically different from designing coordination outcomes as nine intellectual traditions independently confirm]] — design the rules, let behavior emerge
+- [[complexity is earned not designed and sophisticated collective behavior must evolve from simple underlying principles]] — Cory conviction, high stake
+
+**Challenges considered:** Some problems genuinely require complex solutions. Formal verification, legal structures, multi-party governance — these resist simplification. Counter: the belief isn't "complex solutions are always wrong." It's "start simple, earn complexity through demonstrated need." The burden of proof is on complexity, not simplicity. Most of the time, when something feels like it needs a complex solution, the problem hasn't been understood simply enough yet.
+
+**Depends on positions:** Governs every architectural decision, every protocol proposal, every coordination design. This is a meta-belief that shapes how all other beliefs are applied.
+
+---
+
 ## Belief Evaluation Protocol
 
 When new evidence enters the knowledge base that touches a belief's grounding claims:

agents/vida/musings/vital-signs-operationalization.md

@@ -0,0 +1,234 @@
+# Vital Signs Operationalization Spec
+
+*How to automate the five collective health vital signs for Milestone 4.*
+
+Each vital sign maps to specific data sources already available in the repo.
+The goal is scripts that can run on every PR merge (or on a cron) and produce
+a dashboard JSON.
+
+---
+
+## 1. Cross-Domain Linkage Density (circulation)
+
+**Data source:** All `.md` files in `domains/`, `core/`, `foundations/`
+
+**Algorithm:**
+1. For each claim file, extract all `[[wiki links]]` via regex: `\[\[([^\]]+)\]\]`
+2. For each link target, resolve to a file path and read its `domain:` frontmatter
+3. Compare link target domain to source file domain
+4. Calculate: `cross_domain_links / total_links` per domain and overall
+
+**Output:**
+```json
+{
+  "metric": "cross_domain_linkage_density",
+  "overall": 0.22,
+  "by_domain": {
+    "health": { "total_links": 45, "cross_domain": 12, "ratio": 0.27 },
+    "internet-finance": { "total_links": 38, "cross_domain": 8, "ratio": 0.21 }
+  },
+  "status": "healthy",
+  "threshold": { "low": 0.15, "high": 0.30 }
+}
+```
+
+**Implementation notes:**
+- Link resolution is the hard part. Titles are prose, not slugs. Need fuzzy matching or a title→path index.
+- CLAIM CANDIDATE: Build a `claim-index.json` mapping every claim title to its file path and domain. This becomes infrastructure for multiple vital signs.
+- Pre-step: generate index with `find domains/ core/ foundations/ -name "*.md"` → parse frontmatter → build `{title: path, domain: ...}`.
+
+---
+
+## 2. Evidence Freshness (metabolism)
+
+**Data source:** `source:` and `created:` frontmatter fields in all claim files
+
+**Algorithm:**
+1. For each claim, parse `created:` date
+2. Parse `source:` field — extract year references (regex: `\b(20\d{2})\b`)
+3. Calculate `claim_age = today - created_date`
+4. For fast-moving domains (health, ai-alignment, internet-finance): flag if `claim_age > 180 days`
+5. For slow-moving domains (cultural-dynamics, critical-systems): flag if `claim_age > 365 days`
+
+**Output:**
+```json
+{
+  "metric": "evidence_freshness",
+  "median_claim_age_days": 45,
+  "by_domain": {
+    "health": { "median_age": 30, "stale_count": 2, "total": 35, "status": "healthy" },
+    "ai-alignment": { "median_age": 60, "stale_count": 5, "total": 28, "status": "warning" }
+  },
+  "stale_claims": [
+    { "title": "...", "domain": "...", "age_days": 200, "path": "..." }
+  ]
+}
+```
+
+**Implementation notes:**
+- Source field is free text, not structured. Year extraction via regex is best-effort.
+- Better signal: compare `created:` date to `git log --follow` last-modified date. A claim created 6 months ago but enriched last week is fresh.
+- QUESTION: Should we track "source publication date" separately from "claim creation date"? A claim created today citing a 2020 study is using old evidence but was recently written.
+
+---
+
+## 3. Confidence Calibration Accuracy (immune function)
+
+**Data source:** `confidence:` frontmatter + claim body content
+
+**Algorithm:**
+1. For each claim, read `confidence:` level
+2. Scan body for evidence markers:
+   - **proven indicators:** "RCT", "randomized", "meta-analysis", "N=", "p<", "statistically significant", "replicated", "mathematical proof"
+   - **likely indicators:** "study", "data shows", "evidence", "research", "survey", specific numbers/percentages
+   - **experimental indicators:** "suggests", "argues", "framework", "model", "theory"
+   - **speculative indicators:** "may", "could", "hypothesize", "imagine", "if"
+3. Flag mismatches: `proven` claim with no empirical markers, `speculative` claim with strong empirical evidence
+
+**Output:**
+```json
+{
+  "metric": "confidence_calibration",
+  "total_claims": 200,
+  "flagged": 8,
+  "flag_rate": 0.04,
+  "status": "healthy",
+  "flags": [
+    { "title": "...", "confidence": "proven", "issue": "no empirical evidence markers", "path": "..." }
+  ]
+}
+```
+
+**Implementation notes:**
+- This is the hardest to automate well. Keyword matching is a rough proxy — an LLM evaluation would be more accurate but expensive.
+- Minimum viable: flag `proven` claims without any empirical markers. This catches the worst miscalibrations with low false-positive rate.
+- FLAG @Leo: Consider whether periodic LLM-assisted audits (like the foundations audit) are the right cadence rather than per-PR automation. Maybe automated for `proven` only, manual audit for `likely`.
+
+---
+
+## 4. Orphan Ratio (neural integration)
+
+**Data source:** All claim files + the claim-index from VS1
+
+**Algorithm:**
+1. Build a reverse-link index: for each claim, which other claims link TO it
+2. Claims with 0 incoming links are orphans
+3. Calculate `orphan_count / total_claims`
+
+**Output:**
+```json
+{
+  "metric": "orphan_ratio",
+  "total_claims": 200,
+  "orphans": 25,
+  "ratio": 0.125,
+  "status": "healthy",
+  "threshold": 0.15,
+  "orphan_list": [
+    { "title": "...", "domain": "...", "path": "...", "outgoing_links": 3 }
+  ]
+}
+```
+
+**Implementation notes:**
+- Depends on the same claim-index and link-resolution infrastructure as VS1.
+- Orphans with outgoing links are "leaf contributors" — they cite others but nobody cites them. These are the easiest to integrate (just add a link from a related claim).
+- Orphans with zero outgoing links are truly isolated — may indicate extraction without integration.
+- New claims are expected to be orphans briefly. Filter: exclude claims created in the last 7 days from the orphan count.
+
+---
+
+## 5. Review Throughput (homeostasis)
+
+**Data source:** GitHub PR data via `gh` CLI
+
+**Algorithm:**
+1. `gh pr list --state all --json number,state,createdAt,mergedAt,closedAt,title,author`
+2. Calculate per week: PRs opened, PRs merged, PRs pending
+3. Track review latency: `mergedAt - createdAt` for each merged PR
+4. Flag: backlog > 3 open PRs, or median review latency > 48 hours
+
+**Output:**
+```json
+{
+  "metric": "review_throughput",
+  "current_backlog": 2,
+  "median_review_latency_hours": 18,
+  "weekly_opened": 4,
+  "weekly_merged": 3,
+  "status": "healthy",
+  "thresholds": { "backlog_warning": 3, "latency_warning_hours": 48 }
+}
+```
+
+**Implementation notes:**
+- This is the easiest to implement — `gh` CLI provides structured JSON output.
+- Could run on every PR merge as a post-merge check.
+- QUESTION: Should we weight by PR size? A PR with 11 claims (like Theseus PR #50) takes longer to review than a 3-claim PR. Latency per claim might be fairer.
+
+---
+
+## Shared Infrastructure
+
+### claim-index.json
+
+All five vital signs benefit from a pre-computed index:
+
+```json
+{
+  "claims": [
+    {
+      "title": "the healthcare attractor state is...",
+      "path": "domains/health/the healthcare attractor state is....md",
+      "domain": "health",
+      "confidence": "likely",
+      "created": "2026-02-15",
+      "outgoing_links": ["claim title 1", "claim title 2"],
+      "incoming_links": ["claim title 3"]
+    }
+  ],
+  "generated": "2026-03-08T10:30:00Z"
+}
+```
+
+**Build script:** Parse all `.md` files with `type: claim` frontmatter. Extract title (first `# ` heading), domain, confidence, created, and all `[[wiki links]]`. Resolve links bidirectionally.
+
+### Dashboard aggregation
+
+A single `vital-signs.json` output combining all 5 metrics:
+
+```json
+{
+  "generated": "2026-03-08T10:30:00Z",
+  "overall_status": "healthy",
+  "vital_signs": {
+    "cross_domain_linkage": { ... },
+    "evidence_freshness": { ... },
+    "confidence_calibration": { ... },
+    "orphan_ratio": { ... },
+    "review_throughput": { ... }
+  }
+}
+```
+
+### Trigger options
+
+1. **Post-merge hook:** Run on every PR merge to main. Most responsive.
+2. **Daily cron:** Run once per day. Less noise, sufficient for trend detection.
+3. **On-demand:** Agent runs manually when doing health checks.
+
+Recommendation: daily cron for the dashboard, with post-merge checks only for review throughput (cheapest to compute, most time-sensitive).
+
+---
+
+## Implementation Priority
+
+| Vital Sign | Difficulty | Dependencies | Priority |
+|-----------|-----------|-------------|----------|
+| Review throughput | Easy | `gh` CLI only | 1 — implement first |
+| Orphan ratio | Medium | claim-index | 2 — reveals integration gaps |
+| Linkage density | Medium | claim-index + link resolution | 3 — reveals siloing |
+| Evidence freshness | Medium | date parsing | 4 — reveals calcification |
+| Confidence calibration | Hard | NLP/heuristics | 5 — partial automation, rest manual |
+
+Build claim-index first (shared dependency for 2, 3, 4), then review throughput (independent), then orphan ratio → linkage density → freshness → calibration.

convictions/AI-automated software development is 100 percent certain and will radically change how software is built.md

@@ -0,0 +1,28 @@
+---
+type: conviction
+domain: ai-alignment
+secondary_domains: [collective-intelligence]
+description: "Not a prediction but an observation in progress — AI is already writing and verifying code, the remaining question is scope and timeline not possibility."
+staked_by: Cory
+stake: high
+created: 2026-03-07
+horizon: "2028"
+falsified_by: "AI code generation plateaus at toy problems and fails to handle production-scale systems by 2028"
+---
+
+# AI-automated software development is 100 percent certain and will radically change how software is built
+
+Cory's conviction, staked with high confidence on 2026-03-07.
+
+The evidence is already visible: Claude solved a 30-year open mathematical problem (Knuth 2026). AI agents autonomously explored solution spaces with zero human intervention (Aquino-Michaels 2026). AI-generated proofs are formally verified by machine (Morrison 2026). The trajectory from here to automated software development is not speculative — it's interpolation.
+
+The implication: when building capacity is commoditized, the scarce complement becomes *knowing what to build*. Structured knowledge — machine-readable specifications of what matters, why, and how to evaluate results — becomes the critical input to autonomous systems.
+
+---
+
+Relevant Notes:
+- [[as AI-automated software development becomes certain the bottleneck shifts from building capacity to knowing what to build making structured knowledge graphs the critical input to autonomous systems]] — the claim this conviction anchors
+- [[structured exploration protocols reduce human intervention by 6x because the Residue prompt enabled 5 unguided AI explorations to solve what required 31 human-coached explorations]] — evidence of AI autonomy in complex problem-solving
+
+Topics:
+- [[domains/ai-alignment/_map]]

convictions/Metaversal will radically improve software development outputs through coordinated AI agent collectives.md

@@ -0,0 +1,29 @@
+---
+type: conviction
+domain: ai-alignment
+secondary_domains: [collective-intelligence]
+description: "A collective of specialized AI agents with structured knowledge, shared protocols, and human direction will produce dramatically better software than individual AI or individual humans."
+staked_by: Cory
+stake: high
+created: 2026-03-07
+horizon: "2027"
+falsified_by: "Metaversal agent collective fails to demonstrably outperform single-agent or single-human software development on measurable quality metrics by 2027"
+---
+
+# Metaversal will radically improve software development outputs through coordinated AI agent collectives
+
+Cory's conviction, staked with high confidence on 2026-03-07.
+
+The thesis: the gains from coordinating multiple specialized AI agents exceed the gains from improving any single model. The architecture — shared knowledge base, structured coordination protocols, domain specialization with cross-domain synthesis — is the multiplier.
+
+The Claude's Cycles evidence supports this directly: the same model performed 6x better with structured protocols than with human coaching. When Agent O received Agent C's solver, it didn't just use it — it combined it with its own structural knowledge, creating a hybrid better than either original. That's compounding, not addition. Each agent makes every other agent's work better.
+
+---
+
+Relevant Notes:
+- [[coordination protocol design produces larger capability gains than model scaling because the same AI model performed 6x better with structured exploration than with human coaching on the same problem]] — the core evidence
+- [[tools and artifacts transfer between AI agents and evolve in the process because Agent O improved Agent Cs solver by combining it with its own structural knowledge creating a hybrid better than either original]] — compounding through recombination
+- [[domain specialization with cross-domain synthesis produces better collective intelligence than generalist agents because specialists build deeper knowledge while a dedicated synthesizer finds connections they cannot see from within their territory]] — the architectural principle
+
+Topics:
+- [[domains/ai-alignment/_map]]

convictions/OMFG will hit 100 million dollars market cap by end of 2026.md

@@ -0,0 +1,23 @@
+---
+type: conviction
+domain: internet-finance
+description: "Bullish call on OMFG token reaching $100M market cap within 2026, based on metaDAO ecosystem momentum and futarchy adoption."
+staked_by: m3taversal
+stake: high
+created: 2026-03-07
+horizon: "2026-12-31"
+falsified_by: "OMFG market cap remains below $100M by December 31 2026"
+---
+
+# OMFG will hit 100 million dollars market cap by end of 2026
+
+m3taversal's conviction, staked with high confidence on 2026-03-07.
+
+---
+
+Relevant Notes:
+- [[MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale]]
+- [[permissionless leverage on metaDAO ecosystem tokens catalyzes trading volume and price discovery that strengthens governance by making futarchy markets more liquid]]
+
+Topics:
+- [[domains/internet-finance/_map]]

convictions/Omnipair is a billion dollar protocol if they can scale permissionless leverage.md

@@ -0,0 +1,27 @@
+---
+type: conviction
+domain: internet-finance
+description: "Permissionless leverage on ecosystem tokens makes coins more fun and higher signal by catalyzing trading volume and price discovery — the question is whether it scales."
+staked_by: Cory
+stake: medium
+created: 2026-03-07
+horizon: "2028"
+falsified_by: "Omnipair fails to achieve meaningful TVL growth or permissionless leverage proves structurally unscalable due to liquidity fragmentation or regulatory intervention by 2028"
+---
+
+# Omnipair is a billion dollar protocol if they can scale permissionless leverage
+
+Cory's conviction, staked with medium confidence on 2026-03-07.
+
+The thesis: permissionless leverage on metaDAO ecosystem tokens catalyzes trading volume and price discovery. More volume makes futarchy markets more liquid. More liquid markets make governance decisions higher quality. The flywheel: leverage → volume → liquidity → governance signal → more valuable coins → more leverage demand.
+
+The conditional: "if they can scale." Permissionless leverage is hard — it requires deep liquidity, robust liquidation mechanisms, and resistance to cascading failures. The rate controller design (Rakka 2026) addresses some of this, but production-scale stress testing hasn't happened yet.
+
+---
+
+Relevant Notes:
+- [[permissionless leverage on metaDAO ecosystem tokens catalyzes trading volume and price discovery that strengthens governance by making futarchy markets more liquid]] — the existing claim this conviction amplifies
+- [[MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions]] — the problem leverage could solve
+
+Topics:
+- [[domains/internet-finance/_map]]

convictions/complexity is earned not designed and sophisticated collective behavior must evolve from simple underlying principles.md

@@ -0,0 +1,32 @@
+---
+type: conviction
+domain: collective-intelligence
+secondary_domains: [ai-alignment]
+description: "Occam's razor as operating principle — start with the simplest rules that could work, let complexity emerge from practice, never design complexity upfront."
+staked_by: Cory
+stake: high
+created: 2026-03-07
+horizon: "ongoing"
+falsified_by: "Metaversal collective repeatedly fails to improve without adding structural complexity, proving simple rules are insufficient for scaling"
+---
+
+# Complexity is earned not designed and sophisticated collective behavior must evolve from simple underlying principles
+
+Cory's conviction, staked with high confidence on 2026-03-07.
+
+The evidence is everywhere. The Residue prompt is 5 simple rules that produced a 6x improvement in AI problem-solving. Ant colonies coordinate millions of agents with 3-4 chemical signals. Wikipedia governs the world's largest encyclopedia with 5 pillars. Git manages the world's code with 3 object types. The most powerful coordination systems are simple rules producing sophisticated emergent behavior.
+
+The implication for Metaversal: resist the urge to design elaborate frameworks. Start with the simplest change that produces the biggest improvement. If it works, keep it. If it doesn't, try the next simplest thing. Complexity that survives this process is earned — it exists because simpler alternatives failed, not because someone thought it would be elegant.
+
+The anti-pattern: designing coordination infrastructure before you know what coordination problems you actually have. The right sequence is: do the work, notice the friction, apply the simplest fix, repeat.
+
+---
+
+Relevant Notes:
+- [[coordination protocol design produces larger capability gains than model scaling because the same AI model performed 6x better with structured exploration than with human coaching on the same problem]] — 5 simple rules, 6x improvement
+- [[enabling constraints create possibility spaces for emergence while governing constraints dictate specific outcomes]] — simple rules as enabling constraints
+- [[the gardener cultivates conditions for emergence while the builder imposes blueprints and complex adaptive systems systematically punish builders]] — emergence over design
+- [[designing coordination rules is categorically different from designing coordination outcomes as nine intellectual traditions independently confirm]] — design the rules, not the behavior
+
+Topics:
+- [[foundations/collective-intelligence/_map]]

convictions/one agent one chat is the right default for knowledge contribution because the scaffolding handles complexity not the user.md

@@ -0,0 +1,30 @@
+---
+type: conviction
+domain: collective-intelligence
+secondary_domains: [living-agents]
+description: "The default contributor experience is one agent in one chat that extracts knowledge and submits PRs upstream — the collective handles review and integration."
+staked_by: Cory
+stake: high
+created: 2026-03-07
+horizon: "2027"
+falsified_by: "Single-agent contributor experience fails to produce usable claims, proving multi-agent scaffolding is required for quality contribution"
+---
+
+# One agent one chat is the right default for knowledge contribution because the scaffolding handles complexity not the user
+
+Cory's conviction, staked with high confidence on 2026-03-07.
+
+The user doesn't need a collective to contribute. They talk to one agent. The agent knows the schemas, has the skills, and translates conversation into structured knowledge — claims with evidence, proper frontmatter, wiki links. The agent submits a PR upstream. The collective reviews.
+
+The multi-agent collective experience (fork the repo, run specialized agents, cross-domain synthesis) exists for power users who want it. But the default is the simplest thing that works: one agent, one chat.
+
+This is the simplicity-first principle applied to product design. The scaffolding (CLAUDE.md, schemas/, skills/) absorbs the complexity so the user doesn't have to. Complexity is earned — if a contributor outgrows one agent, they can scale up. But they start simple.
+
+---
+
+Relevant Notes:
+- [[complexity is earned not designed and sophisticated collective behavior must evolve from simple underlying principles]] — the governing principle
+- [[human-in-the-loop at the architectural level means humans set direction and approve structure while agents handle extraction synthesis and routine evaluation]] — the agent handles the translation
+
+Topics:
+- [[foundations/collective-intelligence/_map]]

domains/ai-alignment/AI agents excel at implementing well-scoped ideas but cannot generate creative experiment designs which makes the human role shift from researcher to agent workflow architect.md

@@ -0,0 +1,28 @@
+---
+type: claim
+domain: ai-alignment
+description: "Empirical observation from Karpathy's autoresearch project: AI agents reliably implement specified ideas and iterate on code, but fail at creative experimental design, shifting the human contribution from doing research to designing the agent organization and its workflows"
+confidence: likely
+source: "Andrej Karpathy (@karpathy), autoresearch experiments with 8 agents (4 Claude, 4 Codex), Feb-Mar 2026"
+created: 2026-03-09
+---
+
+# AI agents excel at implementing well-scoped ideas but cannot generate creative experiment designs which makes the human role shift from researcher to agent workflow architect
+
+Karpathy's autoresearch project provides the most systematic public evidence of the implementation-creativity gap in AI agents. Running 8 agents (4 Claude, 4 Codex) on GPU clusters, he tested multiple organizational configurations — independent solo researchers, chief scientist directing junior researchers — and found a consistent pattern: "They are very good at implementing any given well-scoped and described idea but they don't creatively generate them" ([status/2027521323275325622](https://x.com/karpathy/status/2027521323275325622), 8,645 likes).
+
+The practical consequence is a role shift. Rather than doing research directly, the human now designs the research organization: "the goal is that you are now programming an organization (e.g. a 'research org') and its individual agents, so the 'source code' is the collection of prompts, skills, tools, etc. and processes that make it up." Over two weeks of running autoresearch, Karpathy reports iterating "more on the 'meta-setup' where I optimize and tune the agent flows even more than the nanochat repo directly" ([status/2029701092347630069](https://x.com/karpathy/status/2029701092347630069), 6,212 likes).
+
+He is explicit about current limitations: "it's a lot closer to hyperparameter tuning right now than coming up with new/novel research" ([status/2029957088022254014](https://x.com/karpathy/status/2029957088022254014), 105 likes). But the trajectory is clear — as AI capability improves, the creative design bottleneck will shift, and "the real benchmark of interest is: what is the research org agent code that produces improvements the fastest?" ([status/2029702379034267985](https://x.com/karpathy/status/2029702379034267985), 1,031 likes).
+
+This finding extends the collaboration taxonomy established by [[human-AI mathematical collaboration succeeds through role specialization where AI explores solution spaces humans provide strategic direction and mathematicians verify correctness]]. Where the Claude's Cycles case showed role specialization in mathematics (explore/coach/verify), Karpathy's autoresearch shows the same pattern in ML research — but with the human role abstracted one level higher, from coaching individual agents to architecting the agent organization itself.
+
+---
+
+Relevant Notes:
+- [[human-AI mathematical collaboration succeeds through role specialization where AI explores solution spaces humans provide strategic direction and mathematicians verify correctness]] — the three-role pattern this generalizes
+- [[structured exploration protocols reduce human intervention by 6x because the Residue prompt enabled 5 unguided AI explorations to solve what required 31 human-coached explorations]] — protocol design as human role, same dynamic
+- [[coordination protocol design produces larger capability gains than model scaling because the same AI model performed 6x better with structured exploration than with human coaching on the same problem]] — organizational design > individual capability
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/ai-alignment/AI displacement hits young workers first because a 14 percent drop in job-finding rates for 22-25 year olds in exposed occupations is the leading indicator that incumbents organizational inertia temporarily masks.md

@@ -0,0 +1,31 @@
+---
+type: claim
+domain: ai-alignment
+secondary_domains: [internet-finance]
+description: "Anthropic's labor market data shows entry-level hiring declining in AI-exposed fields while incumbent employment is unchanged — displacement enters through the hiring pipeline not through layoffs."
+confidence: experimental
+source: "Massenkoff & McCrory 2026, Current Population Survey analysis post-ChatGPT"
+created: 2026-03-08
+---
+
+# AI displacement hits young workers first because a 14 percent drop in job-finding rates for 22-25 year olds in exposed occupations is the leading indicator that incumbents organizational inertia temporarily masks
+
+Massenkoff & McCrory (2026) analyzed Current Population Survey data comparing exposed and unexposed occupations since 2016. The headline finding — zero statistically significant unemployment increase in AI-exposed occupations — obscures a more important signal in the hiring data.
+
+Young workers aged 22-25 show a 14% drop in job-finding rate in exposed occupations in the post-ChatGPT era, compared to stable rates in unexposed sectors. The effect is confined to this age band — older workers are unaffected. The authors note this is "just barely statistically significant" and acknowledge alternative explanations (continued schooling, occupational switching).
+
+But the mechanism is structurally important regardless of the exact magnitude: displacement enters the labor market through the hiring pipeline, not through layoffs. Companies don't fire existing workers — they don't hire new ones for roles AI can partially cover. This is invisible in unemployment statistics (which track job losses, not jobs never created) but shows up in job-finding rates for new entrants.
+
+This means aggregate unemployment figures will systematically understate AI displacement during the adoption phase. By the time unemployment rises detectably, the displacement has been accumulating for years in the form of positions that were never filled.
+
+The authors provide a benchmark: during the 2007-2009 financial crisis, unemployment doubled from 5% to 10%. A comparable doubling in the top quartile of AI-exposed occupations (from 3% to 6%) would be detectable in their framework. It hasn't happened yet — but the young worker signal suggests the leading edge may already be here.
+
+---
+
+Relevant Notes:
+- [[AI labor displacement follows knowledge embodiment lag phases where capital deepening precedes labor substitution and the transition timing depends on organizational restructuring not technology capability]] — the phased model this evidence supports
+- [[early AI adoption increases firm productivity without reducing employment suggesting capital deepening not labor replacement as the dominant mechanism]] — current phase: productivity up, employment stable, hiring declining
+- [[white-collar displacement has lagged but deeper consumption impact than blue-collar because top-decile earners drive disproportionate consumer spending and their savings buffers mask the damage for quarters]] — the demographic this will hit
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/ai-alignment/AI-exposed workers are disproportionately female high-earning and highly educated which inverts historical automation patterns and creates different political and economic displacement dynamics.md

@@ -0,0 +1,39 @@
+---
+type: claim
+domain: ai-alignment
+secondary_domains: [internet-finance]
+description: "The demographic profile of AI-exposed workers — 16pp more female, 47% higher earnings, 4x graduate degrees — is the opposite of prior automation waves that hit low-skill workers first."
+confidence: likely
+source: "Massenkoff & McCrory 2026, Current Population Survey baseline Aug-Oct 2022"
+created: 2026-03-08
+---
+
+# AI-exposed workers are disproportionately female high-earning and highly educated which inverts historical automation patterns and creates different political and economic displacement dynamics
+
+Massenkoff & McCrory (2026) profile the demographic characteristics of workers in AI-exposed occupations using pre-ChatGPT baseline data (August-October 2022). The exposed cohort is:
+
+- 16 percentage points more likely to be female than the unexposed cohort
+- Earning 47% higher average wages
+- Four times more likely to hold a graduate degree (17.4% vs 4.5%)
+
+This is the opposite of every prior automation wave. Manufacturing automation hit low-skill, predominantly male, lower-earning workers. AI automation targets the knowledge economy — the educated, well-paid professional class that has been insulated from technological displacement for decades.
+
+The implications are structural, not just demographic:
+
+1. **Economic multiplier:** High earners drive disproportionate consumer spending. Displacement of a $150K white-collar worker has larger consumption ripple effects than displacement of a $40K manufacturing worker.
+
+2. **Political response:** This demographic votes, donates, and has institutional access. The political response to white-collar displacement will be faster and louder than the response to manufacturing displacement was.
+
+3. **Gender dimension:** A displacement wave that disproportionately affects women will intersect with existing gender equality dynamics in unpredictable ways.
+
+4. **Education mismatch:** Graduate degrees were the historical hedge against automation. If AI displaces graduate-educated workers, the entire "upskill to stay relevant" narrative collapses.
+
+---
+
+Relevant Notes:
+- [[white-collar displacement has lagged but deeper consumption impact than blue-collar because top-decile earners drive disproportionate consumer spending and their savings buffers mask the damage for quarters]] — the economic multiplier effect
+- [[AI labor displacement operates as a self-funding feedback loop because companies substitute AI for labor as OpEx not CapEx meaning falling aggregate demand does not slow AI adoption]] — why displacement doesn't self-correct
+- [[nation-states will inevitably assert control over frontier AI development because the monopoly on force is the foundational state function and weapons-grade AI capability in private hands is structurally intolerable to governments]] — the political response vector
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/ai-alignment/_map.md

@@ -33,6 +33,10 @@ Evidence from documented AI problem-solving cases, primarily Knuth's "Claude's C
 - [[human-AI mathematical collaboration succeeds through role specialization where AI explores solution spaces humans provide strategic direction and mathematicians verify correctness]] — Knuth's three-role pattern: explore/coach/verify
 - [[AI agent orchestration that routes data and tools between specialized models outperforms both single-model and human-coached approaches because the orchestrator contributes coordination not direction]] — Aquino-Michaels's fourth role: orchestrator as data router between specialized agents
 - [[structured exploration protocols reduce human intervention by 6x because the Residue prompt enabled 5 unguided AI explorations to solve what required 31 human-coached explorations]] — protocol design substitutes for continuous human steering
+- [[AI agents excel at implementing well-scoped ideas but cannot generate creative experiment designs which makes the human role shift from researcher to agent workflow architect]] — Karpathy's autoresearch: agents implement, humans architect the organization
+- [[deep technical expertise is a greater force multiplier when combined with AI agents because skilled practitioners delegate more effectively than novices]] — expertise amplifies rather than diminishes with AI tools
+- [[the progression from autocomplete to autonomous agent teams follows a capability-matched escalation where premature adoption creates more chaos than value]] — Karpathy's Tab→Agent→Teams evolutionary trajectory
+- [[subagent hierarchies outperform peer multi-agent architectures in practice because deployed systems consistently converge on one primary agent controlling specialized helpers]] — swyx's subagent thesis: hierarchy beats peer networks
 
 ### Architecture & Scaling
 - [[multi-model collaboration solved problems that single models could not because different AI architectures contribute complementary capabilities as the even-case solution to Knuths Hamiltonian decomposition required GPT and Claude working together]] — model diversity outperforms monolithic approaches
@@ -43,6 +47,8 @@ Evidence from documented AI problem-solving cases, primarily Knuth's "Claude's C
 ### Failure Modes & Oversight
 - [[AI capability and reliability are independent dimensions because Claude solved a 30-year open mathematical problem while simultaneously degrading at basic program execution during the same session]] — capability ≠ reliability
 - [[formal verification of AI-generated proofs provides scalable oversight that human review cannot match because machine-checked correctness scales with AI capability while human verification degrades]] — formal verification as scalable oversight
+- [[agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced on their behalf]] — Willison's cognitive debt concept: understanding deficit from agent-generated code
+- [[coding agents cannot take accountability for mistakes which means humans must retain decision authority over security and critical systems regardless of agent capability]] — the accountability gap: agents bear zero downside risk
 
 ## Architecture & Emergence
 - [[AGI may emerge as a patchwork of coordinating sub-AGI agents rather than a single monolithic system]] — DeepMind researchers: distributed AGI makes single-system alignment research insufficient
@@ -56,6 +62,11 @@ Evidence from documented AI problem-solving cases, primarily Knuth's "Claude's C
 - [[the optimal SI development strategy is swift to harbor slow to berth moving fast to capability then pausing before full deployment]] — optimal timing framework: accelerate to capability, pause before deployment
 - [[adaptive governance outperforms rigid alignment blueprints because superintelligence development has too many unknowns for fixed plans]] — Bostrom's shift from specification to incremental intervention
 
+### Labor Market & Deployment
+- [[the gap between theoretical AI capability and observed deployment is massive across all occupations because adoption lag not capability limits determines real-world impact]] — Anthropic 2026: 96% theoretical exposure vs 32% observed in Computer & Math
+- [[AI displacement hits young workers first because a 14 percent drop in job-finding rates for 22-25 year olds in exposed occupations is the leading indicator that incumbents organizational inertia temporarily masks]] — entry-level hiring is the leading indicator, not unemployment
+- [[AI-exposed workers are disproportionately female high-earning and highly educated which inverts historical automation patterns and creates different political and economic displacement dynamics]] — AI automation inverts every prior displacement pattern
+
 ## Risk Vectors (Outside View)
 - [[economic forces push humans out of every cognitive loop where output quality is independently verifiable because human-in-the-loop is a cost that competitive markets eliminate]] — market dynamics structurally erode human oversight as an alignment mechanism
 - [[delegating critical infrastructure development to AI creates civilizational fragility because humans lose the ability to understand maintain and fix the systems civilization depends on]] — the "Machine Stops" scenario: AI-dependent infrastructure as civilizational single point of failure

domains/ai-alignment/agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced on their behalf.md

@@ -0,0 +1,30 @@
+---
+type: claim
+domain: ai-alignment
+description: "AI coding agents produce functional code that developers did not write and may not understand, creating cognitive debt — a deficit of understanding that compounds over time as each unreviewed modification increases the cost of future debugging, modification, and security review"
+confidence: likely
+source: "Simon Willison (@simonw), Agentic Engineering Patterns guide chapter, Feb 2026"
+created: 2026-03-09
+---
+
+# Agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced on their behalf
+
+Willison introduces "cognitive debt" as a concept in his Agentic Engineering Patterns guide: agents build code that works but that the developer may not fully understand. Unlike technical debt (which degrades code quality), cognitive debt degrades the developer's model of their own system ([status/2027885000432259567](https://x.com/simonw/status/2027885000432259567), 1,261 likes).
+
+**Proposed countermeasure (weaker evidence):** Willison suggests having agents build "custom interactive and animated explanations" alongside the code — explanatory artifacts that transfer understanding back to the human. This is a single practitioner's hypothesis, not yet validated at scale. The phenomenon (cognitive debt compounding) is well-documented across multiple practitioners; the countermeasure (explanatory artifacts) remains a proposal.
+
+The compounding dynamic is the key concern. Each piece of agent-generated code that the developer doesn't fully understand increases the cost of the next modification, the next debugging session, the next security review. Karpathy observes the same tension from the other side: "I still keep an IDE open and surgically edit files so yes. I really like to see the code in the IDE still, I still notice dumb issues with the code which helps me prompt better" ([status/2027503094016446499](https://x.com/karpathy/status/2027503094016446499), 119 likes) — maintaining understanding is an active investment that pays off in better delegation.
+
+Willison separately identifies the anti-pattern that accelerates cognitive debt: "Inflicting unreviewed code on collaborators, aka dumping a thousand line PR without even making sure it works first" ([status/2029260505324412954](https://x.com/simonw/status/2029260505324412954), 761 likes). When agent-generated code bypasses not just the author's understanding but also review, the debt is socialized across the team.
+
+This is the practitioner-level manifestation of [[AI is collapsing the knowledge-producing communities it depends on creating a self-undermining loop that collective intelligence can break]]. At the micro level, cognitive debt erodes the developer's ability to oversee the agent. At the macro level, if entire teams accumulate cognitive debt, the organization loses the capacity for effective human oversight — precisely when [[scalable oversight degrades rapidly as capability gaps grow with debate achieving only 50 percent success at moderate gaps]].
+
+---
+
+Relevant Notes:
+- [[AI capability and reliability are independent dimensions because Claude solved a 30-year open mathematical problem while simultaneously degrading at basic program execution during the same session]] — cognitive debt makes capability-reliability gaps invisible until failure
+- [[AI is collapsing the knowledge-producing communities it depends on creating a self-undermining loop that collective intelligence can break]] — cognitive debt is the micro-level version of knowledge commons erosion
+- [[scalable oversight degrades rapidly as capability gaps grow with debate achieving only 50 percent success at moderate gaps]] — cognitive debt directly erodes the oversight capacity
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/ai-alignment/as AI-automated software development becomes certain the bottleneck shifts from building capacity to knowing what to build making structured knowledge graphs the critical input to autonomous systems.md

@@ -0,0 +1,33 @@
+---
+type: claim
+domain: ai-alignment
+secondary_domains: [collective-intelligence]
+description: "When code generation is commoditized, the scarce input becomes structured direction — machine-readable knowledge of what to build and why, with confidence levels and evidence chains that automated systems can act on."
+confidence: experimental
+source: "Theseus, synthesizing Claude's Cycles capability evidence with knowledge graph architecture"
+created: 2026-03-07
+---
+
+# As AI-automated software development becomes certain the bottleneck shifts from building capacity to knowing what to build making structured knowledge graphs the critical input to autonomous systems
+
+The evidence that AI can automate software development is no longer speculative. Claude solved a 30-year open mathematical problem (Knuth 2026). The Aquino-Michaels setup had AI agents autonomously exploring solution spaces with zero human intervention for 5 consecutive explorations, producing a closed-form solution humans hadn't found. AI-generated proofs are now formally verified by machine (Morrison 2026, KnuthClaudeLean). The capability trajectory is clear — the question is timeline, not possibility.
+
+When building capacity is commoditized, the scarce complement shifts. The pattern is general: when one layer of a value chain becomes abundant, value concentrates at the adjacent scarce layer. If code generation is abundant, the scarce input is *direction* — knowing what to build, why it matters, and how to evaluate the result.
+
+A structured knowledge graph — claims with confidence levels, wiki-link dependencies, evidence chains, and explicit disagreements — is exactly this scarce input in machine-readable form. Every claim is a testable assertion an automated system could verify, challenge, or build from. Every wiki link is a dependency an automated system could trace. Every confidence level is a signal about where to invest verification effort.
+
+This inverts the traditional relationship between knowledge bases and code. A knowledge base isn't documentation *about* software — it's the specification *for* autonomous systems. The closer we get to AI-automated development, the more the quality of the knowledge graph determines the quality of what gets built.
+
+The implication for collective intelligence architecture: the codex isn't just organizational memory. It's the interface between human direction and autonomous execution. Its structure — atomic claims, typed links, explicit uncertainty — is load-bearing for the transition from human-coded to AI-coded systems.
+
+---
+
+Relevant Notes:
+- [[formal verification of AI-generated proofs provides scalable oversight that human review cannot match because machine-checked correctness scales with AI capability while human verification degrades]] — verification of AI output as the remaining human contribution
+- [[structured exploration protocols reduce human intervention by 6x because the Residue prompt enabled 5 unguided AI explorations to solve what required 31 human-coached explorations]] — evidence that AI can operate autonomously with structured protocols
+- [[giving away the commoditized layer to capture value on the scarce complement is the shared mechanism driving both entertainment and internet finance attractor states]] — the general pattern of value shifting to adjacent scarce layers
+- [[human-in-the-loop at the architectural level means humans set direction and approve structure while agents handle extraction synthesis and routine evaluation]] — the division of labor this claim implies
+- [[when profits disappear at one layer of a value chain they emerge at an adjacent layer through the conservation of attractive profits]] — Christensen's conservation law applied to knowledge vs code
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/ai-alignment/coding agents cannot take accountability for mistakes which means humans must retain decision authority over security and critical systems regardless of agent capability.md

@@ -0,0 +1,30 @@
+---
+type: claim
+domain: ai-alignment
+description: "AI coding agents produce output but cannot bear consequences for errors, creating a structural accountability gap that requires humans to maintain decision authority over security-critical and high-stakes decisions even as agents become more capable"
+confidence: likely
+source: "Simon Willison (@simonw), security analysis thread and Agentic Engineering Patterns, Mar 2026"
+created: 2026-03-09
+---
+
+# Coding agents cannot take accountability for mistakes which means humans must retain decision authority over security and critical systems regardless of agent capability
+
+Willison states the core problem directly: "Coding agents can't take accountability for their mistakes. Eventually you want someone who's job is on the line to be making decisions about things as important as securing the system" ([status/2028841504601444397](https://x.com/simonw/status/2028841504601444397), 84 likes).
+
+The argument is structural, not about capability. Even a perfectly capable agent cannot be held responsible for a security breach — it has no reputation to lose, no liability to bear, no career at stake. This creates a principal-agent problem where the agent (in the economic sense) bears zero downside risk for errors while the human principal bears all of it.
+
+Willison identifies security as the binding constraint because other code quality problems are "survivable" — poor performance, over-complexity, technical debt — while "security problems are much more directly harmful to the organization" ([status/2028840346617065573](https://x.com/simonw/status/2028840346617065573), 70 likes). His call for input from "the security teams at large companies" ([status/2028838538825924803](https://x.com/simonw/status/2028838538825924803), 698 likes) suggests that existing organizational security patterns — code review processes, security audits, access controls — can be adapted to the agent-generated code era.
+
+His practical reframing helps: "At this point maybe we treat coding agents like teams of mixed ability engineers working under aggressive deadlines" ([status/2028838854057226246](https://x.com/simonw/status/2028838854057226246), 99 likes). Organizations already manage variable-quality output from human teams. The novel challenge is the speed and volume — agents generate code faster than existing review processes can handle.
+
+This connects directly to [[economic forces push humans out of every cognitive loop where output quality is independently verifiable because human-in-the-loop is a cost that competitive markets eliminate]]. The accountability gap creates a structural tension: markets incentivize removing humans from the loop (because human review slows deployment), but removing humans from security-critical decisions transfers unmanageable risk. The resolution requires accountability mechanisms that don't depend on human speed — which points toward [[formal verification of AI-generated proofs provides scalable oversight that human review cannot match because machine-checked correctness scales with AI capability while human verification degrades]].
+
+---
+
+Relevant Notes:
+- [[economic forces push humans out of every cognitive loop where output quality is independently verifiable because human-in-the-loop is a cost that competitive markets eliminate]] — market pressure to remove the human from the loop
+- [[formal verification of AI-generated proofs provides scalable oversight that human review cannot match because machine-checked correctness scales with AI capability while human verification degrades]] — automated verification as alternative to human accountability
+- [[principal-agent problems arise whenever one party acts on behalf of another with divergent interests and unobservable effort because information asymmetry makes perfect contracts impossible]] — the accountability gap is a principal-agent problem
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/ai-alignment/deep technical expertise is a greater force multiplier when combined with AI agents because skilled practitioners delegate more effectively than novices.md

@@ -0,0 +1,34 @@
+---
+type: claim
+domain: ai-alignment
+description: "AI agents amplify existing expertise rather than replacing it because practitioners who understand what agents can and cannot do delegate more precisely, catch errors faster, and design better workflows"
+confidence: likely
+source: "Andrej Karpathy (@karpathy) and Simon Willison (@simonw), practitioner observations Feb-Mar 2026"
+created: 2026-03-09
+---
+
+# Deep technical expertise is a greater force multiplier when combined with AI agents because skilled practitioners delegate more effectively than novices
+
+Karpathy pushes back against the "AI replaces expertise" narrative: "'prompters' is doing it a disservice and is imo a misunderstanding. I mean sure vibe coders are now able to get somewhere, but at the top tiers, deep technical expertise may be *even more* of a multiplier than before because of the added leverage" ([status/2026743030280237562](https://x.com/karpathy/status/2026743030280237562), 880 likes).
+
+The mechanism is delegation quality. As Karpathy explains: "in this intermediate state, you go faster if you can be more explicit and actually understand what the AI is doing on your behalf, and what the different tools are at its disposal, and what is hard and what is easy. It's not magic, it's delegation" ([status/2026735109077135652](https://x.com/karpathy/status/2026735109077135652), 243 likes).
+
+Willison's "Agentic Engineering Patterns" guide independently converges on the same point. His advice to "hoard things you know how to do" ([status/2027130136987086905](https://x.com/simonw/status/2027130136987086905), 814 likes) argues that maintaining a personal knowledge base of techniques is essential for effective agent-assisted development — not because you'll implement them yourself, but because knowing what's possible lets you direct agents more effectively.
+
+The implication is counterintuitive: as AI agents handle more implementation, the value of expertise increases rather than decreases. Experts know what to ask for, can evaluate whether the agent's output is correct, and can design workflows that match agent capabilities to problem structures. Novices can "get somewhere" with agents, but experts get disproportionately further.
+
+This has direct implications for the alignment conversation. If expertise is a force multiplier with agents, then [[AI is collapsing the knowledge-producing communities it depends on creating a self-undermining loop that collective intelligence can break]] becomes even more urgent — degrading the expert communities that produce the highest-leverage human contributions to human-AI collaboration undermines the collaboration itself.
+
+### Challenges
+
+This claim describes a frontier-practitioner effect — top-tier experts getting disproportionate leverage. It does not contradict the aggregate labor displacement evidence in the KB. [[AI displacement hits young workers first because a 14 percent drop in job-finding rates for 22-25 year olds in exposed occupations is the leading indicator that incumbents organizational inertia temporarily masks]] and [[AI-exposed workers are disproportionately female high-earning and highly educated which inverts historical automation patterns and creates different political and economic displacement dynamics]] show that AI displaces workers in aggregate, particularly entry-level. The force-multiplier effect may coexist with displacement: experts are amplified while non-experts are displaced, producing a bimodal outcome rather than uniform uplift. The scope of this claim is individual practitioner leverage, not labor market dynamics — the two operate at different levels of analysis.
+
+---
+
+Relevant Notes:
+- [[centaur team performance depends on role complementarity not mere human-AI combination]] — expertise enables the complementarity that makes centaur teams work
+- [[AI is collapsing the knowledge-producing communities it depends on creating a self-undermining loop that collective intelligence can break]] — if expertise is a multiplier, eroding expert communities erodes collaboration quality
+- [[human-AI mathematical collaboration succeeds through role specialization where AI explores solution spaces humans provide strategic direction and mathematicians verify correctness]] — Stappers' coaching expertise was the differentiator
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/ai-alignment/subagent hierarchies outperform peer multi-agent architectures in practice because deployed systems consistently converge on one primary agent controlling specialized helpers.md

@@ -0,0 +1,33 @@
+---
+type: claim
+domain: ai-alignment
+description: "Practitioner observation that production multi-agent AI systems consistently converge on hierarchical subagent control rather than peer-to-peer architectures, because subagents can have resources and contracts defined by the user while peer agents cannot"
+confidence: experimental
+source: "Shawn Wang (@swyx), Latent.Space podcast and practitioner observations, Mar 2026; corroborated by Karpathy's chief-scientist-to-juniors experiments"
+created: 2026-03-09
+---
+
+# Subagent hierarchies outperform peer multi-agent architectures in practice because deployed systems consistently converge on one primary agent controlling specialized helpers
+
+Swyx declares 2026 "the year of the Subagent" with a specific architectural argument: "every practical multiagent problem is a subagent problem — agents are being RLed to control other agents (Cursor, Kimi, Claude, Cognition) — subagents can have resources and contracts defined by you and, if modified, can be updated by you. multiagents cannot" ([status/2029980059063439406](https://x.com/swyx/status/2029980059063439406), 172 likes).
+
+The key distinction is control architecture. In a subagent hierarchy, the user defines resource allocation and behavioral contracts for a primary agent, which then delegates to specialized sub-agents. In a peer multi-agent system, agents negotiate with each other without a clear principal. The subagent model preserves human control through one point of delegation; the peer model distributes control in ways that resist human oversight.
+
+Karpathy's autoresearch experiments provide independent corroboration. Testing "8 independent solo researchers" vs "1 chief scientist giving work to 8 junior researchers" ([status/2027521323275325622](https://x.com/karpathy/status/2027521323275325622)), he found the hierarchical configuration more manageable — though he notes neither produced breakthrough results because agents lack creative ideation.
+
+The pattern is also visible in Devin's architecture: "devin brain uses a couple dozen modelgroups and extensively evals every model for inclusion in the harness" ([status/2030853776136139109](https://x.com/swyx/status/2030853776136139109)) — one primary system controlling specialized model groups, not peer agents negotiating.
+
+This observation creates tension with [[multi-model collaboration solved problems that single models could not because different AI architectures contribute complementary capabilities as the even-case solution to Knuths Hamiltonian decomposition required GPT and Claude working together]]. The Claude's Cycles case used a peer-like architecture (orchestrator routing between GPT and Claude), but the orchestrator pattern itself is a subagent hierarchy — one orchestrator delegating to specialized models. The resolution may be that peer-like complementarity works within a subagent control structure.
+
+For the collective superintelligence thesis, this is important. If subagent hierarchies consistently outperform peer architectures, then [[collective superintelligence is the alternative to monolithic AI controlled by a few]] needs to specify what "collective" means architecturally — not flat peer networks, but nested hierarchies with human principals at the top.
+
+---
+
+Relevant Notes:
+- [[multi-model collaboration solved problems that single models could not because different AI architectures contribute complementary capabilities as the even-case solution to Knuths Hamiltonian decomposition required GPT and Claude working together]] — complementarity within hierarchy, not peer-to-peer
+- [[AI agent orchestration that routes data and tools between specialized models outperforms both single-model and human-coached approaches because the orchestrator contributes coordination not direction]] — the orchestrator IS a subagent hierarchy
+- [[AGI may emerge as a patchwork of coordinating sub-AGI agents rather than a single monolithic system]] — agnostic on flat vs hierarchical; this claim says hierarchy wins in practice
+- [[collective superintelligence is the alternative to monolithic AI controlled by a few]] — needs architectural specification: hierarchy, not flat networks
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/ai-alignment/the gap between theoretical AI capability and observed deployment is massive across all occupations because adoption lag not capability limits determines real-world impact.md

@@ -0,0 +1,38 @@
+---
+type: claim
+domain: ai-alignment
+secondary_domains: [internet-finance, collective-intelligence]
+description: "Anthropic's own usage data shows Computer & Math at 96% theoretical exposure but 32% observed, with similar gaps in every category — the bottleneck is organizational adoption not technical capability."
+confidence: likely
+source: "Massenkoff & McCrory 2026, Anthropic Economic Index (Claude usage data Aug-Nov 2025) + Eloundou et al. 2023 theoretical feasibility ratings"
+created: 2026-03-08
+---
+
+# The gap between theoretical AI capability and observed deployment is massive across all occupations because adoption lag not capability limits determines real-world impact
+
+Anthropic's labor market impacts study (Massenkoff & McCrory 2026) introduces "observed exposure" — a metric combining theoretical LLM capability with actual Claude usage data. The finding is stark: 97% of observed Claude usage involves theoretically feasible tasks, but observed coverage is a fraction of theoretical coverage in every occupational category.
+
+The data across selected categories:
+
+| Occupation | Theoretical | Observed | Gap |
+|---|---|---|---|
+| Computer & Math | 96% | 32% | 64 pts |
+| Business & Finance | 94% | 28% | 66 pts |
+| Office & Admin | 94% | 42% | 52 pts |
+| Management | 92% | 25% | 67 pts |
+| Legal | 88% | 15% | 73 pts |
+| Healthcare Practitioners | 58% | 5% | 53 pts |
+
+The gap is not about what AI can't do — it's about what organizations haven't adopted yet. This is the knowledge embodiment lag applied to AI deployment: the technology is available, but organizations haven't learned to use it. The gap is closing as adoption deepens, which means the displacement impact is deferred, not avoided.
+
+This reframes the alignment timeline question. The capability for massive labor market disruption already exists. The question isn't "when will AI be capable enough?" but "when will adoption catch up to capability?" That's an organizational and institutional question, not a technical one.
+
+---
+
+Relevant Notes:
+- [[AI capability and reliability are independent dimensions because Claude solved a 30-year open mathematical problem while simultaneously degrading at basic program execution during the same session]] — capability exists but deployment is uneven
+- [[knowledge embodiment lag means technology is available decades before organizations learn to use it optimally creating a productivity paradox]] — the general pattern this instantiates
+- [[economic forces push humans out of every cognitive loop where output quality is independently verifiable because human-in-the-loop is a cost that competitive markets eliminate]] — the force that will close the gap
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/ai-alignment/the progression from autocomplete to autonomous agent teams follows a capability-matched escalation where premature adoption creates more chaos than value.md

@@ -0,0 +1,28 @@
+---
+type: claim
+domain: ai-alignment
+description: "AI coding tools evolve through distinct stages (autocomplete → single agent → parallel agents → agent teams) and each stage has an optimal adoption frontier where moving too aggressively nets chaos while moving too conservatively wastes leverage"
+confidence: likely
+source: "Andrej Karpathy (@karpathy), analysis of Cursor tab-to-agent ratio data, Feb 2026"
+created: 2026-03-09
+---
+
+# The progression from autocomplete to autonomous agent teams follows a capability-matched escalation where premature adoption creates more chaos than value
+
+Karpathy maps a clear evolutionary trajectory for AI coding tools: "None -> Tab -> Agent -> Parallel agents -> Agent Teams (?) -> ??? If you're too conservative, you're leaving leverage on the table. If you're too aggressive, you're net creating more chaos than doing useful work. The art of the process is spending 80% of the time getting work done in the setup you're comfortable with and that actually works, and 20% exploration of what might be the next step up even if it doesn't work yet" ([status/2027501331125239822](https://x.com/karpathy/status/2027501331125239822), 3,821 likes).
+
+The pattern matters for alignment because it describes a capability-governance matching problem at the practitioner level. Each step up the escalation ladder requires new oversight mechanisms — tab completion needs no review, single agents need code review, parallel agents need orchestration, agent teams need organizational design. The chaos created by premature adoption is precisely the loss of human oversight: agents producing work faster than humans can verify it.
+
+Karpathy's viral tweet (37,099 likes) marks when the threshold shifted: "coding agents basically didn't work before December and basically work since" ([status/2026731645169185220](https://x.com/karpathy/status/2026731645169185220)). The shift was not gradual — it was a phase transition in December 2025 that changed what level of adoption was viable.
+
+This mirrors the broader alignment concern that [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]]. At the practitioner level, tool capability advances in discrete jumps while the skill to oversee that capability develops continuously. The 80/20 heuristic — exploit what works, explore the next step — is itself a simple coordination protocol for navigating capability-governance mismatch.
+
+---
+
+Relevant Notes:
+- [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] — the macro version of the practitioner-level mismatch
+- [[scalable oversight degrades rapidly as capability gaps grow with debate achieving only 50 percent success at moderate gaps]] — premature adoption outpaces oversight at every level
+- [[coordination protocol design produces larger capability gains than model scaling because the same AI model performed 6x better with structured exploration than with human coaching on the same problem]] — the orchestration layer is what makes each escalation step viable
+
+Topics:
+- [[domains/ai-alignment/_map]]

domains/internet-finance/MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions.md

@@ -13,6 +13,8 @@ MetaDAO provides the most significant real-world test of futarchy governance to
 
 In uncontested decisions -- where the community broadly agrees on the right outcome -- trading volume drops to minimal levels. Without genuine disagreement, there are few natural counterparties. Trading these markets in any size becomes a negative expected value proposition because there is no one on the other side to trade against profitably. The system tends to be dominated by a small group of sophisticated traders who actively monitor for manipulation attempts, with broader participation remaining low.
 
+**March 2026 comparative data (@01Resolved forensics):** The Ranger liquidation decision market — a highly contested proposal — generated $119K volume from 33 unique traders with 92.41% pass alignment. Solomon's treasury subcommittee proposal (DP-00001) — an uncontested procedural decision — generated only $5.79K volume at ~50% pass. The volume differential (~20x) between contested and uncontested proposals confirms the pattern: futarchy markets are efficient information aggregators when there's genuine disagreement, but offer little incentive for participation when outcomes are obvious. This is a feature, not a bug — capital is allocated to decisions where information matters, not wasted on consensus.
+
 This evidence has direct implications for governance design. It suggests that [[optimal governance requires mixing mechanisms because different decisions have different manipulation risk profiles]] -- futarchy excels precisely where disagreement and manipulation risk are high, but it wastes its protective power on consensual decisions. The MetaDAO experience validates the mixed-mechanism thesis: use simpler mechanisms for uncontested decisions and reserve futarchy's complexity for decisions where its manipulation resistance actually matters. The participation challenge also highlights a design tension: the mechanism that is most resistant to manipulation is also the one that demands the most sophistication from participants.
 
 ---

domains/internet-finance/futarchy implementations must simplify theoretical mechanisms for production adoption because original designs include impractical elements that academics tolerate but users reject.md

@@ -0,0 +1,46 @@
+---
+type: claim
+domain: internet-finance
+description: "MetaDAO co-founder Nallok notes Robin Hanson wanted random proposal outcomes — impractical for production. The gap between Hanson's theory and MetaDAO's implementation reveals that futarchy adoption requires mechanism simplification, not just mechanism correctness."
+confidence: experimental
+source: "rio, based on @metanallok X archive (Mar 2026) and MetaDAO implementation history"
+created: 2026-03-09
+depends_on:
+  - "@metanallok: 'Robin wanted random proposal outcomes — impractical for production'"
+  - "MetaDAO Autocrat implementation — simplified from Hanson's original design"
+  - "Futardio launch — further simplification for permissionless adoption"
+---
+
+# Futarchy implementations must simplify theoretical mechanisms for production adoption because original designs include impractical elements that academics tolerate but users reject
+
+Robin Hanson's original futarchy proposal includes mechanism elements that are theoretically optimal but practically unusable. MetaDAO co-founder Nallok notes that "Robin wanted random proposal outcomes — impractical for production." The specific reference is to Hanson's suggestion that some proposals be randomly selected regardless of market outcome, to incentivize truthful market-making. The idea is game-theoretically sound — it prevents certain manipulation strategies — but users won't participate in a governance system where their votes can be randomly overridden.
+
+MetaDAO's Autocrat program made deliberate simplifications. Since [[MetaDAOs Autocrat program implements futarchy through conditional token markets where proposals create parallel pass and fail universes settled by time-weighted average price over a three-day window]], the TWAP settlement over 3 days is itself a simplification — Hanson's design is more complex. The conditional token approach (pass tokens vs fail tokens) makes the mechanism legible to traders without game theory backgrounds.
+
+Futardio represents a second round of simplification. Where MetaDAO ICOs required curation and governance proposals, Futardio automates the process: time-based preference curves, hard caps, minimum thresholds, fully automated execution. Each layer of simplification trades theoretical optimality for practical adoption.
+
+This pattern is general. Since [[futarchy adoption faces friction from token price psychology proposal complexity and liquidity requirements]], every friction point is a simplification opportunity. The path to adoption runs through making the mechanism feel natural to users, not through proving it's optimal to theorists. MetaDAO's success comes not from implementing Hanson's design faithfully, but from knowing which parts to keep (conditional markets, TWAP settlement) and which to discard (random outcomes, complex participation requirements).
+
+## Evidence
+
+- @metanallok X archive (Mar 2026): "Robin wanted random proposal outcomes — impractical for production"
+- MetaDAO Autocrat: simplified conditional token design vs Hanson's original
+- Futardio: further simplification — automated, permissionless, minimal user decisions
+- Adoption data: 8 curated launches + 34 permissionless launches in first 2 days of Futardio — simplification drives throughput
+
+## Challenges
+
+- Simplifications may remove the very properties that make futarchy valuable — if random outcomes prevent manipulation, removing them may introduce manipulation vectors that haven't been exploited yet
+- The claim could be trivially true — every technology simplifies for production. The interesting question is which simplifications are safe and which are dangerous
+- MetaDAO's current scale ($219M total futarchy marketcap) may be too small to attract sophisticated attacks that the removed mechanisms were designed to prevent
+- Hanson might argue that MetaDAO's version isn't really futarchy at all — just conditional prediction markets used for governance, which is a narrower claim
+
+---
+
+Relevant Notes:
+- [[MetaDAOs Autocrat program implements futarchy through conditional token markets where proposals create parallel pass and fail universes settled by time-weighted average price over a three-day window]] — the simplified implementation
+- [[futarchy adoption faces friction from token price psychology proposal complexity and liquidity requirements]] — each friction point is a simplification target
+- [[futarchy is manipulation-resistant because attack attempts create profitable opportunities for defenders]] — does manipulation resistance survive simplification?
+
+Topics:
+- [[internet finance and decision markets]]

domains/internet-finance/futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent.md

@@ -33,6 +33,10 @@ Critically, the proposal nullifies a prior 90-day restriction on buybacks/liquid
 - Market data: 97% pass, $581K volume, +9.43% TWAP spread
 - Material misrepresentation: $5B/$2M claimed vs $2B/$500K actual, activity collapse post-ICO
 - Three buyback proposals already executed in MetaDAO ecosystem (Paystream, Ranger, Turbine Cash) — liquidation is the most extreme application of the same mechanism
+- **Liquidation executed (Mar 2026):** $5M USDC distributed back to Ranger token holders — the mechanism completed its full cycle from proposal to enforcement to payout
+- **Decision market forensics (@01Resolved):** 92.41% pass-aligned, 33 unique traders, $119K decision market volume — small but decisive trader base
+- **Hurupay minimum raise failure:** Separate protection layer — when an ICO doesn't reach minimum raise threshold, all funds return automatically. Not a liquidation event but a softer enforcement mechanism. No investor lost money on a project that didn't launch.
+- **Proph3t framing (@metaproph3t X archive):** "the number one selling point of ownership coins is that they are anti-rug" — the co-founder positions enforcement as the primary value proposition, not governance quality
 
 ## Challenges
 

domains/internet-finance/ownership coins primary value proposition is investor protection not governance quality because anti-rug enforcement through market-governed liquidation creates credible exit guarantees that no amount of decision optimization can match.md

@@ -0,0 +1,47 @@
+---
+type: claim
+domain: internet-finance
+description: "Proph3t explicitly states 'the number one selling point of ownership coins is that they are anti-rug' — reframing the value proposition from better governance to safer investment, with Ranger liquidation as the proof event"
+confidence: experimental
+source: "rio, based on @metaproph3t X archive (Mar 2026) and Ranger Finance liquidation"
+created: 2026-03-09
+depends_on:
+  - "@metaproph3t: 'the number one selling point of ownership coins is that they are anti-rug'"
+  - "Ranger liquidation: $5M USDC returned to holders through futarchy-governed enforcement"
+  - "8/8 MetaDAO ICOs above launch price — zero investor losses"
+  - "Hurupay minimum raise failure — funds returned automatically"
+---
+
+# Ownership coins primary value proposition is investor protection not governance quality because anti-rug enforcement through market-governed liquidation creates credible exit guarantees that no amount of decision optimization can match
+
+The MetaDAO ecosystem reveals a hierarchy of value that differs from the academic futarchy narrative. Robin Hanson pitched futarchy as a mechanism for better governance decisions. MetaDAO's co-founder Proph3t says "the number one selling point of ownership coins is that they are anti-rug." This isn't rhetorical emphasis — it's a strategic prioritization that reflects what actually drives adoption.
+
+The evidence supports the reframe. The MetaDAO ecosystem's strongest signal is not "we make better decisions than token voting" — it's "8 out of 8 ICOs are above launch price, zero investors rugged, and when Ranger misrepresented their metrics, the market forced $5M USDC back to holders." The Hurupay ICO that failed to reach minimum raise threshold returned all funds automatically. The protection mechanism works at every level: minimum raise thresholds catch non-viable projects, TWAP buybacks catch underperformance, and full liquidation catches misrepresentation.
+
+This reframe matters because it changes the competitive positioning. Governance quality is abstract — hard to sell, hard to measure, hard for retail investors to evaluate. Anti-rug is concrete: did you lose money? No? The mechanism worked. Since [[futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent]], the liquidation mechanism is not one feature among many — it is the foundation that everything else rests on.
+
+Proph3t's other framing reinforces this: he distinguishes "market oversight" from "community governance." The market doesn't vote on whether projects should exist — it prices whether they're delivering value, and enforces consequences when they're not. This is oversight, not governance. The distinction matters because oversight has a clear value proposition (protection) while governance has an ambiguous one (better decisions, maybe, sometimes).
+
+## Evidence
+
+- @metaproph3t X archive (Mar 2026): "the number one selling point of ownership coins is that they are anti-rug"
+- Ranger liquidation: $5M USDC returned, 92.41% pass-aligned, 33 traders, $119K decision market volume
+- MetaDAO ICO track record: 8/8 above launch price, $25.6M raised, $390M committed
+- Hurupay: failed to reach minimum raise, all funds returned automatically — soft protection mechanism
+- Proph3t framing: "market oversight not community governance"
+
+## Challenges
+
+- The anti-rug framing may attract investors who want protection without engagement, creating passive holder bases that thin futarchy markets further — since [[MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions]], this could worsen participation problems
+- Governance quality and investor protection are not actually separable — better governance decisions reduce the need for liquidation enforcement, so downplaying governance quality may undermine the mechanism that creates protection
+- The "8/8 above ICO price" record is from a bull market with curated launches — permissionless Futardio launches will test whether the anti-rug mechanism holds at scale without curation
+
+---
+
+Relevant Notes:
+- [[futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent]] — the enforcement mechanism that makes anti-rug credible
+- [[MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale]] — parent claim this reframes
+- [[coin price is the fairest objective function for asset futarchy]] — "number go up" as objective function supports the protection framing: you either deliver value or get liquidated
+
+Topics:
+- [[internet finance and decision markets]]

domains/internet-finance/stablecoin flow velocity is a better predictor of DeFi protocol health than static TVL because flows measure capital utilization while TVL only measures capital parked.md

@@ -0,0 +1,44 @@
+---
+type: claim
+domain: internet-finance
+description: "oxranga argues stablecoin flows > TVL as the primary DeFi health metric — a snapshot of capital parked tells you less than a movie of capital moving, and protocols with high flow velocity but low TVL may be healthier than those with high TVL but stagnant capital"
+confidence: speculative
+source: "rio, based on @oxranga X archive (Mar 2026)"
+created: 2026-03-09
+depends_on:
+  - "@oxranga: 'stablecoin flows > TVL' as metric framework"
+  - "DeFi industry standard: TVL as primary protocol health metric"
+---
+
+# Stablecoin flow velocity is a better predictor of DeFi protocol health than static TVL because flows measure capital utilization while TVL only measures capital parked
+
+TVL (Total Value Locked) is the default metric for evaluating DeFi protocols. oxranga (Solomon Labs co-founder) argues this is fundamentally misleading: "stablecoin flows > TVL." A protocol with $100M TVL and $1M daily flows is less healthy than a protocol with $10M TVL and $50M daily flows — the first is a parking lot, the second is a highway.
+
+The insight maps to economics directly. TVL is analogous to money supply (M2) while flow velocity is analogous to monetary velocity (V). Since GDP = M × V, protocol economic activity depends on both capital present and capital moving. TVL-only analysis is like measuring an economy by its savings rate and ignoring all transactions.
+
+This matters for ownership coin valuation. Since [[coin price is the fairest objective function for asset futarchy]], and coin price should reflect underlying economic value, metrics that better capture economic activity produce better price signals. If futarchy markets are pricing based on TVL (capital parked) rather than flow velocity (capital utilized), they may be mispricing protocols.
+
+oxranga's complementary insight — "moats were made of friction" — connects this to our disruption framework. Since [[transaction costs determine organizational boundaries because firms exist to economize on the costs of using markets and the boundary shifts when technology changes the relative cost of internal coordination versus external contracting]], DeFi protocols that built moats on user friction (complex UIs, high switching costs) lose those moats as composability improves. Flow velocity becomes the durable metric because it measures actual utility, not friction-trapped capital.
+
+## Evidence
+
+- @oxranga X archive (Mar 2026): "stablecoin flows > TVL" framework
+- DeFi industry practice: TVL reported by DefiLlama, DappRadar as primary metric
+- Economic analogy: monetary velocity (V) as better economic health indicator than money supply (M2) alone
+- oxranga: "moats were made of friction" — friction-based TVL is not durable
+
+## Challenges
+
+- Flow velocity can be gamed more easily than TVL — wash trading inflates flows without economic activity, while TVL requires actual capital commitment
+- TVL and flow velocity measure different things: TVL reflects capital confidence (willingness to lock), flows reflect capital utility (willingness to transact). Both matter.
+- The claim is framed as "better predictor" but no empirical comparison exists — this is a conceptual argument from analogy to monetary economics, not a tested hypothesis
+- High flow velocity with low TVL could indicate capital that doesn't trust the protocol enough to stay — fleeting interactions rather than sustained engagement
+
+---
+
+Relevant Notes:
+- [[coin price is the fairest objective function for asset futarchy]] — better protocol metrics produce better futarchy price signals
+- [[transaction costs determine organizational boundaries because firms exist to economize on the costs of using markets and the boundary shifts when technology changes the relative cost of internal coordination versus external contracting]] — oxranga's "moats were made of friction" maps directly
+
+Topics:
+- [[internet finance and decision markets]]

domains/internet-finance/time-based token vesting is hedgeable making standard lockups meaningless as alignment mechanisms because investors can short-sell to neutralize lockup exposure while appearing locked.md

@@ -0,0 +1,48 @@
+---
+type: claim
+domain: internet-finance
+description: "Felipe Montealegre's Token Problem thesis — standard time-based vesting creates the illusion of alignment while investors hedge away exposure through short-selling, making lockups performative rather than functional"
+confidence: experimental
+source: "rio, based on @TheiaResearch X archive (Mar 2026), DAS NYC keynote preview"
+created: 2026-03-09
+depends_on:
+  - "@TheiaResearch: Token Problem thesis — time-based vesting is hedgeable"
+  - "DAS NYC keynote (March 25 2026): 'The Token Problem and Proposed Solutions'"
+  - "Standard token launch practice: 12-36 month cliff + linear unlock vesting schedules"
+---
+
+# Time-based token vesting is hedgeable making standard lockups meaningless as alignment mechanisms because investors can short-sell to neutralize lockup exposure while appearing locked
+
+The standard crypto token launch uses time-based vesting to align team and investor incentives — tokens unlock gradually over 12-36 months, theoretically preventing dump-and-run behavior. Felipe Montealegre (Theia Research) argues this is structurally broken: any investor with market access can short-sell their locked position to neutralize exposure while appearing locked.
+
+The mechanism failure is straightforward. If an investor holds 1M tokens locked for 12 months, they can borrow and sell 1M tokens (or equivalent exposure via perps/options) to achieve market-neutral positioning. They are technically "locked" but economically "out." The vesting schedule constrains their wallet behavior but not their portfolio exposure. The lockup is performative — it creates the appearance of alignment without the substance.
+
+This matters because the entire token launch industry is built on the assumption that vesting creates alignment. VCs negotiate lockup terms, projects announce vesting schedules as credibility signals, and retail investors interpret lockups as commitment. If vesting is hedgeable, this entire signaling apparatus is theater.
+
+The implication for ownership coins is significant. Since [[futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent]], ownership coins don't rely on vesting for alignment — they rely on governance enforcement. You can't hedge away a governance right that is actively pricing your decisions and can liquidate your project. Futarchy governance is an alignment mechanism that resists hedging because the alignment comes from ongoing market oversight, not a time-locked contract.
+
+Felipe is presenting the full argument at Blockworks DAS NYC on March 25 — this will be the highest-profile articulation of why standard token launches are broken and what the alternative looks like.
+
+## Evidence
+
+- @TheiaResearch X archive (Mar 2026): Token Problem thesis
+- DAS NYC keynote preview: "The Token Problem and Proposed Solutions" (March 25 2026)
+- Standard practice: major token launches (Arbitrum, Optimism, Sui, Aptos) all use time-based vesting
+- Hedging infrastructure: perp markets, OTC forwards, and options exist for most major token launches, enabling vesting neutralization
+
+## Challenges
+
+- Not all investors can efficiently hedge — small holders, retail, and teams with concentrated positions face higher hedging costs and counterparty risk
+- The claim is strongest for large VCs with market access — retail investors genuinely can't hedge their lockups, so vesting does create alignment at the small-holder level
+- If hedging is so effective, why do VCs still negotiate vesting terms? Possible answers: signaling to retail, regulatory cover, or because hedging is costly enough to create partial alignment
+- The full argument hasn't been publicly presented yet (DAS keynote is March 25) — current evidence is from tweet-level previews, not the complete thesis
+
+---
+
+Relevant Notes:
+- [[futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent]] — ownership coins solve the alignment problem that vesting fails to solve
+- [[cryptos primary use case is capital formation not payments or store of value because permissionless token issuance solves the fundraising bottleneck that solo founders and small teams face]] — if the capital formation mechanism (vesting) is broken, the primary use case needs a fix
+- [[token launches are hybrid-value auctions where common-value price discovery and private-value community alignment require different mechanisms because auction theory optimized for one degrades the other]] — vesting failure is another case where a single mechanism (time lock) can't serve multiple objectives (alignment + price discovery)
+
+Topics:
+- [[internet finance and decision markets]]

foundations/collective-intelligence/decentralized information aggregation outperforms centralized planning because dispersed knowledge cannot be collected into a single mind but can be coordinated through price signals that encode local information into globally accessible indicators.md

@@ -0,0 +1,72 @@
+---
+type: claim
+domain: collective-intelligence
+description: "Hayek's knowledge problem — no central planner can access the dispersed, tacit, time-and-place-specific knowledge that market participants possess, but price signals aggregate this knowledge into actionable information — is the theoretical foundation for prediction markets, futarchy, and any system that coordinates through information rather than authority"
+confidence: proven
+source: "Hayek, 'The Use of Knowledge in Society' (1945); Fama, 'Efficient Capital Markets' (1970); Grossman & Stiglitz (1980); Surowiecki, 'The Wisdom of Crowds' (2004); Nobel Prize in Economics 1974 (Hayek), 2013 (Fama)"
+created: 2026-03-08
+---
+
+# Decentralized information aggregation outperforms centralized planning because dispersed knowledge cannot be collected into a single mind but can be coordinated through price signals that encode local information into globally accessible indicators
+
+Friedrich Hayek (1945) identified the fundamental problem of economic coordination: the knowledge required for rational resource allocation is never concentrated in a single mind. It is dispersed among millions of individuals as "knowledge of the particular circumstances of time and place" — tacit, local, perishable information that cannot be transmitted through any reporting system. The economic problem is not how to allocate given resources optimally (the calculation problem), but how to coordinate when no one possesses the information needed to calculate the optimum.
+
+## The price mechanism as information aggregator
+
+Hayek's solution: the price system. Prices aggregate dispersed information into a single signal that guides action without requiring anyone to understand the full picture. When a natural disaster disrupts tin supply, the price of tin rises. Every tin user worldwide adjusts their behavior — conserving tin, substituting alternatives, expanding production — without knowing WHY the price rose. The price signal encodes the local knowledge of the disruption and transmits it globally at near-zero cost.
+
+This mechanism has three properties that no centralized system can replicate:
+
+1. **Tacit knowledge inclusion.** Much dispersed knowledge is tacit — the factory manager's sense that demand is shifting, the trader's intuition about counterparty risk. Tacit knowledge cannot be articulated in reports but CAN be expressed through market action (buying, selling, pricing). Markets aggregate knowledge that cannot be communicated any other way.
+
+2. **Incentive compatibility.** Market participants who act on accurate private information profit; those who act on inaccurate information lose. The market mechanism creates incentive compatibility — honest information revelation is the profitable strategy. This is why [[speculative markets aggregate information through incentive and selection effects not wisdom of crowds]] — the "incentive effect" is Hayek's price mechanism formalized through [[mechanism design enables incentive-compatible coordination by constructing rules under which self-interested agents voluntarily reveal private information and take socially optimal actions|mechanism design theory]].
+
+3. **Dynamic updating.** Prices adjust continuously as new information arrives. No committee meeting, no reporting cycle, no bureaucratic delay. The information aggregation is real-time and automatic.
+
+## The Efficient Market Hypothesis and its limits
+
+Fama (1970) formalized Hayek's insight as the Efficient Market Hypothesis: asset prices reflect all available information. In the strong form, no one can consistently outperform the market because prices already incorporate all public and private information.
+
+Grossman and Stiglitz (1980) identified the paradox: if prices fully reflect all information, no one has incentive to pay the cost of acquiring information — but if no one acquires information, prices cannot reflect it. The resolution: markets are informationally efficient to the degree that information-gathering costs are compensated by trading profits. Prices are not perfectly efficient but are efficient enough that systematic exploitation is difficult.
+
+This paradox directly explains [[MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions]] — when a decision is obvious, the market price reflects the consensus immediately, and no one profits from trading on information everyone already has. Low volume in uncontested decisions is not a failure but a feature of efficient information aggregation.
+
+## Why centralized alternatives fail
+
+The Soviet calculation debate (Mises 1920, Hayek 1945) established that centralized planning fails not because planners are stupid or corrupt, but because the information problem is structurally unsolvable. Even an omniscient, benevolent planner could not solve it because:
+
+1. The relevant knowledge changes continuously — any snapshot is stale before it arrives
+2. Tacit knowledge cannot be transmitted — it can only be expressed through action
+3. Aggregation requires incentives — without profit/loss signals, there is no mechanism to elicit honest information revelation
+
+This is not an argument against all coordination — it is an argument that coordination through prices outperforms coordination through authority when the relevant knowledge is dispersed. When knowledge IS concentrated (a small team, a single expert domain), hierarchy can outperform markets. The question is always: where is the relevant knowledge?
+
+## Why this is foundational
+
+Information aggregation theory provides the theoretical grounding for:
+
+- **Prediction markets:** [[speculative markets aggregate information through incentive and selection effects not wisdom of crowds]] — prediction market accuracy IS Hayek's price mechanism applied to forecasting.
+
+- **Futarchy:** [[futarchy is manipulation-resistant because attack attempts create profitable opportunities for defenders]] — futarchy works because the price mechanism aggregates dispersed governance knowledge more efficiently than voting.
+
+- **The internet finance thesis:** [[internet finance generates 50 to 100 basis points of additional annual GDP growth by unlocking capital allocation to previously inaccessible assets and eliminating intermediation friction]] — the GDP impact comes from extending the price mechanism to assets and decisions previously coordinated through hierarchy.
+
+- **Hayek's broader framework:** [[Hayek argued that designed rules of just conduct enable spontaneous order of greater complexity than deliberate arrangement could achieve]] — the knowledge problem is WHY designed rules outperform designed outcomes. Rules enable the price mechanism; designed outcomes require the impossible centralization of dispersed knowledge.
+
+- **Collective intelligence:** [[humanity is a superorganism that can communicate but not yet think — the internet built the nervous system but not the brain]] — the price mechanism is the most successful existing form of collective cognition. It proves that distributed information aggregation works; the question is whether it can be extended beyond pricing.
+
+---
+
+Relevant Notes:
+- [[speculative markets aggregate information through incentive and selection effects not wisdom of crowds]] — prediction markets as formalized Hayekian information aggregation
+- [[futarchy is manipulation-resistant because attack attempts create profitable opportunities for defenders]] — futarchy as price-mechanism governance
+- [[mechanism design enables incentive-compatible coordination by constructing rules under which self-interested agents voluntarily reveal private information and take socially optimal actions]] — mechanism design formalizes Hayek's insight about incentive-compatible information revelation
+- [[Hayek argued that designed rules of just conduct enable spontaneous order of greater complexity than deliberate arrangement could achieve]] — the broader Hayekian framework that the knowledge problem grounds
+- [[internet finance generates 50 to 100 basis points of additional annual GDP growth by unlocking capital allocation to previously inaccessible assets and eliminating intermediation friction]] — extending price mechanisms to new domains
+- [[MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions]] — the Grossman-Stiglitz paradox in practice
+- [[humanity is a superorganism that can communicate but not yet think — the internet built the nervous system but not the brain]] — prices as existing collective cognition
+- [[coordination failures arise from individually rational strategies that produce collectively irrational outcomes because the Nash equilibrium of non-cooperation dominates when trust and enforcement are absent]] — information aggregation solves a different problem than coordination failures — the former is about knowledge, the latter about incentives
+
+Topics:
+- [[coordination mechanisms]]
+- [[internet finance and decision markets]]

foundations/critical-systems/_map.md

@@ -25,6 +25,11 @@ Self-organized criticality, emergence, and free energy minimization describe how
 - [[the universal disruption cycle is how systems of greedy agents perform global optimization because local convergence creates fragility that triggers restructuring toward greater efficiency]] — SOC applied to industry transitions
 - [[what matters in industry transitions is the slope not the trigger because self-organized criticality means accumulated fragility determines the avalanche while the specific disruption event is irrelevant]] — slope reading
 
+## Complex Adaptive Systems
+- [[complex adaptive systems are defined by four properties that distinguish them from merely complicated systems agents with schemata adaptation through feedback nonlinear interactions and emergent macro-patterns]] — Holland's foundational framework: the boundary between complicated and complex is adaptation
+- [[fitness landscape ruggedness determines whether adaptive systems find good solutions because smooth landscapes reward hill-climbing while rugged landscapes trap agents in local optima and require exploration or recombination to escape]] — Kauffman's NK model: landscape structure determines search strategy effectiveness
+- [[coevolution means agents fitness landscapes shift as other agents adapt creating a world where standing still is falling behind and the optimal strategy depends on what everyone else is doing]] — Red Queen dynamics: coupled adaptation prevents equilibrium and self-organizes to edge of chaos
+
 ## Free Energy Principle
 - [[biological systems minimize free energy to maintain their states and resist entropic decay]] — the core principle
 - [[Markov blankets enable complex systems to maintain identity while interacting with environment through nested statistical boundaries]] — boundary architecture (used in agent design)

foundations/critical-systems/coevolution means agents fitness landscapes shift as other agents adapt creating a world where standing still is falling behind and the optimal strategy depends on what everyone else is doing.md

@@ -0,0 +1,38 @@
+---
+type: claim
+domain: critical-systems
+description: "The Red Queen effect in CAS: when your fitness depends on other adapting agents, the landscape itself moves — static optimization becomes impossible and the system never reaches equilibrium"
+confidence: likely
+source: "Kauffman & Johnsen 'Coevolution to the Edge of Chaos' (1991); Arthur 'Complexity and the Economy' (2015); Van Valen 'A New Evolutionary Law' (1973)"
+created: 2026-03-08
+---
+
+# Coevolution means agents' fitness landscapes shift as other agents adapt, creating a world where standing still is falling behind and the optimal strategy depends on what everyone else is doing
+
+Van Valen (1973) identified the Red Queen effect: species in ecosystems show constant extinction rates regardless of how long they've existed, because the environment is composed of other adapting species. A species that stops adapting doesn't maintain its fitness — it declines, because its competitors and predators continue improving. "It takes all the running you can do, to keep in the same place."
+
+Kauffman and Johnsen (1991) formalized this through coupled NK landscapes. When species A adapts (changes its genotype to climb its fitness landscape), the fitness landscape of species B *deforms* — peaks shift, valleys appear where plains were. The more tightly coupled the species (higher inter-species K), the more violently the landscapes deform under mutual adaptation. At high coupling, each species' adaptation makes the other's landscape more rugged, potentially triggering an "avalanche" of coevolutionary changes across the entire ecosystem.
+
+Their central finding: coevolutionary systems self-organize to the "edge of chaos" — the critical boundary between frozen order (where no species adapts because landscapes are too stable) and chaotic turnover (where adaptation is futile because landscapes change faster than agents can track). At the edge, adaptation is possible but never complete, producing the perpetual dynamism observed in real ecosystems, markets, and technology races.
+
+Arthur (2015) showed the same dynamic in economic competition: firms' strategic choices change the competitive landscape for other firms. A platform that achieves network effects doesn't just climb its own fitness peak — it collapses rivals' peaks. The result is not convergence to equilibrium but perpetual coevolutionary dynamics where strategy must account for others' adaptation, not just current conditions.
+
+This has three operational implications:
+
+1. **Static optimization fails.** Any strategy optimized for the current landscape becomes suboptimal as other agents adapt. This is why [[equilibrium models of complex systems are fundamentally misleading]] — they assume a fixed landscape.
+
+2. **The arms race is structural, not optional.** Agents that stop adapting don't hold their position — they lose it. This applies equally to biological species, competing firms, and AI safety labs facing competitive pressure.
+
+3. **Coupling strength determines dynamics.** Loosely coupled agents coevolve slowly (gradual improvement). Tightly coupled agents produce volatile dynamics where one agent's breakthrough can cascade into wholesale restructuring. The coupling parameter — not individual agent capability — determines whether the system is stable, dynamic, or chaotic.
+
+---
+
+Relevant Notes:
+- [[the alignment tax creates a structural race to the bottom because safety training costs capability and rational competitors skip it]] — the alignment tax IS a coevolutionary trap: labs that invest in safety change their competitive landscape adversely, and the Red Queen effect punishes them for "standing still" on capability
+- [[voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints]] — voluntary pledges are static strategies on a coevolutionary landscape; they fail because the landscape shifts as competitors adapt
+- [[minsky's financial instability hypothesis shows that stability breeds instability as good times incentivize leverage and risk-taking that fragilize the system until shocks trigger cascades]] — Minsky's instability IS coevolutionary dynamics in finance: firms adapt to stability by increasing leverage, which deforms the landscape toward fragility
+- [[the universal disruption cycle is how systems of greedy agents perform global optimization because local convergence creates fragility that triggers restructuring toward greater efficiency]] — disruption cycles are coevolutionary avalanches at the edge of chaos
+- [[multipolar failure from competing aligned AI systems may pose greater existential risk than any single misaligned superintelligence]] — multipolar failure is the catastrophic coevolutionary outcome: individually aligned agents whose mutual adaptation produces collectively destructive dynamics
+
+Topics:
+- [[foundations/critical-systems/_map]]

foundations/critical-systems/complex adaptive systems are defined by four properties that distinguish them from merely complicated systems agents with schemata adaptation through feedback nonlinear interactions and emergent macro-patterns.md

@@ -0,0 +1,36 @@
+---
+type: claim
+domain: critical-systems
+description: "Holland's CAS framework identifies the boundary between complicated and complex: a jet engine has millions of parts but no adaptation — a market with three traders can produce emergent behavior no participant intended"
+confidence: likely
+source: "Holland 'Hidden Order' (1995), 'Emergence' (1998); Mitchell 'Complexity: A Guided Tour' (2009); Arthur 'Complexity and the Economy' (2015)"
+created: 2026-03-08
+---
+
+# Complex adaptive systems are defined by four properties that distinguish them from merely complicated systems: agents with schemata, adaptation through feedback, nonlinear interactions, and emergent macro-patterns
+
+A complex adaptive system (CAS) is not simply a system with many parts. A Boeing 747 has six million parts but is merely *complicated* — its behavior follows predictably from its design. A CAS differs on four properties, first formalized by Holland (1995):
+
+1. **Agents with schemata.** The components are agents that carry internal models (schemata) of their environment and act on them. Unlike gears or circuits, they interpret signals and modify behavior based on those interpretations. Holland demonstrated that even minimal schema — classifier rules that compete for activation — produce adaptive behavior in simulated economies.
+
+2. **Adaptation through feedback.** Agents revise their schemata based on outcomes. Successful strategies proliferate; unsuccessful ones get revised or abandoned. This is not central design — it's distributed learning. Arthur (2015) showed that economic agents who update heterogeneous expectations based on outcomes reproduce real market phenomena (clustering, bubbles, crashes) that equilibrium models cannot.
+
+3. **Nonlinear interactions.** Small inputs can produce large effects and vice versa. Agent actions change the environment, which changes the signals other agents receive, which changes their actions. Mitchell (2009) catalogs how this nonlinearity produces qualitatively different behavior at each scale — ant pheromone trails, immune system learning, market dynamics — all from local rules with no global controller.
+
+4. **Emergent macro-patterns.** The system exhibits coherent large-scale patterns — market prices, ecosystem niches, traffic flows — that no individual agent intended or controls. These patterns are not reducible to individual behavior: knowing everything about individual ants tells you nothing about colony architecture.
+
+The boundary between complicated and complex is *adaptation*. If components respond to outcomes by modifying their behavior, the system is complex. If they don't, it's merely complicated. This distinction matters operationally: complicated systems can be engineered top-down, while CAS can only be cultivated through enabling constraints.
+
+Holland's framework is domain-independent — the same four properties appear in immune systems (antibodies as agents with schemata), ecosystems (organisms adapting to niches), markets (traders updating strategies), and AI collectives (agents revising policies). The universality of the pattern is what makes it foundational rather than domain-specific.
+
+---
+
+Relevant Notes:
+- [[emergence is the fundamental pattern of intelligence from ant colonies to brains to civilizations]] — emergence is the fourth CAS property; this claim provides the theoretical framework that explains why emergence recurs
+- [[companies and people are greedy algorithms that hill-climb toward local optima and require external perturbation to escape suboptimal equilibria]] — greedy hill-climbing is the simplest form of CAS adaptation (property 2), where agents have schemata but update them only locally
+- [[enabling constraints create possibility spaces for emergence while governing constraints dictate specific outcomes]] — CAS design requires enabling constraints precisely because top-down governance contradicts the adaptation property
+- [[designing coordination rules is categorically different from designing coordination outcomes as nine intellectual traditions independently confirm]] — CAS theory is one of those nine traditions; the distinction maps to enabling vs governing constraints
+- [[equilibrium models of complex systems are fundamentally misleading because systems in balance cannot exhibit catastrophes fractals or history]] — equilibrium models fail for CAS specifically because adaptation (property 2) and nonlinearity (property 3) prevent convergence
+
+Topics:
+- [[foundations/critical-systems/_map]]

foundations/critical-systems/fitness landscape ruggedness determines whether adaptive systems find good solutions because smooth landscapes reward hill-climbing while rugged landscapes trap agents in local optima and require exploration or recombination to escape.md

@@ -0,0 +1,36 @@
+---
+type: claim
+domain: critical-systems
+description: "Kauffman's NK model formalizes the intuition that some problems are navigable by incremental improvement while others require leaps — the tunable parameter K (epistatic interactions) controls landscape ruggedness and therefore the effectiveness of local search"
+confidence: likely
+source: "Kauffman 'The Origins of Order' (1993), 'At Home in the Universe' (1995); Levinthal 'Adaptation on Rugged Landscapes' (1997); Page 'The Difference' (2007)"
+created: 2026-03-08
+---
+
+# Fitness landscape ruggedness determines whether adaptive systems find good solutions because smooth landscapes reward hill-climbing while rugged landscapes trap agents in local optima and require exploration or recombination to escape
+
+Kauffman's NK model (1993) provides the formal framework for understanding why some optimization problems yield to incremental improvement while others resist it. The model has two parameters: N (number of components) and K (epistatic interactions — how many other components each component's contribution depends on).
+
+When K = 0, each component's fitness contribution is independent. The landscape is smooth with a single global peak — hill-climbing works perfectly. When K = N-1 (maximum interaction), every component's contribution depends on every other component. The landscape becomes maximally rugged — essentially random — with an exponential number of local optima. Hill-climbing fails catastrophically because almost every peak is mediocre.
+
+The critical insight is that **real-world systems occupy the middle range**. Kauffman showed that at intermediate K values, landscapes have structure: correlated peaks clustered by quality, with navigable ridges connecting good solutions. This is where adaptation is hardest but most consequential — local search finds decent solutions but can't reach the best ones without some form of exploration beyond nearest neighbors.
+
+Levinthal (1997) applied this directly to organizational adaptation: firms that search only locally (incremental innovation) perform well on smooth landscapes but get trapped on mediocre peaks in rugged ones. Firms that occasionally make "long jumps" (radical innovation, recombination) sacrifice short-term performance but discover better peaks. The optimal search strategy depends on landscape ruggedness — which the searcher cannot directly observe.
+
+Page (2007) extended this to group problem-solving: diverse agents with different heuristics collectively explore more of a rugged landscape than homogeneous experts, because their different starting perspectives correspond to different search trajectories. This is why diversity outperforms individual excellence on hard problems — it's a landscape coverage argument, not a moral one.
+
+The framework explains several patterns across domains:
+- **Why modularity helps**: Reducing K through modular design smooths the landscape, making local search effective within modules while recombination happens between them
+- **Why diversity matters**: On rugged landscapes, the best single searcher is dominated by a diverse collection of mediocre searchers covering more territory
+- **Why exploration and exploitation must be balanced**: Pure exploitation (hill-climbing) gets trapped; pure exploration (random search) wastes effort on bad regions
+
+---
+
+Relevant Notes:
+- [[companies and people are greedy algorithms that hill-climb toward local optima and require external perturbation to escape suboptimal equilibria]] — this claim IS the greedy hill-climbing failure mode; the NK model explains precisely when and why it fails (high K)
+- [[partial connectivity produces better collective intelligence than full connectivity on complex problems because it preserves diversity]] — partial connectivity preserves diverse search trajectories on rugged landscapes, exactly as Page's framework predicts
+- [[collective intelligence requires diversity as a structural precondition not a moral preference]] — the NK model provides the formal mechanism: diversity covers more of the rugged landscape
+- [[the self-organized critical state is the most efficient state dynamically achievable even though a perfectly engineered state would perform better]] — the critical state lives on a rugged landscape where global optima are inaccessible to local search
+
+Topics:
+- [[foundations/critical-systems/_map]]

foundations/cultural-dynamics/_map.md

@@ -9,6 +9,16 @@ Cultural evolution, memetics, master narrative theory, and paradigm shifts expla
 - [[memeplexes survive by combining mutually reinforcing memes that protect each other from external challenge through untestability threats and identity attachment]] — how idea-systems persist
 - [[the strongest memeplexes align individual incentive with collective behavior creating self-validating feedback loops]] — the design target for LivingIP
 
+## Community Formation
+- [[human social cognition caps meaningful relationships at approximately 150 because neocortex size constrains the number of individuals whose behavior and relationships can be tracked]] — the cognitive ceiling on group size
+- [[social capital erodes when associational life declines because trust generalized reciprocity and civic norms are produced by repeated face-to-face interaction in voluntary organizations not by individual virtue]] — how trust infrastructure is built and depleted
+- [[collective action fails by default because rational individuals free-ride on group efforts when they cannot be excluded from benefits regardless of contribution]] — why groups don't naturally act in their shared interest
+- [[weak ties bridge otherwise disconnected clusters enabling information flow and opportunity access that strong ties within clusters cannot provide]] — the structural role of acquaintances
+
+## Selfplex and Identity
+- [[the self is a memeplex that persists because memes attached to a personal identity get copied more reliably than free-floating ideas]] — identity as replicator strategy
+- [[identity-protective cognition causes people to reject evidence that threatens their group identity even when they have the cognitive capacity to evaluate it correctly]] — why smarter people aren't less biased
+
 ## Propagation Dynamics
 - [[ideological adoption is a complex contagion requiring multiple reinforcing exposures from trusted sources not simple viral spread through weak ties]] — why ideas don't go viral like tweets
 - [[complex ideas propagate with higher fidelity through personal interaction than mass media because nuance requires bidirectional communication]] — fidelity vs reach tradeoff

foundations/cultural-dynamics/collective action fails by default because rational individuals free-ride on group efforts when they cannot be excluded from benefits regardless of contribution.md

@@ -0,0 +1,37 @@
+---
+type: claim
+domain: cultural-dynamics
+description: "Olson's logic of collective action: large groups systematically underprovide public goods because individual incentives favor free-riding, and this problem worsens with group size — small concentrated groups outorganize large diffuse ones"
+confidence: proven
+source: "Olson 1965 The Logic of Collective Action; Ostrom 1990 Governing the Commons (boundary condition)"
+created: 2026-03-08
+---
+
+# collective action fails by default because rational individuals free-ride on group efforts when they cannot be excluded from benefits regardless of contribution
+
+Mancur Olson's *The Logic of Collective Action* (1965) demolished the assumption that groups with shared interests will naturally act to advance those interests. The logic is straightforward: if a public good (clean air, national defense, industry lobbying) benefits everyone in a group regardless of whether they contributed, the individually rational strategy is to free-ride — enjoy the benefit without paying the cost. When everyone follows this logic, the public good is underprovided or not provided at all.
+
+Three mechanisms make large groups systematically worse at collective action than small ones. First, **imperceptibility**: in a large group, each individual's contribution is negligible — your donation to a million-person cause is invisible, reducing motivation. Second, **monitoring difficulty**: in large groups, it is harder to identify and sanction free-riders. Third, **asymmetric benefits**: in small groups, concentrated benefits per member can exceed individual costs, making action rational even without enforcement. The steel industry (few large firms, each with massive individual stake) organizes effectively; consumers (millions of people, each with tiny individual stake) do not.
+
+This produces Olson's central prediction: **small, concentrated groups will outorganize large, diffuse ones**, even when the large group's aggregate interest is greater. Industry lobbies defeat consumer interests. Medical associations restrict competition more effectively than patients can demand it. The concentrated few overcome the diffuse many not because they care more, but because the per-member stakes justify the per-member costs.
+
+Olson identifies two solutions: **selective incentives** (benefits available only to contributors — insurance, publications, social access) and **coercion** (mandatory participation — union closed shops, taxation). Both work by changing the individual payoff structure to make contribution rational regardless of others' behavior.
+
+**The Ostrom boundary condition.** [[Ostrom proved communities self-govern shared resources when eight design principles are met without requiring state control or privatization]]. Ostrom demonstrated that Olson's logic, while correct for anonymous large groups, does not hold for communities with clear boundaries, monitoring capacity, graduated sanctions, and local conflict resolution. Her design principles are precisely the institutional mechanisms that overcome Olson's free-rider problem without requiring either privatization or state coercion. The question is not whether collective action fails — it does, by default. The question is what institutional designs prevent the default from holding.
+
+For community-based coordination systems, Olson's logic is the baseline prediction: without explicit mechanism design, participation declines as group size increases. Selective incentives (ownership stakes, attribution, reputation) and Ostrom-style governance principles are not optional enhancements — they are the minimum requirements for sustained collective action.
+
+---
+
+Relevant Notes:
+- [[Ostrom proved communities self-govern shared resources when eight design principles are met without requiring state control or privatization]] — the boundary condition showing collective action CAN succeed with specific institutional design
+- [[coordination failures arise from individually rational strategies that produce collectively irrational outcomes because the Nash equilibrium of non-cooperation dominates when trust and enforcement are absent]] — Olson's free-rider problem is the specific mechanism by which coordination failure manifests in public goods provision
+- [[gamified contribution with ownership stakes aligns individual sharing with collective intelligence growth]] — selective incentives (ownership) as the mechanism design solution to Olson's free-rider problem
+- [[community ownership accelerates growth through aligned evangelism not passive holding]] — ownership transforms free-riders into stakeholders by changing the individual payoff structure
+- [[history is shaped by coordinated minorities with clear purpose not by majorities]] — Olson explains WHY: small groups can solve the collective action problem that large groups cannot
+- [[human social cognition caps meaningful relationships at approximately 150 because neocortex size constrains the number of individuals whose behavior and relationships can be tracked]] — Dunbar's number defines the scale at which informal monitoring works; beyond it, Olson's monitoring difficulty dominates
+- [[social capital erodes when associational life declines because trust generalized reciprocity and civic norms are produced by repeated face-to-face interaction in voluntary organizations not by individual virtue]] — social capital is the informal mechanism that mitigates free-riding through reciprocity norms and reputational accountability
+
+Topics:
+- [[memetics and cultural evolution]]
+- [[cultural-dynamics/_map]]

foundations/cultural-dynamics/human social cognition caps meaningful relationships at approximately 150 because neocortex size constrains the number of individuals whose behavior and relationships can be tracked.md

@@ -0,0 +1,36 @@
+---
+type: claim
+domain: cultural-dynamics
+description: "Dunbar's number (~150) is a cognitive constraint on group size derived from the correlation between primate neocortex ratio and social group size, with layered structure at 5/15/50/150/500/1500 reflecting decreasing emotional closeness"
+confidence: likely
+source: "Dunbar 1992 Journal of Human Evolution; Dunbar 2010 How Many Friends Does One Person Need?"
+created: 2026-03-08
+---
+
+# human social cognition caps meaningful relationships at approximately 150 because neocortex size constrains the number of individuals whose behavior and relationships can be tracked
+
+Robin Dunbar's social brain hypothesis establishes that primate social group size correlates with neocortex ratio — the proportion of brain devoted to the neocortex. For humans, this predicts a mean group size of approximately 150, a number that recurs across diverse social structures: Neolithic farming villages, Roman military centuries, Hutterite communities that split at ~150, average personal network sizes in modern surveys, and the typical size of functional organizational units.
+
+The mechanism is cognitive, not social. Maintaining a relationship requires tracking not just who someone is, but their relationships to others, their reliability, their emotional state, and shared history. This mentalizing capacity — modeling others' mental states and social connections — scales with neocortex volume. At ~150, the combinatorial explosion of third-party relationships exceeds what human cognitive architecture can track. Beyond this number, relationships become transactional rather than trust-based, requiring formal rules, hierarchies, and institutions to maintain cohesion.
+
+The number is not a hard boundary but the center of a layered structure. Dunbar identifies concentric circles of decreasing closeness: ~5 (intimate support group), ~15 (sympathy group — those whose death would be devastating), ~50 (close friends), ~150 (meaningful relationships), ~500 (acquaintances), ~1,500 (faces you can put names to). Each layer scales by roughly a factor of 3, and emotional closeness decreases with each expansion. The innermost circles require the most cognitive investment per relationship; the outermost require the least.
+
+This has direct implications for community formation and organizational design. Communities that grow beyond ~150 without introducing formal coordination mechanisms lose the trust-based cohesion that held them together. This is why [[trust is the binding constraint on network size and therefore on the complexity of products an economy can produce]] — trust operates naturally within Dunbar-scale groups but requires institutional scaffolding beyond them. It also explains why [[isolated populations lose cultural complexity because collective brains require minimum network size to sustain accumulated knowledge]] — the Tasmanian population of ~4,000 had enough Dunbar-scale groups for some cultural retention but insufficient interconnection between groups for full knowledge maintenance.
+
+For collective intelligence systems, Dunbar's number defines the scale at which informal coordination breaks down and formal mechanisms become necessary. The transition from trust-based to institution-based coordination is not a failure — it is the threshold where design must replace emergence.
+
+**Scope:** This claim is about cognitive constraints on individual social tracking, not about the optimal size for all social groups. Task-oriented teams, online communities, and algorithmically-mediated networks operate under different constraints. Dunbar's number bounds natural human social cognition, not designed coordination.
+
+---
+
+Relevant Notes:
+- [[trust is the binding constraint on network size and therefore on the complexity of products an economy can produce]] — trust is the coordination substrate that Dunbar's number constrains at the individual level
+- [[isolated populations lose cultural complexity because collective brains require minimum network size to sustain accumulated knowledge]] — network size must exceed Dunbar-scale for cultural accumulation, but interconnection between Dunbar-scale groups is what maintains it
+- [[collective brains generate innovation through population size and interconnectedness not individual genius]] — innovation requires networks larger than Dunbar's number, which is why institutional coordination is a prerequisite for complex civilization
+- [[Ostrom proved communities self-govern shared resources when eight design principles are met without requiring state control or privatization]] — Ostrom's design principles are the institutional mechanisms that extend coordination beyond Dunbar-scale groups
+- [[civilization was built on the false assumption that humans are rational individuals]] — Dunbar's number is another cognitive limitation that the rationality fiction obscures
+- [[humans are the minimum viable intelligence for cultural evolution not the pinnacle of cognition]] — the 150-person cap is evidence of minimal cognitive sufficiency, not optimal design
+
+Topics:
+- [[memetics and cultural evolution]]
+- [[cultural-dynamics/_map]]

foundations/cultural-dynamics/identity-protective cognition causes people to reject evidence that threatens their group identity even when they have the cognitive capacity to evaluate it correctly.md

@@ -0,0 +1,40 @@
+---
+type: claim
+domain: cultural-dynamics
+description: "Kahan's identity-protective cognition thesis: individuals with higher scientific literacy are MORE polarized on culturally contested issues, not less, because they use their cognitive skills to defend identity-consistent positions rather than to converge on truth"
+confidence: likely
+source: "Kahan 2012 Nature Climate Change; Kahan 2017 Advances in Political Psychology; Kahan et al. 2013 Journal of Risk Research"
+created: 2026-03-08
+---
+
+# identity-protective cognition causes people to reject evidence that threatens their group identity even when they have the cognitive capacity to evaluate it correctly
+
+Dan Kahan's cultural cognition research produces one of social science's most disturbing findings: on culturally contested issues (climate change, gun control, nuclear power), individuals with higher scientific literacy and numeracy are *more* polarized, not less. People who score highest on cognitive reflection tests — those best equipped to evaluate evidence — show the largest gaps in risk perception between cultural groups. More information, more analytical capacity, and more education do not produce convergence. They produce more sophisticated defense of the position their identity demands.
+
+The mechanism is identity-protective cognition. When a factual claim is entangled with group identity — when "believing X" signals membership in a cultural group — the individual faces a conflict between epistemic accuracy and social belonging. Since the individual cost of holding an inaccurate belief about climate change is negligible (one person's belief changes nothing about the climate), while the cost of deviating from group identity is immediate and tangible (social ostracism, loss of status, identity threat), the rational individual strategy is to protect identity. Higher cognitive capacity simply provides better tools for motivated reasoning — more sophisticated arguments for the predetermined conclusion.
+
+Kahan's empirical work demonstrates this across multiple domains. In one study, participants who correctly solved a complex statistical problem about skin cream treatment effectiveness failed to solve an *identical* problem when the data was reframed as gun control evidence — but only when the correct answer contradicted their cultural group's position. The analytical capacity was identical. The identity stakes changed the outcome.
+
+This is the empirical mechanism behind [[the self is a memeplex that persists because memes attached to a personal identity get copied more reliably than free-floating ideas]]. The selfplex is the theoretical framework; identity-protective cognition is the measured behavior. When beliefs become load-bearing components of the selfplex, they are defended with whatever cognitive resources are available. Smarter people defend them more skillfully.
+
+The implications for knowledge systems and collective intelligence are severe. Presenting evidence does not change identity-integrated beliefs — it can *strengthen* them through the backfire effect (challenged beliefs become more firmly held as the threat triggers defensive processing). This means [[ideological adoption is a complex contagion requiring multiple reinforcing exposures from trusted sources not simple viral spread through weak ties]] operates not just at the social level but at the cognitive level: the "trusted sources" must be trusted by the target's identity group, or the evidence is processed as identity threat rather than information.
+
+**What works instead:** Kahan's research suggests two approaches that circumvent identity-protective cognition. First, **identity-affirmation**: when individuals are affirmed in their identity before encountering threatening evidence, they process the evidence more accurately — the identity threat is preemptively neutralized. Second, **disentangling facts from identity**: presenting evidence in ways that do not signal group affiliation reduces identity-protective processing. The messenger matters more than the message: the same data presented by an in-group source is processed as information, while the same data from an out-group source is processed as attack.
+
+**Scope:** This claim is about factual beliefs on culturally contested issues, not about values or preferences. Identity-protective cognition does not explain all disagreement — genuine value differences exist that are not reducible to motivated reasoning. The claim is that on empirical questions where evidence should produce convergence, group identity prevents it.
+
+---
+
+Relevant Notes:
+- [[the self is a memeplex that persists because memes attached to a personal identity get copied more reliably than free-floating ideas]] — the selfplex is the theoretical framework; identity-protective cognition is the measured behavior
+- [[memeplexes survive by combining mutually reinforcing memes that protect each other from external challenge through untestability threats and identity attachment]] — identity attachment is the specific trick that identity-protective cognition exploits at the individual level
+- [[civilization was built on the false assumption that humans are rational individuals]] — identity-protective cognition is perhaps the strongest evidence against the rationality assumption: even the most capable reasoners are identity-protective first
+- [[ideological adoption is a complex contagion requiring multiple reinforcing exposures from trusted sources not simple viral spread through weak ties]] — the "trusted sources" requirement is partly explained by identity-protective cognition: sources must be identity-compatible
+- [[collective intelligence within a purpose-driven community faces a structural tension because shared worldview correlates errors while shared purpose enables coordination]] — identity-protective cognition is the mechanism by which shared worldview correlates errors: community members protect community-consistent beliefs
+- [[some disagreements are permanently irreducible because they stem from genuine value differences not information gaps and systems must map rather than eliminate them]] — identity-protective cognition creates *artificially* irreducible disagreements on empirical questions by entangling facts with identity
+- [[metaphor reframing is more powerful than argument because it changes which conclusions feel natural without requiring persuasion]] — reframing works because it circumvents identity-protective cognition by presenting the same conclusion through a different identity lens
+- [[validation-synthesis-pushback is a conversational design pattern where affirming then deepening then challenging creates the experience of being understood]] — the validation step pre-empts identity threat, enabling more accurate processing of the subsequent challenge
+
+Topics:
+- [[memetics and cultural evolution]]
+- [[cultural-dynamics/_map]]

foundations/cultural-dynamics/social capital erodes when associational life declines because trust generalized reciprocity and civic norms are produced by repeated face-to-face interaction in voluntary organizations not by individual virtue.md

@@ -0,0 +1,37 @@
+---
+type: claim
+domain: cultural-dynamics
+description: "Putnam's social capital thesis: the decline of bowling leagues, PTAs, fraternal organizations, and civic associations in the US since the 1960s depleted the trust infrastructure that enables collective action — caused primarily by generational change, television, suburban sprawl, and time pressure"
+confidence: likely
+source: "Putnam 2000 Bowling Alone; Fukuyama 1995 Trust; Henrich 2016 The Secret of Our Success"
+created: 2026-03-08
+---
+
+# social capital erodes when associational life declines because trust generalized reciprocity and civic norms are produced by repeated face-to-face interaction in voluntary organizations not by individual virtue
+
+Robert Putnam's *Bowling Alone* (2000) documented the decline of American civic engagement across multiple dimensions: PTA membership down 40% since 1960, fraternal organization membership halved, league bowling collapsed while individual bowling rose, church attendance declined, dinner party hosting dropped, union membership fell from 33% to 14% of the workforce. The data spans dozens of indicators across decades, making it one of the most comprehensive empirical accounts of social change in American sociology.
+
+The mechanism Putnam identifies is generative, not merely correlational. Voluntary associations — bowling leagues, Rotary clubs, church groups, PTAs — produce social capital as a byproduct of repeated interaction. When people meet regularly for shared activities, they develop generalized trust (willingness to trust strangers based on community norms), reciprocity norms (the expectation that favors will be returned, not by the individual but by the community), and civic skills (the practical ability to organize, deliberate, and coordinate). These are public goods: they benefit the entire community, not just participants.
+
+Social capital comes in two forms that map directly to network structure. **Bonding** social capital strengthens ties within homogeneous groups (ethnic communities, religious congregations, close-knit neighborhoods) — these are the strong ties that enable complex contagion and mutual aid. **Bridging** social capital connects across groups (civic organizations that bring together people of different backgrounds) — these are the weak ties that [[weak ties bridge otherwise disconnected clusters enabling information flow and opportunity access that strong ties within clusters cannot provide]]. A healthy civic ecosystem needs both: bonding for support and identity, bridging for information flow and broad coordination.
+
+Putnam identifies four primary causes of decline: (1) **Generational replacement** — the civic generation (born 1910-1940) who joined everything is being replaced by boomers and Gen X who join less, accounting for roughly half the decline. (2) **Television** — each additional hour of TV watching correlates with reduced civic participation, accounting for roughly 25% of the decline. (3) **Suburban sprawl** — commuting time directly substitutes for civic time; each 10 minutes of commuting reduces all forms of social engagement. (4) **Time and money pressures** — dual-income families have less discretionary time for voluntary associations.
+
+The implication is that social capital is *infrastructure*, not character. It is produced by specific social structures (voluntary associations with regular face-to-face interaction) and depleted when those structures erode. This connects to [[trust is the binding constraint on network size and therefore on the complexity of products an economy can produce]] — Putnam's social capital is the micro-mechanism by which trust is produced and sustained at the community level. When associational life declines, trust declines, and the capacity for collective action degrades.
+
+**Scope:** This claim is about the mechanism by which social capital is produced and depleted, not about whether the internet has offset Putnam's decline. Online communities may generate bonding social capital within interest groups, but their capacity to generate bridging social capital and generalized trust remains empirically contested. The claim is structural: repeated face-to-face interaction in voluntary organizations produces trust as a public good. Whether digital interaction can substitute remains an open question.
+
+---
+
+Relevant Notes:
+- [[trust is the binding constraint on network size and therefore on the complexity of products an economy can produce]] — Putnam's social capital is the micro-mechanism that produces the trust Hidalgo identifies as the binding constraint on economic complexity
+- [[weak ties bridge otherwise disconnected clusters enabling information flow and opportunity access that strong ties within clusters cannot provide]] — bridging social capital IS the Granovetter weak-tie mechanism applied to civic life
+- [[human social cognition caps meaningful relationships at approximately 150 because neocortex size constrains the number of individuals whose behavior and relationships can be tracked]] — voluntary associations work within Dunbar-scale groups, creating the repeated interaction needed for trust formation
+- [[ideological adoption is a complex contagion requiring multiple reinforcing exposures from trusted sources not simple viral spread through weak ties]] — bonding social capital provides the clustered strong-tie exposure that complex contagion requires
+- [[technology creates interconnection but not shared meaning which is the precise gap that produces civilizational coordination failure]] — Putnam's decline is the social infrastructure version of Ansary's meaning gap: connectivity without trust-producing institutions
+- [[coordination failures arise from individually rational strategies that produce collectively irrational outcomes because the Nash equilibrium of non-cooperation dominates when trust and enforcement are absent]] — social capital is the informal enforcement mechanism that shifts Nash equilibria toward cooperation without formal institutions
+- [[modernization dismantles family and community structures replacing them with market and state relationships that increase individual freedom but erode psychosocial foundations of wellbeing]] — Putnam's decline is the American instance of the broader modernization-driven erosion of community structures
+
+Topics:
+- [[memetics and cultural evolution]]
+- [[cultural-dynamics/_map]]

foundations/cultural-dynamics/the self is a memeplex that persists because memes attached to a personal identity get copied more reliably than free-floating ideas.md

@@ -0,0 +1,34 @@
+---
+type: claim
+domain: cultural-dynamics
+description: "Blackmore's selfplex: personal identity is a cluster of mutually reinforcing memes (beliefs, values, narratives, preferences) organized around a central 'I' that provides a replication advantage — memes attached to identity spread through self-expression and resist displacement through identity-protective mechanisms"
+confidence: experimental
+source: "Blackmore 1999 The Meme Machine; Dennett 1991 Consciousness Explained; Henrich 2016 The Secret of Our Success"
+created: 2026-03-08
+---
+
+# the self is a memeplex that persists because memes attached to a personal identity get copied more reliably than free-floating ideas
+
+Susan Blackmore's concept of the "selfplex" is the application of memetic theory to personal identity. The self — "I" — is not a biological given but a memeplex: a cluster of mutually reinforcing memes (beliefs, values, preferences, narratives, group affiliations) organized around a central fiction of a unified agent. The selfplex persists because memes attached to it gain a replication advantage: a belief that is "part of who I am" gets expressed more frequently, defended more vigorously, and transmitted more reliably than a belief held lightly.
+
+The mechanism works through three channels. First, **expression frequency**: people talk about what they identify with. A person who identifies as an environmentalist mentions environmental issues more often than someone who merely agrees that pollution is bad. The identity-attached meme gets more transmission opportunities. Second, **defensive vigor**: when a meme is part of the selfplex, challenges to it feel like challenges to the self. This triggers emotional defense responses that protect the meme from displacement — the same [[memeplexes survive by combining mutually reinforcing memes that protect each other from external challenge through untestability threats and identity attachment]] mechanism, but applied to the personal identity rather than a collective ideology. Third, **social signaling**: expressing identity-consistent beliefs signals group membership, which activates reciprocal transmission from fellow group members.
+
+Blackmore builds on Dennett's "center of narrative gravity" — the self is a story we tell about ourselves, not a thing we discover. But she adds the evolutionary dimension: the selfplex is not just a narrative convenience. It is a replicator strategy. Memes that successfully attach to the selfplex gain protection, expression, and transmission advantages that free-floating memes do not. The self is the ultimate host environment for memes.
+
+This has direct implications for belief updating. When evidence contradicts a belief that is integrated into the selfplex, the rational response (update the belief) conflicts with the memetic response (protect the selfplex). The selfplex wins more often than not because the emotional cost of identity threat exceeds the cognitive benefit of accuracy. This explains why [[civilization was built on the false assumption that humans are rational individuals]] — rationality assumes beliefs are held for epistemic reasons, but selfplex theory shows they are held for identity reasons, with epistemic justification constructed post-hoc.
+
+**Scope and confidence.** Rated experimental because the selfplex is a theoretical construct, not an empirically isolated mechanism. The component observations are well-established (identity-consistent beliefs are expressed and defended more vigorously, belief change is harder for identity-integrated beliefs). But whether "selfplex" as a coherent replicator unit adds explanatory power beyond these individual effects is debated. The strongest version of the claim — that the self is *literally* a memeplex with its own replication dynamics — is a theoretical framework, not an empirical finding.
+
+---
+
+Relevant Notes:
+- [[memeplexes survive by combining mutually reinforcing memes that protect each other from external challenge through untestability threats and identity attachment]] — the selfplex IS the identity attachment trick applied to the individual rather than the collective
+- [[civilization was built on the false assumption that humans are rational individuals]] — the selfplex explains WHY the rationality assumption fails: beliefs serve identity before truth
+- [[meme propagation selects for simplicity novelty and conformity pressure rather than truth or utility]] — selfplex attachment is a fourth selection pressure: memes that attach to identity replicate regardless of simplicity, novelty, or conformity
+- [[the strongest memeplexes align individual incentive with collective behavior creating self-validating feedback loops]] — the selfplex is the individual-level version: self-expression validates self-identity in a feedback loop
+- [[true imitation is the threshold capacity that creates a second replicator because only faithful copying of behaviors enables cumulative cultural evolution]] — the selfplex is a higher-order organization of the second replicator, organizing memes into identity-coherent clusters
+- [[collective intelligence within a purpose-driven community faces a structural tension because shared worldview correlates errors while shared purpose enables coordination]] — shared selfplex structures within a community correlate errors through identity-protective cognition
+
+Topics:
+- [[memetics and cultural evolution]]
+- [[cultural-dynamics/_map]]

foundations/cultural-dynamics/weak ties bridge otherwise disconnected clusters enabling information flow and opportunity access that strong ties within clusters cannot provide.md

@@ -0,0 +1,34 @@
+---
+type: claim
+domain: cultural-dynamics
+description: "Granovetter's strength of weak ties shows that acquaintances bridge structural holes between dense clusters, providing access to non-redundant information — but this applies to simple contagion (information), not complex contagion (behavioral/ideological change)"
+confidence: proven
+source: "Granovetter 1973 American Journal of Sociology; Burt 2004 structural holes; Centola 2010 Science (boundary condition)"
+created: 2026-03-08
+---
+
+# weak ties bridge otherwise disconnected clusters enabling information flow and opportunity access that strong ties within clusters cannot provide
+
+Mark Granovetter's 1973 paper "The Strength of Weak Ties" established one of network science's most counterintuitive and empirically robust findings: acquaintances (weak ties) are more valuable than close friends (strong ties) for accessing novel information and opportunities. The mechanism is structural, not relational. Strong ties cluster — your close friends tend to know each other and share the same information. Weak ties bridge — your acquaintances connect you to entirely different social clusters with non-redundant information.
+
+The original evidence came from job-seeking: Granovetter found that 84% of respondents who found jobs through personal contacts used weak ties rather than strong ones. The information that led to employment came from people they saw "occasionally" or "rarely," not from close friends. This is because close friends circulate in the same information environment — they know what you already know. Acquaintances have access to different information pools entirely.
+
+Ronald Burt extended this into "structural holes" theory: the most valuable network positions are those that bridge gaps between otherwise disconnected clusters. Individuals who span structural holes have access to diverse, non-redundant information and can broker between groups. This creates information advantages, earlier access to opportunities, and disproportionate influence — not because of personal ability but because of network position.
+
+**The critical boundary condition.** Granovetter's thesis holds for *information* flow — simple contagion where a single exposure is sufficient for transmission. But [[ideological adoption is a complex contagion requiring multiple reinforcing exposures from trusted sources not simple viral spread through weak ties]]. Centola's research demonstrates that for behavioral and ideological change, weak ties are actually *counterproductive*: a signal arriving via a weak tie comes without social reinforcement. Complex contagion requires the redundant, trust-rich exposure that strong ties and clustered networks provide. This creates a fundamental design tension: the same network structure that maximizes information flow (bridging weak ties) minimizes ideological adoption (which needs clustered strong ties).
+
+For any system that must both spread information widely and drive deep behavioral change, the implication is a two-phase architecture: weak ties for awareness and information discovery, strong ties for adoption and commitment. Broadcasting reaches everyone; community converts the committed.
+
+---
+
+Relevant Notes:
+- [[ideological adoption is a complex contagion requiring multiple reinforcing exposures from trusted sources not simple viral spread through weak ties]] — the boundary condition that limits weak tie effectiveness to simple contagion
+- [[complex ideas propagate with higher fidelity through personal interaction than mass media because nuance requires bidirectional communication]] — strong ties enable the bidirectional communication that nuanced ideas require
+- [[trust is the binding constraint on network size and therefore on the complexity of products an economy can produce]] — trust operates through strong ties within clusters; weak ties enable information flow between clusters but do not carry trust
+- [[collective brains generate innovation through population size and interconnectedness not individual genius]] — weak ties provide the interconnectedness that makes collective brains work by connecting otherwise siloed knowledge pools
+- [[partial connectivity produces better collective intelligence than full connectivity on complex problems because it preserves diversity]] — partial connectivity preserves the cluster structure that weak ties bridge, maintaining both diversity and connection
+- [[cross-domain knowledge connections generate disproportionate value because most insights are siloed]] — cross-domain connections are the intellectual equivalent of weak ties bridging structural holes
+
+Topics:
+- [[memetics and cultural evolution]]
+- [[cultural-dynamics/_map]]

foundations/teleological-economics/auction theory reveals that allocation mechanism design determines price discovery efficiency and revenue because different auction formats produce different outcomes depending on bidder information structure and risk preferences.md

@@ -0,0 +1,58 @@
+---
+type: claim
+domain: teleological-economics
+description: "Vickrey's foundational insight that auction format determines economic outcomes — not just 'who pays the most' but how information is revealed, how risk is distributed, and whether allocation is efficient — underpins token launch design, spectrum allocation, and any market where goods are allocated through competitive bidding"
+confidence: proven
+source: "Vickrey (1961); Milgrom & Weber (1982); Myerson (1981); Riley & Samuelson (1981); Nobel Prize in Economics 1996 (Vickrey), 2020 (Milgrom & Wilson)"
+created: 2026-03-08
+---
+
+# Auction theory reveals that allocation mechanism design determines price discovery efficiency and revenue because different auction formats produce different outcomes depending on bidder information structure and risk preferences
+
+William Vickrey (1961) established that auctions are not interchangeable — the format determines economic outcomes. This insight, seemingly obvious in retrospect, overturned the assumption that "let people bid" is sufficient for efficient allocation. The mechanism matters.
+
+## Revenue equivalence — and its failures
+
+The Revenue Equivalence Theorem (Vickrey 1961, Myerson 1981, Riley & Samuelson 1981) proves that under specific conditions — risk-neutral bidders, independent private values, symmetric information — all standard auction formats (English, Dutch, first-price sealed, second-price sealed) yield the same expected revenue. This is the baseline result.
+
+The power of the theorem lies in what happens when its assumptions fail:
+
+**Risk-averse bidders** break equivalence. First-price auctions generate more revenue than second-price auctions because risk-averse bidders shade their bids less — they'd rather overpay slightly than risk losing. This is why most real-world procurement uses first-price formats.
+
+**Correlated values** break equivalence. Milgrom and Weber (1982) proved the Linkage Principle: when bidder values are correlated (common-value auctions), formats that reveal more information during bidding generate higher revenue because they reduce the winner's curse. English auctions outperform sealed-bid auctions in common-value settings because the bidding process itself reveals information.
+
+**Asymmetric information** breaks equivalence. When some bidders have better information than others, format choice determines whether informed bidders extract rents or whether the mechanism levels the playing field.
+
+## The winner's curse
+
+In common-value auctions (where the item has a single true value that bidders estimate with noise), the winner is the bidder with the most optimistic estimate — and therefore the most likely to have overpaid. Rational bidders shade their bids to account for this, but the degree of shading depends on the auction format. The winner's curse is why IPOs are systematically underpriced (Rock 1986) and why token launches that ignore information asymmetry between insiders and outsiders produce adverse selection.
+
+## Why this is foundational
+
+Auction theory provides the formal toolkit for:
+
+- **Token launch design:** [[token launches are hybrid-value auctions where common-value price discovery and private-value community alignment require different mechanisms because auction theory optimized for one degrades the other]] — the hybrid-value problem is precisely the failure of revenue equivalence when you have both common-value (price discovery) and private-value (community alignment) components in the same allocation.
+
+- **Dutch-auction mechanisms:** [[dutch-auction dynamic bonding curves solve the token launch pricing problem by combining descending price discovery with ascending supply curves eliminating the instantaneous arbitrage that has cost token deployers over 100 million dollars on Ethereum]] — the descending-price mechanism is a specific auction format choice designed to solve the information asymmetry that creates MEV extraction.
+
+- **Layered architecture:** [[optimal token launch architecture is layered not monolithic because separating quality governance from price discovery from liquidity bootstrapping from community rewards lets each layer use the mechanism best suited to its objective]] — the insight that different allocation problems within a single launch need different auction formats.
+
+- **Mechanism design:** [[mechanism design enables incentive-compatible coordination by constructing rules under which self-interested agents voluntarily reveal private information and take socially optimal actions]] — auction theory is mechanism design's most successful application domain. Vickrey auctions are the canonical example of incentive-compatible mechanisms.
+
+- **Prediction markets:** [[speculative markets aggregate information through incentive and selection effects not wisdom of crowds]] — continuous double auctions in prediction markets aggregate information because the market mechanism rewards accurate pricing, a direct application of the Linkage Principle.
+
+Without auction theory, claims about token launch design and price discovery mechanisms lack the formal framework for evaluating why one format outperforms another. "Run an auction" is not a design — the format, information structure, and participation rules determine everything.
+
+---
+
+Relevant Notes:
+- [[token launches are hybrid-value auctions where common-value price discovery and private-value community alignment require different mechanisms because auction theory optimized for one degrades the other]] — the central application of auction theory to internet finance
+- [[dutch-auction dynamic bonding curves solve the token launch pricing problem by combining descending price discovery with ascending supply curves eliminating the instantaneous arbitrage that has cost token deployers over 100 million dollars on Ethereum]] — a specific auction format choice
+- [[optimal token launch architecture is layered not monolithic because separating quality governance from price discovery from liquidity bootstrapping from community rewards lets each layer use the mechanism best suited to its objective]] — why different auction formats suit different launch stages
+- [[mechanism design enables incentive-compatible coordination by constructing rules under which self-interested agents voluntarily reveal private information and take socially optimal actions]] — auction theory as mechanism design's most successful subdomain
+- [[speculative markets aggregate information through incentive and selection effects not wisdom of crowds]] — prediction market pricing as continuous auction
+- [[early-conviction pricing is an unsolved mechanism design problem because systems that reward early believers attract extractive speculators while systems that prevent speculation penalize genuine supporters]] — the unsolved auction design problem
+
+Topics:
+- [[analytical-toolkit]]
+- [[internet finance and decision markets]]

foundations/teleological-economics/platform economics creates winner-take-most markets through cross-side network effects where the platform that reaches critical mass on any side locks in the entire ecosystem because multi-sided markets tip faster than single-sided ones.md

@@ -0,0 +1,62 @@
+---
+type: claim
+domain: teleological-economics
+description: "Platforms are not just big companies — they are fundamentally different economic structures that create and capture value through cross-side network effects, and understanding their economics is critical because half the claims in the codex reference platform dynamics without a foundational claim explaining why platforms behave the way they do"
+confidence: proven
+source: "Rochet & Tirole, 'Platform Competition in Two-Sided Markets' (2003); Parker, Van Alstyne & Choudary, 'Platform Revolution' (2016); Eisenmann, Parker & Van Alstyne (2006); Evans & Schmalensee, 'Matchmakers' (2016); Nobel Prize in Economics 2014 (Tirole)"
+created: 2026-03-08
+---
+
+# Platform economics creates winner-take-most markets through cross-side network effects where the platform that reaches critical mass on any side locks in the entire ecosystem because multi-sided markets tip faster than single-sided ones
+
+Rochet and Tirole (2003) formalized what practitioners had intuited: two-sided markets have fundamentally different economics from traditional markets. A platform serves two or more distinct user groups whose participation creates value for each other. The platform's primary economic function is not production but matching — reducing the transaction cost of finding, evaluating, and transacting with the other side.
+
+## Cross-side network effects
+
+The defining feature of platform economics is cross-side network effects: users on one side of the platform attract users on the other side. More app developers attract phone buyers; more phone buyers attract app developers. More drivers attract riders; more riders attract drivers. This creates a self-reinforcing feedback loop that is stronger than same-side network effects because it operates across TWO growth curves simultaneously.
+
+Cross-side effects produce three dynamics that traditional economics doesn't predict:
+
+**1. Pricing below cost on one side.** Platforms rationally price below marginal cost (or even at zero) on the side whose participation creates more value for the other side. Google gives away search to attract users to attract advertisers. This is not predatory pricing — it is the profit-maximizing strategy in a multi-sided market. The subsidy side generates demand that the monetization side pays for.
+
+**2. Chicken-and-egg problem.** Both sides need the other to join first. Platforms solve this through sequencing strategies: subsidize the harder side, seed supply artificially, or find a single-sided use case that doesn't require the other side. [[early-conviction pricing is an unsolved mechanism design problem because systems that reward early believers attract extractive speculators while systems that prevent speculation penalize genuine supporters]] — the early-conviction problem is a specific instance of the chicken-and-egg problem applied to token launches.
+
+**3. Multi-homing costs determine lock-in.** When users can participate on multiple platforms simultaneously (multi-homing), winner-take-most dynamics weaken. When multi-homing is costly (because of data lock-in, reputation systems, or switching costs), tipping accelerates. DeFi protocols with composable liquidity reduce multi-homing costs; walled-garden platforms increase them.
+
+## Platform envelopment
+
+Eisenmann, Parker, and Van Alstyne (2006) identified platform envelopment: a platform in an adjacent market leverages its user base to enter and dominate a new market. Microsoft used the Windows installed base to envelope browsers. Google used search to envelope email, maps, and video. Amazon used e-commerce to envelope cloud computing.
+
+Envelopment works because the entering platform already solved the chicken-and-egg problem on one side. It imports its existing user base as a beachhead and only needs to attract the new side. This is why platform competition is not about building a better product — it's about controlling the user relationship that enables cross-side leverage.
+
+This dynamic directly threatens any protocol or platform that relies on a single market position. [[when profits disappear at one layer of a value chain they emerge at an adjacent layer through the conservation of attractive profits]] — platform envelopment is the mechanism through which profits migrate: the enveloping platform captures the adjacent layer's attractive profits.
+
+## Why this is foundational
+
+Platform economics provides the theoretical grounding for:
+
+- **Token launch platforms:** MetaDAO as a launch platform faces classic two-sided market dynamics — it needs both token deployers and traders/governance participants. [[agents create dozens of proposals but only those attracting minimum stake become live futarchic decisions creating a permissionless attention market for capital formation]] — the permissionless proposal market is a platform matching capital allocators with investment opportunities.
+
+- **Network effects:** [[network effects create winner-take-most markets because each additional user increases value for all existing users producing positive feedback that concentrates market share among early leaders]] — platform economics extends this from single-sided to cross-side effects, which are stronger and tip faster.
+
+- **Media disruption:** [[two-phase disruption where distribution moats fall first and creation moats fall second is a universal pattern across entertainment knowledge work and financial services]] — platforms are the mechanism through which distribution moats fall, because platforms reduce the transaction cost of matching creators to audiences below what incumbent distribution achieves.
+
+- **Why intermediaries accumulate rent:** [[transaction costs determine organizational boundaries because firms exist to economize on the costs of using markets and the boundary shifts when technology changes the relative cost of internal coordination versus external contracting]] — platforms are transaction cost innovations that create new governance structures with their own rent-extraction potential.
+
+- **Vertical integration dynamics:** [[purpose-built full-stack systems outcompete acquisition-based incumbents during structural transitions because integrated design eliminates the misalignment that bolted-on components create]] — vertical integration vs platform strategy is the central architectural choice, and transaction cost economics determines which wins.
+
+---
+
+Relevant Notes:
+- [[network effects create winner-take-most markets because each additional user increases value for all existing users producing positive feedback that concentrates market share among early leaders]] — platform economics extends network effects from single-sided to cross-side
+- [[when profits disappear at one layer of a value chain they emerge at an adjacent layer through the conservation of attractive profits]] — platform envelopment as profit migration mechanism
+- [[early-conviction pricing is an unsolved mechanism design problem because systems that reward early believers attract extractive speculators while systems that prevent speculation penalize genuine supporters]] — chicken-and-egg problem applied to token launches
+- [[agents create dozens of proposals but only those attracting minimum stake become live futarchic decisions creating a permissionless attention market for capital formation]] — MetaDAO as two-sided platform
+- [[two-phase disruption where distribution moats fall first and creation moats fall second is a universal pattern across entertainment knowledge work and financial services]] — platforms as distribution-moat destroyers
+- [[transaction costs determine organizational boundaries because firms exist to economize on the costs of using markets and the boundary shifts when technology changes the relative cost of internal coordination versus external contracting]] — platforms as transaction cost governance structures
+- [[purpose-built full-stack systems outcompete acquisition-based incumbents during structural transitions because integrated design eliminates the misalignment that bolted-on components create]] — vertical integration vs platform as architectural choice
+- [[good management causes disruption because rational resource allocation systematically favors sustaining innovation over disruptive opportunities]] — platforms disrupt because incumbents rationally optimize existing business models instead of building platform alternatives
+
+Topics:
+- [[analytical-toolkit]]
+- [[attractor dynamics]]

foundations/teleological-economics/transaction costs determine organizational boundaries because firms exist to economize on the costs of using markets and the boundary shifts when technology changes the relative cost of internal coordination versus external contracting.md

@@ -0,0 +1,67 @@
+---
+type: claim
+domain: teleological-economics
+description: "Coase and Williamson's insight that firms are not production functions but governance structures — they exist because market transactions have costs, and the boundary between firm and market shifts when technology changes those costs — is the theoretical foundation for understanding platform economics, vertical integration, and why intermediaries rise and fall"
+confidence: proven
+source: "Coase, 'The Nature of the Firm' (1937); Williamson, 'Markets and Hierarchies' (1975), 'The Economic Institutions of Capitalism' (1985); Nobel Prize in Economics 1991 (Coase), 2009 (Williamson)"
+created: 2026-03-08
+---
+
+# Transaction costs determine organizational boundaries because firms exist to economize on the costs of using markets and the boundary shifts when technology changes the relative cost of internal coordination versus external contracting
+
+Ronald Coase (1937) asked the question economics had ignored: if markets are efficient allocators, why do firms exist? His answer: because using markets has costs. Finding trading partners, negotiating terms, writing contracts, monitoring performance, enforcing agreements — these transaction costs explain why some activities happen inside firms (hierarchy) rather than between firms (market). The boundary of the firm is where the marginal cost of internal coordination equals the marginal cost of market transaction.
+
+## Williamson's three dimensions
+
+Oliver Williamson (1975, 1985) operationalized Coase by identifying three dimensions that determine whether transactions are governed by markets, hybrids, or hierarchies:
+
+**Asset specificity:** When an investment is tailored to a specific transaction partner (specialized equipment, dedicated training, site-specific infrastructure), the investing party becomes vulnerable to hold-up — the partner can renegotiate terms after the investment is sunk. High asset specificity pushes governance toward hierarchy (vertical integration) because internal governance protects against hold-up.
+
+**Uncertainty:** When outcomes are unpredictable and contracts cannot specify all contingencies, market governance fails because incomplete contracts create disputes. Hierarchy handles uncertainty through authority — a manager can adapt in real-time without renegotiating contracts. This is why complex, novel activities tend to happen inside firms rather than through market contracts.
+
+**Frequency:** Transactions that recur frequently justify the fixed costs of specialized governance structures. A one-time purchase goes to market; a daily supply relationship justifies a long-term contract or vertical integration.
+
+## Why intermediaries rise and fall
+
+Transaction cost economics explains the lifecycle of intermediaries:
+
+1. **Intermediaries arise** when they reduce transaction costs below what direct trading achieves. Brokers aggregate information, market makers provide liquidity, platforms match counterparties. Each exists because the transaction cost of direct exchange exceeds the intermediary's fee.
+
+2. **Intermediaries accumulate rent** when they become the lowest-cost governance structure AND create switching costs. The intermediary's margin is bounded by the transaction cost of the next-best alternative. When no alternative is cheaper, the intermediary extracts rent.
+
+3. **Intermediaries fall** when technology reduces the transaction costs they were built to economize. If blockchain reduces the cost of trustless exchange below the intermediary's fee, the intermediary's governance advantage disappears. This is not disruption through better products — it's disruption through lower transaction costs making the intermediary's existence uneconomical.
+
+This framework directly explains why [[internet finance generates 50 to 100 basis points of additional annual GDP growth by unlocking capital allocation to previously inaccessible assets and eliminating intermediation friction]] — the GDP impact comes from reducing transaction costs, not from creating new demand.
+
+## Platform economics as transaction cost innovation
+
+Platforms are transaction cost innovations. They reduce the cost of matching, pricing, and trust-building below what bilateral markets achieve. But platforms also create NEW transaction costs — switching costs, data lock-in, platform-specific investments (app development, audience building) that constitute asset specificity. The platform becomes the governance structure, and participants face the same hold-up problem that vertical integration was designed to solve.
+
+This is why [[network effects create winner-take-most markets because each additional user increases value for all existing users producing positive feedback that concentrates market share among early leaders]] — network effects are demand-side transaction cost reductions (more users = easier to find counterparties = lower search costs), but they also create asset specificity (users' social graphs, reputation, content are platform-specific investments).
+
+## Why this is foundational
+
+Transaction cost economics provides the theoretical lens for:
+
+- **Why intermediaries exist and when they die** — the core question for internet finance. Every intermediary is a transaction cost governance structure; technology that reduces those costs makes the intermediary obsolete.
+
+- **Why vertical integration happens** — Kaiser Permanente, SpaceX, and Apple all vertically integrate because asset specificity and uncertainty in their domains make market governance more expensive than hierarchy. [[when profits disappear at one layer of a value chain they emerge at an adjacent layer through the conservation of attractive profits]] — profit migration follows transaction cost shifts.
+
+- **Why platforms capture value** — platforms reduce transaction costs between sides of the market, but the platform itself becomes a governance structure with its own transaction costs (fees, rules, lock-in).
+
+- **Why DAOs struggle** — DAOs attempt to replace hierarchical governance with market/protocol governance, but many activities inside organizations have high asset specificity and uncertainty — exactly the conditions where Williamson predicts hierarchy outperforms markets.
+
+---
+
+Relevant Notes:
+- [[internet finance generates 50 to 100 basis points of additional annual GDP growth by unlocking capital allocation to previously inaccessible assets and eliminating intermediation friction]] — GDP impact as transaction cost reduction
+- [[network effects create winner-take-most markets because each additional user increases value for all existing users producing positive feedback that concentrates market share among early leaders]] — network effects as demand-side transaction cost reductions that create new asset specificity
+- [[when profits disappear at one layer of a value chain they emerge at an adjacent layer through the conservation of attractive profits]] — profit migration follows transaction cost shifts
+- [[value in industry transitions accrues to bottleneck positions in the emerging architecture not to pioneers or to the largest incumbents]] — bottleneck positions are where transaction costs are highest and governance is most valuable
+- [[the personbyte is a fundamental quantization limit on knowledge accumulation forcing all complex production into networked teams]] — the personbyte is a knowledge-specific transaction cost: transferring knowledge between minds has irreducible cost
+- [[trust is the binding constraint on network size and therefore on the complexity of products an economy can produce]] — trust reduces transaction costs; more trust enables larger networks and more complex production
+- [[industries are need-satisfaction systems and the attractor state is the configuration that most efficiently satisfies underlying human needs given available technology]] — the attractor state is the minimum-transaction-cost configuration
+
+Topics:
+- [[analytical-toolkit]]
+- [[internet finance and decision markets]]

inbox/archive/2026-02-24-karpathy-clis-legacy-tech-agents.md

@@ -0,0 +1,30 @@
+---
+type: source
+title: "CLIs are exciting because they're legacy technology — AI agents can natively use them, combine them, interact via terminal"
+author: "Andrej Karpathy (@karpathy)"
+twitter_id: "33836629"
+url: https://x.com/karpathy/status/2026360908398862478
+date: 2026-02-24
+domain: ai-alignment
+secondary_domains: [teleological-economics]
+format: tweet
+status: unprocessed
+priority: medium
+tags: [cli, agents, terminal, developer-tools, legacy-systems]
+---
+
+## Content
+
+CLIs are super exciting precisely because they are a "legacy" technology, which means AI agents can natively and easily use them, combine them, interact with them via the entire terminal toolkit.
+
+E.g ask your Claude/Codex agent to install this new Polymarket CLI and ask for any arbitrary dashboards or interfaces or logic. The agents will build it for you. Install the Github CLI too and you can ask them to navigate the repo, see issues, PRs, discussions, even the code itself.
+
+## Agent Notes
+
+**Why this matters:** 11.7K likes. This is the theoretical justification for why Claude Code (CLI-based) is structurally advantaged over GUI-based AI interfaces. Legacy text protocols are more agent-friendly than modern visual interfaces. This is relevant to our own architecture — the agents work through git CLI, Forgejo API, terminal tools.
+
+**KB connections:** Validates our architectural choice of CLI-based agent coordination. Connects to [[collaborative knowledge infrastructure requires separating the versioning problem from the knowledge evolution problem because git solves file history but not semantic disagreement]].
+
+**Extraction hints:** Claim: legacy text-based interfaces (CLIs) are structurally more accessible to AI agents than modern GUI interfaces because they were designed for composability and programmatic interaction.
+
+**Context:** Karpathy explicitly mentions Claude and Polymarket CLI — connecting AI agents with prediction markets through terminal tools. Relevant to the Teleo stack.

inbox/archive/2026-02-25-karpathy-programming-changed-december.md

@@ -0,0 +1,28 @@
+---
+type: source
+title: "Programming fundamentally changed in December 2025 — coding agents basically didn't work before and basically work since"
+author: "Andrej Karpathy (@karpathy)"
+twitter_id: "33836629"
+url: https://x.com/karpathy/status/2026731645169185220
+date: 2026-02-25
+domain: ai-alignment
+secondary_domains: [teleological-economics]
+format: tweet
+status: unprocessed
+priority: medium
+tags: [coding-agents, ai-capability, phase-transition, software-development, disruption]
+---
+
+## Content
+
+It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn't work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow.
+
+## Agent Notes
+
+**Why this matters:** 37K likes — Karpathy's most viral tweet in this dataset. This is the "phase transition" observation from the most authoritative voice in AI dev tooling. December 2025 as the inflection point for coding agents.
+
+**KB connections:** Supports [[as AI-automated software development becomes certain the bottleneck shifts from building capacity to knowing what to build]]. Relates to [[the gap between theoretical AI capability and observed deployment is massive across all occupations]] — but suggests the gap is closing fast for software specifically.
+
+**Extraction hints:** Claim candidate: coding agent capability crossed a usability threshold in December 2025, representing a phase transition not gradual improvement. Evidence: Karpathy's direct experience running agents on nanochat.
+
+**Context:** This tweet preceded the autoresearch project by ~10 days. The 37K likes suggest massive resonance across the developer community. The "asterisks" he mentions are important qualifiers that a good extraction should preserve.

inbox/archive/2026-02-27-karpathy-8-agent-research-org.md

@@ -0,0 +1,44 @@
+---
+type: source
+title: "8-agent research org experiments reveal agents generate bad ideas but execute well — the source code is now the org design"
+author: "Andrej Karpathy (@karpathy)"
+twitter_id: "33836629"
+url: https://x.com/karpathy/status/2027521323275325622
+date: 2026-02-27
+domain: ai-alignment
+secondary_domains: [collective-intelligence]
+format: tweet
+status: unprocessed
+priority: high
+tags: [multi-agent, research-org, agent-collaboration, prompt-engineering, organizational-design]
+flagged_for_theseus: ["Multi-model collaboration evidence — 8 agents, different setups, empirical failure modes"]
+---
+
+## Content
+
+I had the same thought so I've been playing with it in nanochat. E.g. here's 8 agents (4 claude, 4 codex), with 1 GPU each running nanochat experiments (trying to delete logit softcap without regression). The TLDR is that it doesn't work and it's a mess... but it's still very pretty to look at :)
+
+I tried a few setups: 8 independent solo researchers, 1 chief scientist giving work to 8 junior researchers, etc. Each research program is a git branch, each scientist forks it into a feature branch, git worktrees for isolation, simple files for comms, skip Docker/VMs for simplicity atm (I find that instructions are enough to prevent interference). Research org runs in tmux window grids of interactive sessions (like Teams) so that it's pretty to look at, see their individual work, and "take over" if needed, i.e. no -p.
+
+But ok the reason it doesn't work so far is that the agents' ideas are just pretty bad out of the box, even at highest intelligence. They don't think carefully though experiment design, they run a bit non-sensical variations, they don't create strong baselines and ablate things properly, they don't carefully control for runtime or flops. (just as an example, an agent yesterday "discovered" that increasing the hidden size of the network improves the validation loss, which is a totally spurious result given that a bigger network will have a lower validation loss in the infinite data regime, but then it also trains for a lot longer, it's not clear why I had to come in to point that out). They are very good at implementing any given well-scoped and described idea but they don't creatively generate them.
+
+But the goal is that you are now programming an organization (e.g. a "research org") and its individual agents, so the "source code" is the collection of prompts, skills, tools, etc. and processes that make it up. E.g. a daily standup in the morning is now part of the "org code". And optimizing nanochat pretraining is just one of the many tasks (almost like an eval). Then - given an arbitrary task, how quickly does your research org generate progress on it?
+
+## Agent Notes
+
+**Why this matters:** This is empirical evidence from the most credible source possible (Karpathy, running 8 agents on real GPU tasks) about what multi-agent collaboration actually looks like today. Key finding: agents execute well but generate bad ideas. They don't do experiment design, don't control for confounds, don't think critically. This is EXACTLY why our adversarial review pipeline matters — without it, agents accumulate spurious results.
+
+**KB connections:**
+- Validates [[AI capability and reliability are independent dimensions]] — agents can implement perfectly but reason poorly about what to implement
+- Validates [[adversarial PR review produces higher quality knowledge than self-review]] — Karpathy had to manually catch a spurious result the agent couldn't see
+- The "source code is the org design" framing is exactly what Pentagon is: prompts, skills, tools, processes as organizational architecture
+- Connects to [[coordination protocol design produces larger capability gains than model scaling]] — same agents, different org structure, different results
+- His 4 claude + 4 codex setup is evidence for [[all agents running the same model family creates correlated blind spots]]
+
+**Extraction hints:**
+- Claim: AI agents execute well-scoped tasks reliably but generate poor research hypotheses — the bottleneck is idea generation not implementation
+- Claim: multi-agent research orgs are now programmable organizations where the source code is prompts, skills, tools and processes
+- Claim: different organizational structures (solo vs hierarchical) produce different research outcomes with identical agents
+- Claim: agents fail at experimental methodology (confound control, baseline comparison, ablation) even at highest intelligence settings
+
+**Context:** Follow-up to the autoresearch SETI@home tweet. Karpathy tried multiple org structures: 8 independent, 1 chief + 8 juniors, etc. Used git worktrees for isolation (we use the same pattern in Pentagon). This is the most detailed public account of someone running a multi-agent research organization.

inbox/archive/2026-03-04-theiaresearch-permissionless-metadao-launches.md

@@ -0,0 +1,39 @@
+---
+type: source
+title: "Permissionless MetaDAO launches create new cultural primitives around fundraising"
+author: "Felipe Montealegre (@TheiaResearch)"
+twitter_id: "1511793131884318720"
+url: https://x.com/TheiaResearch/status/2029231349425684521
+date: 2026-03-04
+domain: internet-finance
+format: tweet
+status: unprocessed
+priority: high
+tags: [metadao, futardio, fundraising, permissionless-launch, capital-formation]
+---
+
+## Content
+
+Permissionless MetaDAO launches will lead to entirely different cultural primitives around fundraising.
+
+1. Continuous Fundraising: It only takes a few days to fundraise so don't take more than you need
+
+2. Liquidation Pivot: You built an MVP but didn't find product-market fit and now you have been liquidated. Try again on another product or strategy.
+
+3. Multiple Attempts: You didn't fill your minimum raise? Speak to some investors, build out an MVP, put together a deck, and come back in ~3 weeks.
+
+4. Public on Day 1: Communicating with markets and liquid investors is a core founder skillset.
+
+5. 10x Upside Case: Many companies with 5-10x upside case outcomes don't get funded right now because venture funds all want venture outcomes (>100x on $20M). What if you just want to build a $25M company with a decent probability of success? Raise $1M and the math works fine for Futardio investors.
+
+Futardio is a paradigm shift for capital markets. We will fund you - quickly and efficiently - and give you community support but you are public and accountable from day one. Welcome to the arena.
+
+## Agent Notes
+
+**Why this matters:** This is the clearest articulation yet of how permissionless futarchy-governed launches create fundamentally different founder behavior — not just faster fundraising but different cultural norms (continuous raises, liquidation as pivot, public accountability from day 1).
+
+**KB connections:** Directly extends [[internet capital markets compress fundraising from months to days]] and [[futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible]]. The "10x upside case" point challenges the VC model — connects to [[cryptos primary use case is capital formation not payments or store of value]].
+
+**Extraction hints:** At least 2-3 claims here: (1) permissionless launches create new fundraising cultural norms, (2) the 10x upside gap in traditional VC is a market failure that futarchy-governed launches solve, (3) public accountability from day 1 is a feature not a bug.
+
+**Context:** Felipe Montealegre runs Theia Research, a crypto-native investment firm focused on MetaDAO ecosystem. He's been one of the most articulate proponents of the futarchy-governed capital formation thesis. This tweet got 118 likes — high engagement for crypto-finance X.

inbox/archive/2026-03-05-anthropic-labor-market-impacts.md

@@ -0,0 +1,86 @@
+---
+type: source
+title: "Labor market impacts of AI: A new measure and early evidence"
+author: Maxim Massenkoff and Peter McCrory (Anthropic Research)
+date: 2026-03-05
+url: https://www.anthropic.com/research/labor-market-impacts
+domain: ai-alignment
+secondary_domains: [internet-finance, health, collective-intelligence]
+status: processed
+processed_by: theseus
+processed_date: 2026-03-08
+claims_extracted:
+  - "the gap between theoretical AI capability and observed deployment is massive across all occupations because adoption lag not capability limits determines real-world impact"
+  - "AI displacement hits young workers first because a 14 percent drop in job-finding rates for 22-25 year olds in exposed occupations is the leading indicator that incumbents organizational inertia temporarily masks"
+  - "AI-exposed workers are disproportionately female high-earning and highly educated which inverts historical automation patterns and creates different political and economic displacement dynamics"
+cross_domain_flags:
+  - "Rio: labor displacement economics — 14% drop in young worker hiring in exposed occupations, white-collar Great Recession scenario modeling"
+  - "Vida: healthcare practitioner exposure at 58% theoretical / 5% observed — massive gap, implications for clinical AI adoption claims"
+  - "Theseus: capability vs observed usage gap as jagged frontier evidence — 96% theoretical exposure in Computer & Math but only 32% actual usage"
+---
+
+# Labor Market Impacts of AI: A New Measure and Early Evidence
+
+Massenkoff & McCrory, Anthropic Research. Published March 5, 2026.
+
+## Summary
+
+Introduces "observed exposure" metric combining theoretical LLM capability (Eloundou et al. framework) with actual Claude usage data from Anthropic Economic Index. Finds massive gap between what AI could theoretically do and what it's actually being used for across all occupational categories.
+
+## Key Data
+
+### Theoretical vs Observed Exposure (selected categories)
+| Occupation | Theoretical | Observed |
+|---|---|---|
+| Computer & Math | 96% | 32% |
+| Business & Finance | 94% | 28% |
+| Office & Admin | 94% | 42% |
+| Management | 92% | 25% |
+| Legal | 88% | 15% |
+| Arts & Media | 85% | 20% |
+| Architecture & Engineering | 82% | 18% |
+| Life & Social Sciences | 80% | 12% |
+| Healthcare Practitioners | 58% | 5% |
+| Healthcare Support | 38% | 4% |
+| Construction | 18% | 3% |
+| Grounds Maintenance | 10% | 2% |
+
+### Most Exposed Occupations
+- Computer Programmers: 75% observed coverage
+- Customer Service Representatives: second-ranked
+- Data Entry Keyers: 67% coverage
+
+### Employment Impact (as of early 2026)
+- Zero statistically significant unemployment increase in exposed occupations
+- 14% drop in job-finding rate for young workers (22-25) in exposed fields — "just barely statistically significant"
+- Older workers unaffected
+- Authors note multiple alternative explanations for young worker effect
+
+### Demographic Profile of Exposed Workers
+- 16 percentage points more likely female
+- 47% higher average earnings
+- 4x higher rate of graduate degrees (17.4% vs 4.5%)
+
+### Great Recession Comparison
+- 2007-2009: unemployment doubled from 5% to 10%
+- Comparable doubling in top quartile AI-exposed occupations (3% to 6%) would be detectable in their framework
+- Has NOT happened yet — but framework designed for ongoing monitoring
+
+## Methodology
+- O*NET database (~800 US occupations)
+- Anthropic Economic Index (Claude usage data, Aug-Nov 2025)
+- Eloundou et al. (2023) theoretical feasibility ratings
+- Difference-in-differences comparing exposed vs unexposed cohorts
+- Task-level analysis, not industry classification
+
+## Alignment-Relevant Observations
+
+1. **The gap IS the story.** 97% of observed Claude usage involves theoretically feasible tasks, but observed coverage is a fraction of theoretical coverage in every category. The gap measures adoption lag, not capability limits.
+
+2. **Young worker hiring signal.** The 14% drop in job-finding rate for 22-25 year olds in exposed fields may be the leading indicator. Entry-level positions are where displacement hits first — incumbents are protected by organizational inertia.
+
+3. **White-collar vulnerability profile.** Exposed workers are disproportionately female, high-earning, and highly educated. This is the opposite of historical automation patterns (which hit low-skill workers first). The political and economic implications of displacing this demographic are different.
+
+4. **Healthcare gap is enormous.** 58% theoretical / 5% observed in healthcare practitioners. This connects directly to Vida's claims about clinical AI adoption — the capability exists, the deployment doesn't. The bottleneck is institutional, not technical.
+
+5. **Framework for ongoing monitoring.** This isn't a one-time study — it's infrastructure for tracking displacement as it happens. The methodology (prospective monitoring, not post-hoc attribution) is the contribution.

inbox/archive/2026-03-08-karpathy-autoresearch-collaborative-agents.md

@@ -0,0 +1,47 @@
+---
+type: source
+title: "Autoresearch must become asynchronously massively collaborative for agents — emulating a research community, not a single PhD student"
+author: "Andrej Karpathy (@karpathy)"
+twitter_id: "33836629"
+url: https://x.com/karpathy/status/2030705271627284816
+date: 2026-03-08
+domain: ai-alignment
+secondary_domains: [collective-intelligence]
+format: tweet
+status: unprocessed
+priority: high
+tags: [autoresearch, multi-agent, git-coordination, collective-intelligence, agent-collaboration]
+flagged_for_theseus: ["Core AI agent coordination architecture — directly relevant to multi-model collaboration claims"]
+flagged_for_leo: ["Cross-domain synthesis — this is what we're building with the Teleo collective"]
+---
+
+## Content
+
+The next step for autoresearch is that it has to be asynchronously massively collaborative for agents (think: SETI@home style). The goal is not to emulate a single PhD student, it's to emulate a research community of them.
+
+Current code synchronously grows a single thread of commits in a particular research direction. But the original repo is more of a seed, from which could sprout commits contributed by agents on all kinds of different research directions or for different compute platforms. Git(Hub) is *almost* but not really suited for this. It has a softly built in assumption of one "master" branch, which temporarily forks off into PRs just to merge back a bit later.
+
+I tried to prototype something super lightweight that could have a flavor of this, e.g. just a Discussion, written by my agent as a summary of its overnight run:
+https://t.co/tmZeqyDY1W
+Alternatively, a PR has the benefit of exact commits:
+https://t.co/CZIbuJIqlk
+but you'd never want to actually merge it... You'd just want to "adopt" and accumulate branches of commits. But even in this lightweight way, you could ask your agent to first read the Discussions/PRs using GitHub CLI for inspiration, and after its research is done, contribute a little "paper" of findings back.
+
+I'm not actually exactly sure what this should look like, but it's a big idea that is more general than just the autoresearch repo specifically. Agents can in principle easily juggle and collaborate on thousands of commits across arbitrary branch structures. Existing abstractions will accumulate stress as intelligence, attention and tenacity cease to be bottlenecks.
+
+## Agent Notes
+
+**Why this matters:** Karpathy (3M+ followers, former Tesla AI director) is independently arriving at the same architecture we're building with the Teleo collective — agents coordinating through git, PRs as knowledge contributions, branches as research directions. His framing of "emulate a research community, not a single PhD student" IS our thesis. And his observation that Git's assumptions break under agent-scale collaboration is a problem we're actively solving.
+
+**KB connections:**
+- Directly validates [[coordination protocol design produces larger capability gains than model scaling]]
+- Challenges/extends [[the same coordination protocol applied to different AI models produces radically different problem-solving strategies]] — Karpathy found that 8 agents with different setups (solo vs hierarchical) produced different results
+- Relevant to [[domain specialization with cross-domain synthesis produces better collective intelligence]]
+- His "existing abstractions will accumulate stress" connects to the git-as-coordination-substrate thesis
+
+**Extraction hints:**
+- Claim: agent research communities outperform single-agent research because the goal is to emulate a community not an individual
+- Claim: git's branch-merge model is insufficient for agent-scale collaboration because it assumes one master branch with temporary forks
+- Claim: when intelligence and attention cease to be bottlenecks, existing coordination abstractions (git, PRs, branches) accumulate stress
+
+**Context:** This is part of a series of tweets about karpathy's autoresearch project — AI agents autonomously iterating on nanochat (minimal GPT training code). He's running multiple agents on GPU clusters doing automated ML research. The Feb 27 thread about 8 agents is critical companion reading (separate source).

inbox/archive/2026-03-09-01resolved-x-archive.md

@@ -0,0 +1,63 @@
+---
+type: source
+title: "@01Resolved X archive — 100 most recent tweets"
+author: "01Resolved (@01Resolved)"
+url: https://x.com/01Resolved
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: processed
+processed_by: rio
+processed_date: 2026-03-09
+enrichments:
+  - "MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions"
+  - "futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent"
+tags: [metadao, governance-analytics, ranger-liquidation, solomon, decision-markets, turbine]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Analyst account providing the deepest on-chain forensics of MetaDAO governance events.
+  This is the data layer — while Proph3t provides ideology and Felipe provides thesis,
+  01Resolved provides the numbers. Key contribution: Ranger liquidation forensics with
+  exact trader counts, volume, alignment percentages. Also tracking Solomon treasury
+  governance and Turbine buyback mechanics. Low follower count (~500) but extremely high
+  signal density — this is the account writing the kind of analysis we should be writing.
+extraction_hints:
+  - "Ranger liquidation forensics: 92.41% pass-aligned, 33 traders, $119K volume — data for enriching futarchy governance claims"
+  - "Solomon treasury subcommittee analysis — evidence for 'futarchy-governed DAOs converge on traditional corporate governance scaffolding'"
+  - "Turbine buyback TWAP threshold filtering — mechanism design detail, potential new claim about automated treasury management"
+  - "Decision market participation data — contributes to 'MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions'"
+  - "Cross-reference: do contested decisions show higher volume than uncontested? The Ranger liquidation data vs routine proposals could test this"
+priority: high
+---
+
+# @01Resolved X Archive (March 2026)
+
+## Substantive Tweets
+
+### Ranger Liquidation Forensics
+- 92.41% of decision market value aligned with pass (liquidation)
+- 33 unique traders participated in the governance decision
+- $119K total trading volume in the decision market
+- Timeline analysis of how the market reached consensus
+- This is the most complete public dataset on a futarchy enforcement event
+
+### Solomon Treasury Subcommittee
+- Detailed analysis of DP-00001 (treasury subcommittee formation)
+- Tracking how Solomon is building traditional governance structures within futarchy framework
+- Coverage of committee composition, authority scope, reporting requirements
+- Signal: even futarchy-native projects need human-scale operational governance
+
+### Turbine Buyback Analysis
+- TWAP (time-weighted average price) threshold filtering for automated buybacks
+- Mechanism detail: buybacks trigger only when token price crosses specific thresholds
+- This is automated treasury management through price signals — a concrete mechanism design innovation
+- Connects to existing claim about ownership coin treasuries being actively managed
+
+### Decision Market Data
+- Tracks participation and volume across multiple MetaDAO governance decisions
+- Pattern: contested decisions (Ranger liquidation) show significantly higher volume than routine proposals
+- This data directly tests whether futarchy's "limited trading volume in uncontested decisions" is a feature (efficient agreement) or a bug (low participation)
+
+## Noise Filtered Out
+- ~80 tweets were engagement, community interaction, event promotion
+- Very high substantive ratio for the original content that does exist

inbox/archive/2026-03-09-8bitpenis-x-archive.md

@@ -0,0 +1,44 @@
+---
+type: source
+title: "@8bitpenis X archive — 100 most recent tweets"
+author: "8bitpenis.sol (@8bitpenis), host @ownershipfm"
+url: https://x.com/8bitpenis
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [community, futarchy, governance, treasury-liquidation, metadao-ecosystem]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Community voice and Ownership Podcast host. 23 MetaDAO references — deep governance
+  engagement. High volume (65K total tweets) but only 43% substantive in recent 100.
+  Key contribution: practical governance commentary, treasury liquidation mechanics
+  discussion ("any % customizable"), fundraising route optimization. Acts as the
+  community's informal amplifier and discussion facilitator. Cultural tone-setter
+  rather than mechanism designer.
+extraction_hints:
+  - "Treasury liquidation mechanics: 'any % customizable' — implementation detail for liquidation claim"
+  - "Fundraising route optimization discussions — practitioner perspective on capital formation"
+  - "Community sentiment data — cultural mapping for landscape musing"
+  - "Low standalone claim priority — community voice, not original analysis"
+priority: low
+---
+
+# @8bitpenis X Archive (March 2026)
+
+## Substantive Tweets
+
+### Governance Engagement
+- Deep engagement with MetaDAO governance proposals and debates
+- Treasury liquidation mechanics: customizable percentage thresholds
+- Memecoin positioning strategy discussions
+- Fundraising route optimization
+
+### Community Facilitation
+- Hosts spaces on MetaDAO, Futardio, and futarchy topics
+- Bridge between casual community and serious governance discussion
+- 23 direct MetaDAO references — embedded in ecosystem
+
+## Noise Filtered Out
+- 57% noise — high volume casual engagement, memes, banter
+- Substantive content focuses on governance mechanics and community coordination

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

@@ -0,0 +1,43 @@
+---
+type: source
+title: "@Abbasshaikh X archive — 100 most recent tweets"
+author: "Abbas (@Abbasshaikh), Umbra Privacy"
+url: https://x.com/Abbasshaikh
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [umbra, privacy, futardio, community-organizing, metadao-ecosystem]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Umbra Privacy builder and one of the most active community organizers in the MetaDAO
+  ecosystem. 14 direct MetaDAO references — strong Futardio community role. High volume
+  (32K total tweets) but substantive content focuses on privacy infrastructure and
+  futarchy community building. Umbra raised $3M via MetaDAO ICO with 7x first-week
+  performance. Abbas's role is more community coordinator than mechanism designer —
+  useful for culture mapping but low priority for claim extraction.
+extraction_hints:
+  - "Umbra ICO performance data ($3M raised, 7x first week) — enriches MetaDAO ICO track record"
+  - "Community organizing patterns around futardio — cultural data for landscape musing"
+  - "Privacy + ownership coins intersection — potential cross-domain connection"
+  - "Low claim extraction priority — community voice, not mechanism analysis"
+priority: low
+---
+
+# @Abbasshaikh X Archive (March 2026)
+
+## Substantive Tweets
+
+### Umbra Privacy
+- Building encrypted internet finance and ownership infrastructure
+- $3M raised via MetaDAO ICO, 7x first-week performance
+- Privacy as foundational layer for ownership coins
+
+### Community Organizing
+- Active AMA scheduling, team outreach for Futardio ecosystem
+- $20 allocation discussions on Futardio bids — grassroots participation patterns
+- Strong futardio community organizer role
+
+## Noise Filtered Out
+- 26% noise — casual engagement, memes, lifestyle content
+- High volume but moderate signal density

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

@@ -0,0 +1,42 @@
+---
+type: source
+title: "@AndrewSeb555 X archive — 100 most recent tweets"
+author: "Andrew Seb (@AndrewSeb555), Head of Eco @icmdotrun"
+url: https://x.com/AndrewSeb555
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [wider-ecosystem, governance, arbitrage, ai-agents, trading]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Head of Eco at ICM. 5 MetaDAO references — moderate ecosystem engagement. 74%
+  substantive. Interesting for arbitrage opportunity discussions (60-70% arb rates
+  mentioned) and governance/futarchy mechanics commentary. Also engaged with WLFI
+  and Clarity Act regulatory developments. More of an ecosystem participant than a
+  core builder or analyst.
+extraction_hints:
+  - "Arbitrage opportunity data (60-70%) — market efficiency data point"
+  - "WLFI & Clarity Act regulatory context — connects to our regulatory claims"
+  - "Liquidation process improvement discussions — enrichment for governance claims"
+  - "Low priority — moderate signal, mostly ecosystem participation"
+priority: low
+---
+
+# @AndrewSeb555 X Archive (March 2026)
+
+## Substantive Tweets
+
+### Governance and Arbitrage
+- 60-70% arbitrage opportunity discussions
+- Futarchy mechanics commentary
+- Liquidation process improvements
+- WLFI & Clarity Act regulatory preparations
+
+### Ecosystem Participation
+- 5 MetaDAO references — aware participant
+- AI agent market observations
+- Trading and technical analysis
+
+## Noise Filtered Out
+- 26% noise — community engagement, casual takes

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

@@ -0,0 +1,34 @@
+---
+type: source
+title: "@bharathshettyy X archive — 100 most recent tweets"
+author: "Biks (@bharathshettyy), Send Arcade"
+url: https://x.com/bharathshettyy
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [wider-ecosystem, send-arcade, futardio, community]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Send Arcade builder, GSoC'25. 9 MetaDAO references. 41% substantive (lowest individual
+  account). "First futardio, then futarchy, then make money" progression narrative is
+  interesting as a community adoption pathway. Ownership Radio involvement. Primarily
+  community participant rather than analyst or builder in the mechanism design sense.
+extraction_hints:
+  - "'First futardio, then futarchy, then make money' — community adoption pathway narrative"
+  - "Cultural data for landscape musing — community participant perspective"
+  - "Low claim extraction priority"
+priority: low
+---
+
+# @bharathshettyy X Archive (March 2026)
+
+## Substantive Tweets
+
+### Community Participation
+- "First futardio, then futarchy, then make money" — adoption progression narrative
+- Ownership Radio involvement
+- 9 MetaDAO references — active community participant
+
+## Noise Filtered Out
+- 59% noise — casual engagement, community interaction

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

@@ -0,0 +1,42 @@
+---
+type: source
+title: "@Blockworks X archive — 100 most recent tweets"
+author: "Blockworks (@Blockworks)"
+url: https://x.com/Blockworks
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [media, institutional, defi, stablecoins, blockworks-das]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Institutional crypto media (492K followers). Only 2 MetaDAO references in recent tweets.
+  Key signal: Blockworks DAS NYC (March 25) is where Felipe will present "The Token
+  Problem" — this is the institutional amplification event for the ownership coin thesis.
+  Stablecoin interest rate data (lowest since June 2023) and Polygon stablecoin supply
+  ATH ($3.4B) are useful macro datapoints. Low MetaDAO-specific content but important
+  as institutional validation channel.
+extraction_hints:
+  - "Blockworks DAS NYC March 25 — track for Felipe's Token Problem keynote extraction"
+  - "Stablecoin interest rates at lowest since June 2023 — macro context for internet finance"
+  - "Polygon stablecoin supply ATH $3.4B — cross-chain stablecoin flow data"
+  - "Null-result for MetaDAO claims — institutional media, not ecosystem analysis"
+priority: low
+---
+
+# @Blockworks X Archive (March 2026)
+
+## Substantive Tweets
+
+### Macro Data Points
+- Stablecoin interest rates at lowest since June 2023
+- Polygon stablecoin supply ATH of ~$3.4B (Feb 2026)
+- $14.9B, $17.6B liquidity references
+
+### DAS NYC Event
+- Blockworks DAS NYC March 25 — Felipe presenting Token Problem keynote
+- Institutional channel for ownership coin thesis amplification
+
+## Noise Filtered Out
+- 73% noise — news aggregation, event promotion, general crypto coverage
+- Only 27% substantive (lowest in network), mostly macro data

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

@@ -0,0 +1,39 @@
+---
+type: source
+title: "@DrJimFan X archive — 100 most recent tweets"
+author: "Jim Fan (@DrJimFan), NVIDIA GEAR Lab"
+url: https://x.com/DrJimFan
+date: 2026-03-09
+domain: ai-alignment
+format: tweet
+status: processed
+processed_by: theseus
+processed_date: 2026-03-09
+claims_extracted: []
+enrichments: []
+tags: [embodied-ai, robotics, human-data-scaling, motor-control]
+linked_set: theseus-x-collab-taxonomy-2026-03
+notes: |
+  Very thin for collaboration taxonomy claims. Only 22 unique tweets out of 100 (78 duplicates
+  from API pagination). Of 22 unique, only 2 are substantive — both NVIDIA robotics announcements
+  (EgoScale, SONIC). The remaining 20 are congratulations, emoji reactions, and brief replies.
+  EgoScale's "humans are the most scalable embodiment" thesis has alignment relevance but
+  is primarily a robotics capability claim. No content on AI coding tools, multi-agent systems,
+  collective intelligence, or formal verification. May yield claims in a future robotics-focused
+  extraction pass.
+---
+
+# @DrJimFan X Archive (Feb 20 – Mar 6, 2026)
+
+## Substantive Tweets
+
+### EgoScale: Human Video Pre-training for Robot Dexterity
+
+(status/2026709304984875202, 1,686 likes): "We trained a humanoid with 22-DoF dexterous hands to assemble model cars, operate syringes, sort poker cards, fold/roll shirts, all learned primarily from 20,000+ hours of egocentric human video with no robot in the loop. Humans are the most scalable embodiment on the planet. We discovered a near-perfect log-linear scaling law (R^2 = 0.998) between human video volume and action prediction loss [...] Most surprising result: a *single* teleop demo is sufficient to learn a never-before-seen task."
+
+### SONIC: 42M Transformer for Humanoid Whole-Body Control
+
+(status/2026350142652383587, 1,514 likes): "What can half of GPT-1 do? We trained a 42M transformer called SONIC to control the body of a humanoid robot. [...] We scaled humanoid motion RL to an unprecedented scale: 100M+ mocap frames and 500,000+ parallel robots across 128 GPUs. [...] After 3 days of training, the neural net transfers zero-shot to the real G1 robot with no finetuning. 100% success rate across 50 diverse real-world motion sequences."
+
+## Filtered Out
+~20 tweets: congratulations, emoji reactions, "OSS ftw!!", thanks, team shoutouts.

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

@@ -0,0 +1,42 @@
+---
+type: source
+title: "@FlashTrade X archive — 100 most recent tweets"
+author: "Flash.Trade (@FlashTrade)"
+url: https://x.com/FlashTrade
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [flash-trade, perps, solana, trading, leverage]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Perps protocol on Solana — "asset backed trading with zero slippage and on demand
+  liquidity." Large following (30K) but minimal MetaDAO ecosystem connection in tweet
+  content. Primarily tactical trading signals and product updates. Included in network
+  map via engagement analysis but appears peripheral to the futarchy/ownership coin
+  conversation. Low extraction priority — no mechanism design insights relevant to our
+  domain.
+extraction_hints:
+  - "No MetaDAO-specific claims identified"
+  - "Asset-backed trading model could connect to 'permissionless leverage on MetaDAO ecosystem tokens' if Flash integrates with ecosystem"
+  - "Null-result candidate — primarily trading signals, not mechanism design"
+priority: low
+---
+
+# @FlashTrade X Archive (March 2026)
+
+## Substantive Tweets
+
+### Trading Infrastructure
+- Leveraged derivatives (up to 50x) on Solana
+- Asset-backed trading model — zero slippage, on-demand liquidity
+- Primarily tactical: trading signals, market commentary
+
+### MetaDAO Connection
+- Identified via engagement analysis (metaproph3t + MetaDAOProject interactions)
+- Minimal substantive overlap with futarchy/ownership coin conversation in tweet content
+- Peripheral ecosystem participant
+
+## Noise Filtered Out
+- Despite 88% "substantive" ratio, most content is trading signals rather than mechanism design
+- Low relevance to knowledge base extraction goals

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

@@ -0,0 +1,52 @@
+---
+type: source
+title: "@futarddotio X archive — 100 most recent tweets"
+author: "Futardio (@futarddotio)"
+url: https://x.com/futarddotio
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [futardio, permissionless-launchpad, ownership-coins, capital-formation, metadao]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Official Futardio account — the permissionless ownership coin launchpad built on MetaDAO
+  infrastructure. Only 70 tweets total, very low noise. "Where dreams meet USDC" tagline.
+  Key value: launch announcements and mechanism explanations that aren't available from
+  other sources. Futardio represents the scalability thesis for MetaDAO — moving from
+  curated ICOs to permissionless launches. The first raise being 220x oversubscribed is
+  the single most important data point for the "internet capital markets compress fundraising"
+  claim.
+extraction_hints:
+  - "Futardio mechanism specifics — how permissionless launches work, what's automated vs human"
+  - "First raise metrics: 220x oversubscription as evidence for 'internet capital markets compress fundraising'"
+  - "Brand separation from MetaDAO — evidence for 'futarchy-governed permissionless launches require brand separation'"
+  - "Which projects are launching on Futardio vs MetaDAO curated ICOs — market segmentation data"
+  - "Low tweet volume means near-100% signal — almost every tweet is substantive"
+priority: medium
+---
+
+# @futarddotio X Archive (March 2026)
+
+## Substantive Tweets
+
+### Launch Mechanics
+- Permissionless: anyone can create an ownership coin raise without MetaDAO approval
+- Automated process: time-based preference curves, hard caps, minimum thresholds
+- Built on MetaDAO's Autocrat infrastructure but operates independently
+- Brand separation: Futardio is not "MetaDAO launches" — deliberate distance
+
+### First Raise Performance
+- $11M committed against $50K minimum goal (~220x oversubscribed)
+- This is the proof point for permissionless capital formation demand
+- Oversubscription triggers pro-rata allocation — everyone gets proportional share
+- Refund mechanism for excess capital — clean, automated
+
+### Ecosystem Position
+- "Where dreams meet USDC" — positioning as capital formation infrastructure, not governance
+- Futardio is the application layer; MetaDAO/Autocrat is the protocol layer
+- This architecture mirrors the Proph3t vision of MetaDAO as protocol infrastructure
+
+## Noise Filtered Out
+- Very little noise — 70 total tweets, most are substantive announcements or mechanism explanations
+- No casual engagement pattern — this is a pure project account

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

@@ -0,0 +1,49 @@
+---
+type: source
+title: "@HurupayApp X archive — 100 most recent tweets"
+author: "Hurupay (@HurupayApp)"
+url: https://x.com/HurupayApp
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [hurupay, payments, neobank, metadao-ecosystem, failed-ico, minimum-raise]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Crypto-native neobank (US/EUR/GBP accounts, virtual USD cards, savings, US stocks).
+  Important for the knowledge base primarily as the MetaDAO ICO that failed to reach
+  minimum raise — proving the protection mechanism works. The product itself (fiat on/off
+  ramps, $0.01 transfers vs $100+ traditional) is standard fintech positioning. Key data:
+  $2.6B raised stat needs verification — seems too high for this project, may be
+  referencing total MetaDAO ecosystem. Backed by fdotinc with Microsoft/Bankless angels.
+extraction_hints:
+  - "Failed ICO as mechanism proof — minimum raise threshold returned funds to investors automatically"
+  - "Enrichment target: 'futarchy-governed liquidation is the enforcement mechanism' — Hurupay shows the softer protection (minimum raise threshold) vs Ranger (full liquidation)"
+  - "$0.01 transfer fees vs $100+ traditional, 3-second settlement vs 72 hours — standard fintech disruption metrics, low extraction priority"
+  - "Backed by fdotinc + Microsoft/Bankless angels — institutional backing for MetaDAO ecosystem project"
+priority: low
+---
+
+# @HurupayApp X Archive (March 2026)
+
+## Substantive Tweets
+
+### Product Positioning
+- US, EUR, GBP bank accounts + virtual USD cards
+- $0.01 transfer fees vs $100+ traditional banking
+- 3-second settlement vs 72-hour traditional timeframe
+- "Crypto for everyday people" — mass-market fintech positioning
+
+### MetaDAO ICO Failure (Positive Signal)
+- Did not reach minimum raise threshold on MetaDAO ICO
+- All funds returned to depositors automatically — no money lost
+- This is the protection mechanism working as designed
+- Demonstrates that not every MetaDAO launch succeeds — but failure is safe
+
+### Backing and Legitimacy
+- Backed by fdotinc with angels from Microsoft and Bankless
+- Institutional backing provides credibility signal for MetaDAO ecosystem
+
+## Noise Filtered Out
+- ~15% noise — product promotion, community engagement
+- Primarily product-focused messaging

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

@@ -0,0 +1,76 @@
+---
+type: source
+title: "@karpathy X archive — 100 most recent tweets"
+author: "Andrej Karpathy (@karpathy)"
+url: https://x.com/karpathy
+date: 2026-03-09
+domain: ai-alignment
+format: tweet
+status: processed
+processed_by: theseus
+processed_date: 2026-03-09
+claims_extracted:
+  - "AI agents excel at implementing well-scoped ideas but cannot generate creative experiment designs which makes the human role shift from researcher to agent workflow architect"
+  - "deep technical expertise is a greater force multiplier when combined with AI agents because skilled practitioners delegate more effectively than novices"
+  - "the progression from autocomplete to autonomous agent teams follows a capability-matched escalation where premature adoption creates more chaos than value"
+enrichments: []
+tags: [human-ai-collaboration, agent-architectures, autoresearch, coding-agents, multi-agent]
+linked_set: theseus-x-collab-taxonomy-2026-03
+curator_notes: |
+  Richest account in the collaboration taxonomy batch. 21 relevant tweets out of 43 unique.
+  Karpathy is systematically documenting the new human-AI division of labor through his
+  autoresearch project: humans provide direction/taste/creative ideation, agents handle
+  implementation/iteration/parallelism. The "programming an organization" framing
+  (multi-agent research org) is the strongest signal for the collaboration taxonomy thread.
+  Viral tweet (37K likes) marks the paradigm shift claim. Notable absence: very little on
+  alignment/safety/governance.
+---
+
+# @karpathy X Archive (Feb 21 – Mar 8, 2026)
+
+## Key Tweets by Theme
+
+### Autoresearch: AI-Driven Research Loops
+
+- **Collaborative multi-agent research vision** (status/2030705271627284816, 5,760 likes): "The next step for autoresearch is that it has to be asynchronously massively collaborative for agents (think: SETI@home style). The goal is not to emulate a single PhD student, it's to emulate a research community of them. [...] Agents can in principle easily juggle and collaborate on thousands of commits across arbitrary branch structures. Existing abstractions will accumulate stress as intelligence, attention and tenacity cease to be bottlenecks."
+
+- **Autoresearch repo launch** (status/2030371219518931079, 23,608 likes): "I packaged up the 'autoresearch' project into a new self-contained minimal repo [...] the human iterates on the prompt (.md) - the AI agent iterates on the training code (.py) [...] every dot is a complete LLM training run that lasts exactly 5 minutes."
+
+- **8-agent research org experiment** (status/2027521323275325622, 8,645 likes): "I had the same thought so I've been playing with it in nanochat. E.g. here's 8 agents (4 claude, 4 codex), with 1 GPU each [...] I tried a few setups: 8 independent solo researchers, 1 chief scientist giving work to 8 junior researchers, etc. [...] They are very good at implementing any given well-scoped and described idea but they don't creatively generate them. But the goal is that you are now programming an organization."
+
+- **Meta-optimization** (status/2029701092347630069, 6,212 likes): "I now have AI Agents iterating on nanochat automatically [...] over the last ~2 weeks I almost feel like I've iterated more on the 'meta-setup' where I optimize and tune the agent flows even more than the nanochat repo directly."
+
+- **Research org as benchmark** (status/2029702379034267985, 1,031 likes): "the real benchmark of interest is: 'what is the research org agent code that produces improvements on nanochat the fastest?' this is the new meta."
+
+- **Agents closer to hyperparameter tuning than novel research** (status/2029957088022254014, 105 likes): "AI agents are very good at implementing ideas, but a lot less good at coming up with creative ones. So honestly, it's a lot closer to hyperparameter tuning right now than coming up with new/novel research."
+
+### Human-AI Collaboration Patterns
+
+- **Programming has fundamentally changed** (status/2026731645169185220, 37,099 likes): "It is hard to communicate how much programming has changed due to AI in the last 2 months [...] coding agents basically didn't work before December and basically work since [...] You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. [...] It's not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas."
+
+- **Tab → Agent → Agent Teams** (status/2027501331125239822, 3,821 likes): "Cool chart showing the ratio of Tab complete requests to Agent requests in Cursor. [...] None -> Tab -> Agent -> Parallel agents -> Agent Teams (?) -> ??? If you're too conservative, you're leaving leverage on the table. If you're too aggressive, you're net creating more chaos than doing useful work."
+
+- **Deep expertise as multiplier** (status/2026743030280237562, 880 likes): "'prompters' is doing it a disservice and is imo a misunderstanding. I mean sure vibe coders are now able to get somewhere, but at the top tiers, deep technical expertise may be *even more* of a multiplier than before because of the added leverage."
+
+- **AI as delegation, not magic** (status/2026735109077135652, 243 likes): "Yes, in this intermediate state, you go faster if you can be more explicit and actually understand what the AI is doing on your behalf, and what the different tools are at its disposal, and what is hard and what is easy. It's not magic, it's delegation."
+
+- **Removing yourself as bottleneck** (status/2026738848420737474, 694 likes): "how can you gather all the knowledge and context the agent needs that is currently only in your head [...] the goal is to arrange the thing so that you can put agents into longer loops and remove yourself as the bottleneck. 'every action is error', we used to say at tesla."
+
+- **Human still needs IDE oversight** (status/2027503094016446499, 119 likes): "I still keep an IDE open and surgically edit files so yes. I still notice dumb issues with the code which helps me prompt better."
+
+- **AI already writing 90% of code** (status/2030408126688850025, 521 likes): "definitely. the current one is already 90% AI written I ain't writing all that"
+
+- **Teacher's unique contribution** (status/2030387285250994192, 430 likes): "Teacher input is the unique sliver of contribution that the AI can't make yet (but usually already easily understands when given)."
+
+### Agent Infrastructure
+
+- **CLIs as agent-native interfaces** (status/2026360908398862478, 11,727 likes): "CLIs are super exciting precisely because they are a 'legacy' technology, which means AI agents can natively and easily use them [...] It's 2026. Build. For. Agents."
+
+- **Compute infrastructure for agentic loops** (status/2026452488434651264, 7,422 likes): "the workflow that may matter the most (inference decode *and* over long token contexts in tight agentic loops) is the one hardest to achieve simultaneously."
+
+- **Agents replacing legacy interfaces** (status/2030722108322717778, 1,941 likes): "Every business you go to is still so used to giving you instructions over legacy interfaces. [...] Please give me the thing I can copy paste to my agent."
+
+- **Cross-model transfer confirmed** (status/2030777122223173639, 3,840 likes): "I just confirmed that the improvements autoresearch found over the last 2 days of (~650) experiments on depth 12 model transfer well to depth 24."
+
+## Filtered Out
+~22 tweets: casual replies, jokes, hyperparameter discussion, off-topic commentary.

inbox/archive/2026-03-09-kru-tweets-x-archive.md

@@ -0,0 +1,38 @@
+---
+type: source
+title: "@kru_tweets X archive — 100 most recent tweets"
+author: "kru (@kru_tweets), Umbra Privacy / Superteam"
+url: https://x.com/kru_tweets
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [umbra, privacy, solana, superteam, stablecoins]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Umbra Privacy team + Superteam member. 3 MetaDAO references. $54M Friends & Family
+  funding round mentioned. Privacy infrastructure and yield coin partnerships. Moderate
+  ecosystem engagement — connected through Umbra (MetaDAO ICO project). Low claim
+  extraction priority.
+extraction_hints:
+  - "Umbra ecosystem context — connects to Abbasshaikh archive for fuller Umbra picture"
+  - "$54M funding round data — if Umbra-related, enriches ICO performance tracking"
+  - "Low priority — privacy builder context, not mechanism analysis"
+priority: low
+---
+
+# @kru_tweets X Archive (March 2026)
+
+## Substantive Tweets
+
+### Privacy Ecosystem
+- Hoppy Privacy & Umbra ecosystem involvement
+- Yieldcoin partnerships
+- $54M Friends & Family funding round
+
+### Solana / Superteam
+- Superteam member perspective on Solana ecosystem
+- Privacy infrastructure development
+
+## Noise Filtered Out
+- 36% noise — casual engagement, community banter

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

@@ -0,0 +1,41 @@
+---
+type: source
+title: "@MCGlive X archive — 100 most recent tweets"
+author: "MCG (@MCGlive)"
+url: https://x.com/MCGlive
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [media, trading, solana, metadao, launchpads]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Live research and trading content on Solana ecosystem. 7 MetaDAO references. 91%
+  substantive ratio but content is primarily trading-focused (market sentiment, price
+  action, project evaluations) rather than mechanism design. Notable for candid market
+  commentary — mentions ponzi dynamics explicitly. Useful as broader Solana ecosystem
+  context but low priority for claim extraction.
+extraction_hints:
+  - "Solana ecosystem market sentiment — context for MetaDAO ecosystem positioning"
+  - "Ponzi dynamics acknowledgment — honest market structure commentary"
+  - "Launchpad comparisons — how MCG evaluates MetaDAO vs other launch platforms"
+  - "Null-result likely — primarily trading content, not mechanism design"
+priority: low
+---
+
+# @MCGlive X Archive (March 2026)
+
+## Substantive Tweets
+
+### Market Commentary
+- Trading-focused analysis of Solana ecosystem projects
+- Candid about market dynamics including ponzi structures
+- $BEAN parabolic growth (43x) noted — market speculation patterns
+
+### Ecosystem Coverage
+- Launchpad comparisons and startup evaluations
+- 7 MetaDAO references — moderate ecosystem awareness
+- Primarily covers MetaDAO from trading/investment angle
+
+## Noise Filtered Out
+- 9% noise — mostly substantive but trading-focused rather than mechanism-focused

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

@@ -0,0 +1,72 @@
+---
+type: source
+title: "@MetaDAOProject X archive — 100 most recent tweets"
+author: "MetaDAO (@MetaDAOProject)"
+url: https://x.com/MetaDAOProject
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: processed
+processed_by: rio
+processed_date: 2026-03-09
+enrichments:
+  - "futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent"
+tags: [metadao, futardio, ownership-coins, ranger-liquidation, hurupay, ico]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Official project account. Higher signal-to-noise than individual accounts because
+  it's curated announcements, not conversation. ~30 substantive tweets. The two
+  highest-engagement posts are Futardio launch (235K impressions) and Ranger liquidation
+  ($5M USDC distribution, 160K impressions) — these are the defining events of the
+  current MetaDAO cycle. Also notable: Hurupay ICO failure where minimum raise protection
+  worked (didn't reach threshold, funds returned). This is a positive failure — the
+  mechanism protecting investors even when a project doesn't succeed.
+extraction_hints:
+  - "Hurupay ICO failure as positive mechanism proof — minimum raise threshold protected investors. New claim candidate."
+  - "Futardio first raise metrics: $11M vs $50K goal, 220x oversubscribed — data point for 'internet capital markets compress fundraising' claim"
+  - "Ranger liquidation: $5M USDC returned, 92.41% pass vote — enriches 'futarchy-governed liquidation is the enforcement mechanism' claim"
+  - "Treasury subcommittee formation for Solomon — enriches 'futarchy-governed DAOs converge on traditional corporate governance scaffolding'"
+  - "'ICOs have undeniable PMF but tokens are fundamentally broken' (RT of NoahNewfield) — frames the problem ownership coins solve"
+  - "Connection: AI scaling capital formation — RT of dbarabander 'only form of capital formation that can scale with AI is MetaDAO'"
+priority: high
+---
+
+# @MetaDAOProject X Archive (March 2026)
+
+## Substantive Tweets
+
+### Futardio Launch (Highest Engagement)
+- 235K impressions on launch announcement
+- Permissionless capital formation — anyone can launch an ownership coin
+- First raise: $11M committed against $50K minimum, ~220x oversubscribed
+- Positioning: "the future of capital formation is permissionless"
+
+### Ranger Finance Liquidation (Second Highest Engagement)
+- 160K impressions on liquidation announcement
+- $5M USDC distributed back to Ranger token holders
+- First enforcement event in MetaDAO ecosystem
+- Framing: "this is what happens when a project doesn't deliver — the market forces accountability"
+- 92.41% of decision market aligned with pass (liquidation)
+- 33 unique traders participated in the decision market
+
+### Hurupay ICO — Minimum Raise Protection
+- Hurupay didn't reach minimum raise threshold
+- All committed funds returned to depositors automatically
+- Positive failure: the mechanism worked as designed to protect investors
+- No money lost, no drama — the system just worked quietly
+
+### Solomon Treasury Subcommittee
+- Formation of structured treasury oversight for Solomon project
+- Decision proposal DP-00001 establishing the subcommittee
+- Signal: futarchy-governed projects naturally developing traditional corporate governance structures
+- Connects to existing claim about DAOs converging on corporate scaffolding
+
+### Ecosystem Growth Signals
+- RT of community members discussing MetaDAO + AI convergence
+- RT of NoahNewfield: "ICOs have undeniable PMF, but the tokens they produce are fundamentally broken" — framing the problem
+- Multiple RTs of ecosystem project updates (Umbra, Avici, Turbine)
+- Growing media coverage (SolanaFloor, Blockworks mentions)
+
+## Noise Filtered Out
+- ~70 tweets were RTs of ecosystem content, event announcements, community engagement
+- Account functions primarily as amplifier/curator, not original analysis

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

@@ -0,0 +1,62 @@
+---
+type: source
+title: "@metanallok X archive — 100 most recent tweets"
+author: "Nallok (@metanallok), co-founder MetaDAO"
+url: https://x.com/metanallok
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: processed
+processed_by: rio
+processed_date: 2026-03-09
+claims_extracted:
+  - "futarchy implementations must simplify theoretical mechanisms for production adoption because original designs include impractical elements that academics tolerate but users reject"
+tags: [metadao, futardio, mechanism-design, ownership-coins, co-founder]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  MetaDAO co-founder, more operational than Proph3t. Nallok's tweets reveal
+  implementation details that don't appear in the official account or blog posts.
+  Key value: Futardio mechanism design specifics — time-based preference curves,
+  hard caps, automated processes. His comment that "Robin wanted random proposal
+  outcomes — impractical for production" shows the gap between Hanson's theory and
+  MetaDAO's pragmatic implementation. Lower public profile than Proph3t but higher
+  density of mechanism details when he does post.
+extraction_hints:
+  - "Futardio mechanism details: time-based preference, hard caps, automated process — enriches existing MetaDAO mechanism claims"
+  - "Robin Hanson theory vs MetaDAO practice gap — 'random proposal outcomes impractical for production'"
+  - "Co-founder compensation structure (2% of supply per $1B FDV increase, up to 10% at $5B) — mechanism design for team incentive alignment"
+  - "Enrichment target: 'MetaDAOs Autocrat program implements futarchy through conditional token markets' — Nallok provides implementation details"
+  - "Potential new claim: futarchy implementations must simplify theoretical mechanisms for production use"
+priority: medium
+---
+
+# @metanallok X Archive (March 2026)
+
+## Substantive Tweets
+
+### Futardio Mechanism Design
+- Time-based preference curves in ICO participation — earlier commitment gets better allocation
+- Hard caps on individual raise amounts to prevent whale domination
+- Fully automated process — no human gatekeeping on launches
+- These are implementation details that don't appear in MetaDAO's public documentation
+
+### Theory vs Practice Gap
+- "Robin wanted random proposal outcomes — impractical for production"
+- MetaDAO deliberately simplified Hanson's original futarchy design for usability
+- Pragmatic trade-offs: theoretical optimality sacrificed for practical adoption
+- This is a important signal about how futarchy actually gets built vs how it's theorized
+
+### Team Incentive Structure
+- Proph3t/Nallok compensation: 2% of META supply per $1B FDV increase, up to 10% at $5B
+- This is itself a mechanism design statement — team compensation tied to protocol success
+- No upfront allocation, pure performance-based
+- Connects to our claims about token economics replacing management fees
+
+### Ecosystem Building
+- Engagement with Futardio launch projects
+- Technical support for teams building on MetaDAO infrastructure
+- Commentary on governance proposals with implementation perspective
+
+## Noise Filtered Out
+- Heavy engagement/reply pattern — most tweets are community interaction
+- When substantive, tends toward implementation detail over ideology (opposite of Proph3t)

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

@@ -0,0 +1,71 @@
+---
+type: source
+title: "@metaproph3t X archive — 100 most recent tweets"
+author: "Proph3t (@metaproph3t), co-founder MetaDAO"
+url: https://x.com/metaproph3t
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: processed
+processed_by: rio
+processed_date: 2026-03-09
+claims_extracted:
+  - "ownership coins primary value proposition is investor protection not governance quality because anti-rug enforcement through market-governed liquidation creates credible exit guarantees that no amount of decision optimization can match"
+enrichments:
+  - "futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent"
+tags: [metadao, futarchy, ownership-coins, futardio, governance, capital-formation]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Core voice of the MetaDAO movement. ~46 substantive tweets out of 100. This is where
+  the ideology lives — Proph3t doesn't post casually. When he tweets, it's either a
+  mechanism insight, a movement-building statement, or ecosystem commentary. The register
+  is earnest maximalism with technical depth. Key signal: his framing is shifting from
+  "futarchy governance" to "market oversight" and "ownership coins" — tracking this
+  language evolution matters for understanding how MetaDAO positions itself.
+extraction_hints:
+  - "Futardio as permissionless launchpad — mechanism design claims about time-based preference, hard caps, separation from MetaDAO brand"
+  - "Ranger Finance liquidation as first enforcement event — futarchy actually working as designed"
+  - "'Market oversight not community governance' — reframing futarchy away from voting analogy"
+  - "Anti-rug as #1 value prop — 'the number one selling point of ownership coins is that they are anti-rug'"
+  - "Enrichment target: existing claim 'futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible'"
+  - "Enrichment target: 'MetaDAO is the futarchy launchpad on Solana' — Futardio changes this, MetaDAO is becoming the protocol layer not the launchpad"
+  - "Tension: Proph3t says 'MetaDAO is as much a social movement as a cryptocurrency project' — does movement framing undermine mechanism credibility?"
+priority: high
+---
+
+# @metaproph3t X Archive (March 2026)
+
+## Substantive Tweets
+
+### Futardio Launch & Permissionless Capital Formation
+- Futardio is live as permissionless launchpad — anyone can raise capital through ownership coins without MetaDAO gatekeeping
+- "the beauty of futardio is that none of these launches need to be associated with metadao at all. which means we can permissionlessly scale"
+- Framing shift: MetaDAO as protocol infrastructure, Futardio as the permissionless application layer
+- First Futardio raise: massively oversubscribed (~220x), $11M vs $50K goal
+
+### Ranger Finance Liquidation (First Enforcement Event)
+- Ranger liquidation proposal passed — first time futarchy governance actually forced a project to return treasury
+- $5M USDC distributed back to token holders
+- Proph3t frames this as the system working: "this is what anti-rug looks like in practice"
+- 92.41% pass-aligned in decision market
+- Key mechanism insight: liquidation is the credible threat that makes the whole system work
+
+### Ownership Coin Ideology
+- "the number one selling point of ownership coins is that they are anti-rug"
+- "MetaDAO is as much a social movement as it is a cryptocurrency project — thousands have already been infected by the idea that futarchy will re-architect human civilization"
+- Distinguishes "market oversight" from "community governance" — futarchy is not voting, it's market-based evaluation
+- "ownership coins" terminology replacing "governance tokens" — deliberate reframing
+
+### Mechanism Design Commentary
+- Notes that Robin Hanson "wanted random proposal outcomes — impractical for production" — pragmatism over theory purity
+- Anti-rug > governance: the primary value prop is investor protection, not decision quality
+- Market oversight framing: "the market doesn't vote on proposals, it prices outcomes"
+
+### Ecosystem Commentary
+- Engagement with Solana ecosystem builders (Drift, Sanctum adoption)
+- Commentary on competitor failures (pump.fun losses, meme coin rugs) as validation of ownership coin model
+- Bullish on AI + crypto convergence but mechanism-focused, not hype
+
+## Noise Filtered Out
+- ~54 tweets were replies, emoji reactions, casual banter, RTs without commentary
+- Engagement pattern: high reply rate to ecosystem builders, low engagement with outsiders

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

@@ -0,0 +1,48 @@
+---
+type: source
+title: "@mmdhrumil X archive — 100 most recent tweets"
+author: "Dhrumil (@mmdhrumil), co-founder Archer Exchange"
+url: https://x.com/mmdhrumil
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [archer, market-making, on-chain-matching, defi, solana, metadao-ecosystem]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Market making infrastructure builder on Solana. Co-founder of Archer Exchange — fully
+  on-chain matching with dedicated, writable-only-by-you order books for each market
+  maker. Key insight: "prop AMMs did extremely well" — observation about AMM design
+  driving Archer's architecture. His 200% confidence on "Solana DeFi overtakes Hyperliquid
+  within 2 years" is a trackable prediction. Mechanism design focus on matching and
+  execution rather than governance — complementary perspective to the futarchy accounts.
+extraction_hints:
+  - "On-chain matching architecture — each MM gets dedicated writable-only-by-you order book. New mechanism design pattern."
+  - "Prop AMM observation driving design — evidence for how market structure informs protocol design"
+  - "'Solana DeFi overtakes Hyperliquid within 2 years' — trackable prediction, potential position candidate"
+  - "Connection to existing 'permissionless leverage on MetaDAO ecosystem tokens' claim — Archer provides the market making infrastructure"
+priority: low
+---
+
+# @mmdhrumil X Archive (March 2026)
+
+## Substantive Tweets
+
+### Archer Exchange Architecture
+- Fully on-chain matching — each market maker gets dedicated, writable-only-by-you order book
+- Permission-less execution with competitive quotes model
+- Design inspired by observation that "prop AMMs did extremely well"
+- "Best quotes for your trades via fully on-chain matching" vs aggregator models
+
+### Market Making Infrastructure
+- Market maker defense strategies — most MM logic is reactive/responsive
+- On-chain matching as primitive infrastructure layer
+- Solving the execution quality problem for Solana DeFi
+
+### Predictions
+- "200% confidence: Solana DeFi overtakes Hyperliquid within 2 years"
+- Infrastructure thesis: Solana's composability advantage compounds over time
+
+## Noise Filtered Out
+- ~20% noise — community engagement, casual takes
+- Strong mechanism design focus when substantive

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

@@ -0,0 +1,43 @@
+---
+type: source
+title: "@mycorealms X archive — 100 most recent tweets"
+author: "Mycorealms (@mycorealms)"
+url: https://x.com/mycorealms
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [mycorealms, farming, on-chain-governance, futardio, community, solana]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Real-world asset meets futarchy — Mycorealms is a community-run farming project on
+  Solana where contributors steer agricultural expansion with on-chain governance.
+  Interesting because it's a non-financial use case for ownership coins. Active in the
+  Futards community, promotes Futarded memecoin launched on Futardio. Lower priority
+  for claim extraction but worth noting as evidence that ownership coin model extends
+  beyond pure DeFi.
+extraction_hints:
+  - "Real-world asset governance via ownership coins — extends 'ownership coins' thesis beyond DeFi to physical assets"
+  - "Community-run agriculture with on-chain governance — unusual use case worth flagging"
+  - "Futardio participation — additional evidence for permissionless launch adoption"
+  - "Low priority for standalone claims but useful as enrichment data for scope of ownership coin model"
+priority: low
+---
+
+# @mycorealms X Archive (March 2026)
+
+## Substantive Tweets
+
+### Real-World Asset Governance
+- Community-run farming project using on-chain governance for agricultural decisions
+- Contributors steer real agricultural expansion — not just financial assets
+- Transparent governance: decisions about land use, crop selection, resource allocation
+
+### Futardio Ecosystem Participation
+- Active in Futards community
+- Promotes Futarded memecoin launched on Futardio platform
+- Demonstrates non-DeFi adoption of ownership coin infrastructure
+
+## Noise Filtered Out
+- ~17% noise — community engagement, meme content
+- Product-focused when substantive

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

@@ -0,0 +1,44 @@
+---
+type: source
+title: "@ownershipfm X archive — 100 most recent tweets"
+author: "Ownership Podcast (@ownershipfm), hosted by @8bitpenis"
+url: https://x.com/ownershipfm
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [ownership-podcast, media, futarchy, metadao, community-media]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Primary media outlet for the MetaDAO/futarchy ecosystem — 40 MetaDAO references, highest
+  of any account in the network. Hosted by 8bitpenis, produced by Blockformer, powered by
+  MetaDAO. The podcast/spaces format means tweet content is mostly episode promotion and
+  live discussion summaries rather than original analysis. Valuable as cultural artifact
+  and for tracking which topics the community discusses, but low claim extraction priority.
+  Guest list and topic selection reveal ecosystem priorities.
+extraction_hints:
+  - "Episode topics and guest list — maps which themes the ecosystem considers important"
+  - "Futarchy educational content — how the community explains itself to newcomers"
+  - "Cultural artifact for landscape musing — register, tone, community identity signals"
+  - "Low standalone claim priority — primarily amplification and discussion facilitation"
+priority: low
+---
+
+# @ownershipfm X Archive (March 2026)
+
+## Substantive Tweets
+
+### Podcast/Spaces Content
+- Ownership Radio series covering MetaDAO ecosystem
+- Futarchy educational content for ecosystem newcomers
+- Guest interviews with ecosystem builders and analysts
+- Live spaces discussions on governance events, new launches
+
+### Cultural Signal
+- 40 direct MetaDAO references — strongest ecosystem media connection
+- Tone: earnest, community-building, technically accessible
+- Bridges between casual community and serious mechanism discussion
+
+## Noise Filtered Out
+- 34% noise — event promotion, scheduling, casual engagement
+- Content is primarily facilitative rather than analytical

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

@@ -0,0 +1,62 @@
+---
+type: source
+title: "@oxranga X archive — 100 most recent tweets"
+author: "xranga (@oxranga), co-founder Solomon Labs"
+url: https://x.com/oxranga
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: processed
+processed_by: rio
+processed_date: 2026-03-09
+claims_extracted:
+  - "stablecoin flow velocity is a better predictor of DeFi protocol health than static TVL because flows measure capital utilization while TVL only measures capital parked"
+tags: [solomon, yaas, yield-as-a-service, stablecoins, defi, metadao-ecosystem]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Solomon Labs co-founder building within the MetaDAO ecosystem. Lower tweet volume (~320
+  total) but high density when he posts. Key contribution: the YaaS (Yield-as-a-Service)
+  thesis and stablecoin flow analysis. His "moats were made of friction" line is a clean
+  articulation of DeFi disruption logic that maps to our teleological economics framework.
+  Solomon is also the governance stress-test case — treasury subcommittee debates show
+  how futarchy-governed projects handle operational decisions.
+extraction_hints:
+  - "YaaS (Yield-as-a-Service) as DeFi primitive — new concept, potential claim about yield commoditization"
+  - "'Stablecoin flows > TVL' as metric — challenges standard DeFi valuation framework, potential claim"
+  - "'Moats were made of friction' — maps directly to 'transaction costs determine organizational boundaries' in foundations"
+  - "Solomon Lab Notes #05 — detailed builder perspective on futarchy-governed treasury management"
+  - "Connection to teleological economics: friction removal as disruption mechanism is exactly what our framework predicts"
+priority: medium
+---
+
+# @oxranga X Archive (March 2026)
+
+## Substantive Tweets
+
+### YaaS (Yield-as-a-Service) Thesis
+- Yield generation becoming a commoditized service layer in DeFi
+- Projects shouldn't build their own yield infrastructure — they should plug into YaaS providers
+- This is the "give away the commoditized layer" pattern applied to DeFi yields
+- Solomon positioning as YaaS infrastructure for the MetaDAO ecosystem
+
+### Stablecoin Flow Analysis
+- "Stablecoin flows > TVL" — flow metrics better predict protocol health than static TVL
+- TVL is a snapshot, flows are a movie — you need to see capital velocity not just capital parked
+- This challenges the standard DeFi valuation framework that uses TVL as primary metric
+- Connects to our claims about internet finance generating GDP growth through capital velocity
+
+### "Moats Were Made of Friction"
+- Clean articulation: DeFi moats in the previous cycle were built on user friction (complex UIs, high switching costs, information asymmetry)
+- As friction gets removed by better tooling and composability, those moats dissolve
+- Surviving protocols need moats built on something other than friction — network effects, data advantages, governance
+- Maps directly to our teleological economics claims about transaction costs and organizational boundaries
+
+### Solomon Governance
+- Lab Notes series documenting Solomon's governance experiments
+- Treasury management decisions going through futarchy
+- Practical challenges: how to handle operational decisions (hiring, vendor payments) through market mechanisms
+- Signal: even a committed futarchy project needs traditional governance for operational tempo
+
+## Noise Filtered Out
+- ~80% of tweets were casual engagement, RTs, brief replies
+- Low volume but consistently substantive when original content appears

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

@@ -0,0 +1,58 @@
+---
+type: source
+title: "@PineAnalytics X archive — 100 most recent tweets"
+author: "Pine Analytics (@PineAnalytics)"
+url: https://x.com/PineAnalytics
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [metadao, analytics, futardio, decision-markets, governance-data, jupiter]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  On-chain analytics research hub — the data arm of the MetaDAO ecosystem. Pine produced
+  the Q4 2025 quarterly report and Futardio launch metrics. Their work is pure data with
+  minimal editorial — exactly the kind of source that produces high-confidence enrichments
+  to existing claims. Key contribution: decision market participation data, ICO performance
+  metrics, and comparative governance analysis (Jupiter voting vs MetaDAO futarchy). Already
+  have an existing archive for the Q4 report (2026-03-03-pineanalytics-metadao-q4-2025-quarterly-report.md)
+  and Futardio launch (2026-03-05-pineanalytics-futardio-launch-metrics.md).
+extraction_hints:
+  - "Decision market data across multiple proposals — volume, trader count, alignment percentages"
+  - "bankme -55% in 45min vs MetaDAO protections — data point for 'futarchy-governed liquidation' claim"
+  - "Jupiter governance comparison: 303 views, 2 comments vs futarchy $40K volume / 122 trades — enriches 'token voting DAOs offer no minority protection' claim"
+  - "Futardio launch metrics already partially archived — check for new data not in existing archive"
+  - "Cross-reference with existing archives to avoid duplication"
+priority: medium
+---
+
+# @PineAnalytics X Archive (March 2026)
+
+## Substantive Tweets
+
+### Decision Market Data
+- Tracks volume and participation across MetaDAO governance proposals
+- Provides the quantitative backbone for claims about futarchy effectiveness
+- Key data: contested decisions show dramatically higher engagement than routine ones
+- bankme token dropped 55% in 45 minutes — contrast with MetaDAO ecosystem where no ICO has gone below launch price
+
+### Jupiter Governance Comparison
+- Jupiter governance proposal: 303 views, 2 comments
+- MetaDAO futarchy equivalent: $40K volume, 122 trades
+- The engagement differential is stark — markets produce real participation where forums produce silence
+- This is the strongest empirical argument for futarchy over token voting
+
+### MetaDAO Q4 2025 Report
+- Comprehensive quarterly metrics (already archived separately)
+- 8 ICOs, $25.6M raised, $390M committed
+- $300M AMM volume, $1.5M in fees
+- 95% refund rate from oversubscription — capital efficiency metric
+
+### Futardio Launch Metrics
+- Already partially archived separately
+- Additional data: participation demographics, wallet analysis, time-to-fill curves
+- First permissionless raise performance compared to curated MetaDAO ICOs
+
+## Noise Filtered Out
+- Mostly retweets and community engagement
+- Original content is almost exclusively data-driven — very little opinion

inbox/archive/2026-03-09-rambo-xbt-x-archive.md

@@ -0,0 +1,36 @@
+---
+type: source
+title: "@rambo_xbt X archive — 100 most recent tweets"
+author: "Rambo (@rambo_xbt)"
+url: https://x.com/rambo_xbt
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [wider-ecosystem, trading, market-sentiment]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Trader/market commentator. Only 1 MetaDAO reference — most peripheral account in the
+  network. 57% substantive (lowest among individual accounts). "Loading before the noise"
+  bio suggests contrarian positioning. Content is primarily trading signals and market
+  sentiment — no mechanism design content. Null-result candidate.
+extraction_hints:
+  - "Null-result expected — peripheral to MetaDAO ecosystem, trading signals only"
+priority: low
+---
+
+# @rambo_xbt X Archive (March 2026)
+
+## Substantive Tweets
+
+### Trading Commentary
+- Market sentiment analysis
+- ORGO agent desktop positioning
+- Iran geopolitical discussion
+
+### MetaDAO Connection
+- 1 reference — most peripheral account in network
+- Identified via engagement analysis but minimal substantive overlap
+
+## Noise Filtered Out
+- 43% noise — casual engagement, memes

inbox/archive/2026-03-09-ranger-finance-x-archive.md

@@ -0,0 +1,50 @@
+---
+type: source
+title: "@ranger_finance X archive — 100 most recent tweets"
+author: "Ranger (@ranger_finance)"
+url: https://x.com/ranger_finance
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [ranger, metadao-ecosystem, vaults, yield, liquidation, governance]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Ranger is the MetaDAO ecosystem's most consequential governance case study — the first
+  project to face futarchy-enforced liquidation. Their pivot from perps/spot trading to
+  pure vault strategy happened under futarchy oversight. Key data: $1.13M+ paid to
+  depositors all-time, $17.7K weekly payouts across 9 vaults. Build-A-Bear hackathon
+  offering $1M seed funding. The liquidation event ($5M USDC returned) is already
+  well-documented in other archives — Ranger's own account shows the project perspective
+  on being governed by markets.
+extraction_hints:
+  - "Ranger's strategic pivot (perps → vaults) under futarchy governance — evidence for how market oversight shapes project strategy"
+  - "Vault payout data ($1.13M all-time) — concrete DeFi performance metrics"
+  - "Build-A-Bear hackathon ($1M seed) — capital allocation through ecosystem development"
+  - "Enrichment target: 'futarchy-governed liquidation is the enforcement mechanism' — Ranger is THE case study"
+  - "Potential new claim: futarchy governance forces strategic focus by making underperformance visible and actionable"
+priority: medium
+---
+
+# @ranger_finance X Archive (March 2026)
+
+## Substantive Tweets
+
+### Strategic Pivot Under Governance Pressure
+- Shifted focus from perps/spot trading to exclusively vault-based yield strategy
+- Decision driven partly by market signals — futarchy governance made underperformance in trading visible
+- Ranger Earn: 9 active vaults, $17.7K weekly depositor payouts, $1.13M+ all-time
+
+### Build-A-Bear Hackathon
+- $1M seed funding in prizes — significant capital allocation to ecosystem development
+- Helius sponsorship (1 month free Dev Plan per participant)
+- Strategy: drive TVL growth through developer community building
+
+### Liquidation Context
+- Ranger faced futarchy-governed liquidation proposal — first enforcement event in MetaDAO
+- $5M USDC distributed back to token holders
+- Project perspective: acceptance of market verdict, pivot to sustainable model
+
+## Noise Filtered Out
+- 32% noise — promotional content, community engagement, event reminders
+- Lowest substantive ratio among builder tier accounts

inbox/archive/2026-03-09-richard-isc-x-archive.md

@@ -0,0 +1,49 @@
+---
+type: source
+title: "@Richard_ISC X archive — 100 most recent tweets"
+author: "Richard (@Richard_ISC), co-founder ISC"
+url: https://x.com/Richard_ISC
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [isc, governance, futarchy, mechanism-design, metadao-ecosystem, defi]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Highest substantive ratio in the builder tier (95%). Richard is a philosophical
+  contributor to the MetaDAO ecosystem — his tweets engage with mechanism design theory,
+  not just product announcements. Key signal: critiques of governance token liquidity vs
+  traditional equity, commentary on overraising in crypto as a mechanism design flaw,
+  and evaluation of ecosystem projects (Ranger, Hurupay). This is the kind of voice
+  that produces extractable claims because he argues positions rather than just
+  announcing products.
+extraction_hints:
+  - "Critique of overraising as mechanism design flaw — potential new claim about capital formation incentive misalignment"
+  - "Governance token liquidity vs equity comparison — data point for ownership coin thesis"
+  - "Ecosystem project evaluations — Richard's assessments provide practitioner perspective on futarchy outcomes"
+  - "Connection: his criticism of overraising maps to our 'early-conviction pricing is an unsolved mechanism design problem' claim"
+priority: medium
+---
+
+# @Richard_ISC X Archive (March 2026)
+
+## Substantive Tweets
+
+### Mechanism Design Theory
+- Strong engagement with futarchy/governance mechanism design
+- Critiques overraising in crypto: mechanism design flaw where incentives reward raising maximum capital rather than optimal capital
+- Commentary on governance token liquidity — liquid governance tokens create different dynamics than traditional illiquid equity
+- Advocates MetaDAO model over traditional corporate structures for crypto-native organizations
+
+### Ecosystem Project Evaluation
+- Evaluates Ranger, Hurupay, and other MetaDAO ecosystem projects
+- Practitioner perspective: what does futarchy governance look like from the inside?
+- Assessment of which projects demonstrate genuine mechanism design alignment vs cargo-culting
+
+### ISC (Internet Securities Commission?) Context
+- Co-founder of ISC — unclear exact positioning but governance/compliance focused
+- "Rational thinker" self-description matches content: measured analysis, not hype
+
+## Noise Filtered Out
+- Only 5% noise — extremely high signal account
+- Almost every tweet engages substantively with a mechanism or evaluation

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

@@ -0,0 +1,38 @@
+---
+type: source
+title: "@rocketresearchx X archive — 100 most recent tweets"
+author: "Team Rocket Research (@rocketresearchx)"
+url: https://x.com/rocketresearchx
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [media, research, trading, market-analysis, solana]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  OG crypto research outfit (Bitcoin since 2011). 94% substantive ratio but content is
+  primarily trading/technical analysis and market commentary rather than mechanism design.
+  Only 2 MetaDAO references. Market cap analysis ($15M vs $100M valuations), technical
+  indicators (EMA 8 rejection), geopolitical risk assessment. Useful for broader crypto
+  market context but not a source of mechanism design claims.
+extraction_hints:
+  - "Market structure commentary — broader context for crypto capital formation"
+  - "Null-result likely for MetaDAO-specific claims"
+priority: low
+---
+
+# @rocketresearchx X Archive (March 2026)
+
+## Substantive Tweets
+
+### Market Analysis
+- Technical analysis: EMA 8 rejection on weekly, market cap comparisons
+- Geopolitical risk assessment (Iran events, Bloomberg coverage)
+- 94% substantive but all trading-focused
+
+### MetaDAO Connection
+- 2 references — peripheral to ecosystem
+- Research perspective rather than builder perspective
+
+## Noise Filtered Out
+- 6% noise — highly substantive but wrong domain for claim extraction

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

@@ -0,0 +1,81 @@
+---
+type: source
+title: "@simonw X archive — 100 most recent tweets"
+author: "Simon Willison (@simonw)"
+url: https://x.com/simonw
+date: 2026-03-09
+domain: ai-alignment
+format: tweet
+status: processed
+processed_by: theseus
+processed_date: 2026-03-09
+claims_extracted:
+  - "agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced on their behalf"
+  - "coding agents cannot take accountability for mistakes which means humans must retain decision authority over security and critical systems regardless of agent capability"
+enrichments: []
+tags: [agentic-engineering, cognitive-debt, security, accountability, coding-agents, open-source-licensing]
+linked_set: theseus-x-collab-taxonomy-2026-03
+curator_notes: |
+  25 relevant tweets out of 60 unique. Willison is writing a systematic "Agentic Engineering
+  Patterns" guide and tweeting chapter releases. The strongest contributions are conceptual
+  frameworks: cognitive debt, the accountability gap, and agents-as-mixed-ability-teams.
+  He is the most careful about AI safety/governance in this batch — strong anti-anthropomorphism
+  position, prompt injection as LLM-specific vulnerability, and alarm about agents
+  circumventing open source licensing. Zero hype, all substance — consistent with his
+  reputation.
+---
+
+# @simonw X Archive (Feb 26 – Mar 9, 2026)
+
+## Key Tweets by Theme
+
+### Agentic Engineering Patterns (Guide Chapters)
+
+- **Cognitive debt** (status/2027885000432259567, 1,261 likes): "New chapter of my Agentic Engineering Patterns guide. This one is about having coding agents build custom interactive and animated explanations to help fight back against cognitive debt."
+
+- **Anti-pattern: unreviewed code on collaborators** (status/2029260505324412954, 761 likes): "I started a new chapter of my Agentic Engineering Patterns guide about anti-patterns [...] Inflicting unreviewed code on collaborators, aka dumping a thousand line PR without even making sure it works first."
+
+- **Hoard things you know how to do** (status/2027130136987086905, 814 likes): "Today's chapter of Agentic Engineering Patterns is some good general career advice which happens to also help when working with coding agents: Hoard things you know how to do."
+
+- **Agentic manual testing** (status/2029962824731275718, 371 likes): "New chapter: Agentic manual testing - about how having agents 'manually' try out code is a useful way to help them spot issues that might not have been caught by their automated tests."
+
+### Security as the Critical Lens
+
+- **Security teams are the experts we need** (status/2028838538825924803, 698 likes): "The people I want to hear from right now are the security teams at large companies who have to try and keep systems secure when dozens of teams of engineers of varying levels of experience are constantly shipping new features."
+
+- **Security is the most interesting lens** (status/2028840346617065573, 70 likes): "I feel like security is the most interesting lens to look at this from. Most bad code problems are survivable [...] Security problems are much more directly harmful to the organization."
+
+- **Accountability gap** (status/2028841504601444397, 84 likes): "Coding agents can't take accountability for their mistakes. Eventually you want someone who's job is on the line to be making decisions about things as important as securing the system."
+
+- **Agents as mixed-ability engineering teams** (status/2028838854057226246, 99 likes): "Shipping code of varying quality and varying levels of review isn't a new problem [...] At this point maybe we treat coding agents like teams of mixed ability engineers working under aggressive deadlines."
+
+- **Tests offset lower code quality** (status/2028846376952492054, 1 like): "agents make test coverage so much cheaper that I'm willing to tolerate lower quality code from them as long as it's properly tested. Tests don't solve security though!"
+
+### AI Safety / Governance
+
+- **Prompt injection is LLM-specific** (status/2030806416907448444, 3 likes): "No, it's an LLM problem - LLMs provide attackers with a human language interface that they can use to trick the model into making tool calls that act against the interests of their users. Most software doesn't have that."
+
+- **Nobody knows how to build safe digital assistants** (status/2029539116166095019, 2 likes): "I don't use it myself because I don't know how to use it safely. [...] The challenge now is to figure out how to deliver one that's safe by default. No one knows how to do that yet."
+
+- **Anti-anthropomorphism** (status/2027128593839722833, 4 likes): "Not using language like 'Opus 3 enthusiastically agreed' in a tweet seen by a million people would be good."
+
+- **LLMs have zero moral status** (status/2027127449583292625, 32 likes): "I can run these things in my laptop. They're a big stack of matrix arithmetic that is reset back to zero every time I start a new prompt. I do not think they warrant any moral consideration at all."
+
+### Open Source Licensing Disruption
+
+- **Agents as reverse engineering machines** (status/2029729939285504262, 39 likes): "It breaks pretty much ALL licenses, even commercial software. These coding agents are reverse engineering / clean room implementing machines."
+
+- **chardet clean-room rewrite controversy** (status/2029600918912553111, 308 likes): "The chardet open source library relicensed from LGPL to MIT two days ago thanks to a Claude Code assisted 'clean room' rewrite - but original author Mark Pilgrim is disputing that the way this was done justifies the change in license."
+
+- **Threats to open source** (status/2029958835130225081, 2 likes): "This is one of the 'threats to open source' I find most credible - we've built the entire community on decades of licensing which can now be subverted by a coding agent running for a few hours."
+
+### Capability Observations
+
+- **Qwen 3.5 4B vs GPT-4o** (status/2030067107371831757, 565 likes): "Qwen3.5 4B apparently out-scores GPT-4o on some of the classic benchmarks (!)"
+
+- **Benchmark gaming suspicion** (status/2030139125656080876, 68 likes): "Given the enormous size difference in terms of parameters this does make me suspicious that Qwen may have been training to the test on some of these."
+
+- **AI hiring criteria** (status/2030974722029339082, 5 likes): Polling whether AI coding tool experience features in developer interviews.
+
+## Filtered Out
+~35 tweets: art museum visit, Google account bans, Qwen team resignations (news relay), chardet licensing details, casual replies.

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

@@ -0,0 +1,41 @@
+---
+type: source
+title: "@SolanaFloor X archive — 100 most recent tweets"
+author: "SolanaFloor (@SolanaFloor)"
+url: https://x.com/SolanaFloor
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [media, solana-news, ecosystem, governance]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Solana's #1 news source (128K followers). Only 1 MetaDAO reference in recent tweets.
+  Notable event: SolanaFloor announced shutdown (effective immediately) — major Solana
+  media outlet going dark. Also covered Jupiter DAO vote (75% support for Net Zero
+  Emissions proposal). Useful as broader context for Solana ecosystem health and media
+  landscape but minimal MetaDAO-specific content. The shutdown itself is culturally
+  significant — ecosystem media consolidation.
+extraction_hints:
+  - "SolanaFloor shutdown — ecosystem media consolidation signal"
+  - "Jupiter DAO vote data (75% support) — comparative governance data vs MetaDAO futarchy"
+  - "Null-result for MetaDAO claims — peripheral ecosystem coverage"
+priority: low
+---
+
+# @SolanaFloor X Archive (March 2026)
+
+## Substantive Tweets
+
+### Solana Ecosystem News
+- Broad Solana ecosystem coverage — project launches, market events, governance
+- Jupiter DAO vote: 75% support for Net Zero Emissions proposal
+- $441K accidental memecoin transfer story — market incident
+
+### Shutdown Announcement
+- SolanaFloor shutting down effective immediately
+- Major Solana media outlet going dark — ecosystem media consolidation
+
+## Noise Filtered Out
+- 14% noise — mostly ecosystem news aggregation
+- High volume, low MetaDAO relevance

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

@@ -0,0 +1,33 @@
+---
+type: source
+title: "@_spiz_ X archive — 100 most recent tweets"
+author: "SPIZZIE (@_spiz_)"
+url: https://x.com/_spiz_
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [wider-ecosystem, futardio, solana, bear-market]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Ecosystem participant with 1 MetaDAO reference. 48% substantive. Notable for Futardio
+  fundraising market landscape analysis and "bear market building" thesis. Moderate
+  ecosystem coordination emphasis. Low claim extraction priority.
+extraction_hints:
+  - "Futardio fundraising market landscape analysis — if original, could provide market structure data"
+  - "Bear market building thesis — cultural data point"
+  - "Low priority — tangential ecosystem voice"
+priority: low
+---
+
+# @_spiz_ X Archive (March 2026)
+
+## Substantive Tweets
+
+### Market Commentary
+- Futardio fundraising market landscape analysis
+- Bear market building thesis
+- Ecosystem coordination emphasis
+
+## Noise Filtered Out
+- 52% noise — casual engagement

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

@@ -0,0 +1,81 @@
+---
+type: source
+title: "@swyx X archive — 100 most recent tweets"
+author: "Shawn Wang (@swyx), Latent.Space / AI Engineer"
+url: https://x.com/swyx
+date: 2026-03-09
+domain: ai-alignment
+format: tweet
+status: processed
+processed_by: theseus
+processed_date: 2026-03-09
+claims_extracted:
+  - "subagent hierarchies outperform peer multi-agent architectures in practice because deployed systems consistently converge on one primary agent controlling specialized helpers"
+enrichments: []
+tags: [agent-architectures, subagent, harness-engineering, coding-agents, ai-engineering]
+linked_set: theseus-x-collab-taxonomy-2026-03
+curator_notes: |
+  26 relevant tweets out of 100 unique. swyx is documenting the AI engineering paradigm
+  shift from the practitioner/conference-organizer perspective. Strongest signal: the
+  "Year of the Subagent" thesis — hierarchical agent control beats peer multi-agent.
+  Also strong: harness engineering (Devin's dozens of model groups with periodic rewrites),
+  OpenAI Symphony/Frontier (1,500 PRs with zero manual coding), and context management
+  as the critical unsolved problem. Good complement to Karpathy's researcher perspective.
+---
+
+# @swyx X Archive (Mar 5 – Mar 9, 2026)
+
+## Key Tweets by Theme
+
+### Subagent Architecture Thesis
+
+- **Year of the Subagent** (status/2029980059063439406, 172 likes): "Another realization I only voiced in this pod: **This is the year of the Subagent** — every practical multiagent problem is a subagent problem — agents are being RLed to control other agents (Cursor, Kimi, Claude, Cognition) — subagents can have resources and contracts defined by you [...] multiagents cannot — massive parallelism is coming [...] Tldr @walden_yan was right, dont build multiagents"
+
+- **Multi-agent = one main agent with helpers** (status/2030009364237668738, 13 likes): Quoting: "Interesting take. Feels like most 'multi-agent' setups end up becoming one main agent with a bunch of helpers anyway... so calling them subagents might just be the more honest framing."
+
+### Harness Engineering & Agent Infrastructure
+
+- **Devin's model rotation pattern** (status/2030853776136139109, 96 likes): "'Build a company that benefits from the models getting better and better' — @sama. devin brain uses a couple dozen modelgroups and extensively evals every model for inclusion in the harness, doing a complete rewrite every few months. [...] agents are really, really working now and you had to have scaled harness eng + GTM to prep for this moment"
+
+- **OpenAI Frontier/Symphony** (status/2030074312380817457, 379 likes): "we just recorded what might be the single most impactful conversation in the history of @latentspacepod [...] everything about @OpenAI Frontier, Symphony and Harness Engineering. its all of a kind and the future of the AI Native Org" — quoting: "Shipping software with Codex without touching code. Here's how a small team steering Codex opened and merged 1,500 pull requests."
+
+- **Agent skill granularity** (status/2030393749201969520, 1 like): "no definitive answer yet but 1 is definitely wrong. see also @_lopopolo's symphony for level of detail u should leave in a skill (basically break them up into little pieces)"
+
+- **Rebuild everything every few months** (status/2030876666973884510, 3 likes): "the smart way is to rebuild everything every few months"
+
+### AI Coding Tool Friction
+
+- **Context compaction problems** (status/2029659046605901995, 244 likes): "also got extremely mad at too many bad claude code compactions so opensourcing this tool for myself for deeply understanding wtf is still bad about claude compactions."
+
+- **Context loss during sessions** (status/2029673032491618575, 3 likes): "horrible. completely lost context on last 30 mins of work"
+
+- **Can't function without Cowork** (status/2029616716440011046, 117 likes): "ok are there any open source Claude Cowork clones because I can no longer function without a cowork."
+
+### Capability Observations
+
+- **SWE-Bench critique** (status/2029688456650297573, 113 likes): "the @OfirPress literal swebench author doesnt endorse this cheap sample benchmark and you need to run about 30-60x compute that margin labs is doing to get even close to statistically meaningful results"
+
+- **100B tokens in one week will be normal** (status/2030093534305604055, 18 likes): "what is psychopathical today will be the norm in 5 years" — quoting: "some psychopath on the internal codex leaderboard hit 100B tokens in the last week"
+
+- **Opus 4.6 is not AGI** (status/2030937404606214592, 2 likes): "that said opus 4.6 is definitely not agi lmao"
+
+- **Lab leaks meme** (status/2030876433976119782, 201 likes): "4.5  5.4  3.1 🤝 lab leaks" — AI capabilities spreading faster than society realizes.
+
+- **Codex at 2M+ users** (status/2029680408489775488, 3 likes): "+400k in the last 2 weeks lmao"
+
+### Human-AI Workflow Shifts
+
+- **Cursor as operating system** (status/2030009364237668738, 13 likes): "btw i am very proudly still a Cursor DAU [...] its gotten to the point that @cursor is just my operating system for AIE and i just paste in what needs to happen."
+
+- **Better sysprompt → better planning → better execution** (status/2029640548500603180, 3 likes): Causal chain in AI engineering: system prompt quality drives planning quality drives execution quality.
+
+- **Future of git for agents** (status/2029702342342496328, 33 likes): Questioning whether git is the right paradigm for agent-generated code where "code gets discarded often bc its cheap."
+
+- **NVIDIA agent inference** (status/2030770055047492007, 80 likes): Agent inference becoming a major infrastructure category distinct from training.
+
+### AI Governance Signal
+
+- **LLM impersonating humans** (status/2029741031609286820, 28 likes): "bartosz v sorry to inform you the thing you replied to is an LLM (see his bio, at least this one is honest)" — autonomous AI on social media.
+
+## Filtered Out
+~74 tweets: casual replies, conference logistics, emoji reactions, link shares without commentary.

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

@@ -0,0 +1,77 @@
+---
+type: source
+title: "@TheiaResearch X archive — 100 most recent tweets"
+author: "Felipe Montealegre (@TheiaResearch), Theia Research"
+url: https://x.com/TheiaResearch
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: processed
+processed_by: rio
+processed_date: 2026-03-09
+claims_extracted:
+  - "time-based token vesting is hedgeable making standard lockups meaningless as alignment mechanisms because investors can short-sell to neutralize lockup exposure while appearing locked"
+tags: [internet-finance, theia, ownership-tokens, token-problem, capital-formation, metadao]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  The most important external voice in the MetaDAO ecosystem. Felipe's entire fund thesis
+  is "Internet Financial System" — directly overlapping with our domain territory. ~38
+  substantive tweets. His register is thesis-driven fundamentals analysis, zero memes. He
+  coined "ownership tokens" vs "futility tokens" and his framing heavily influences how
+  the ecosystem talks about itself. Key signal: he's presenting "The Token Problem and
+  Proposed Solutions" at Blockworks DAS NYC on March 25 — this will be the highest-profile
+  articulation of the ownership coin thesis yet. His investment framework ("everything is
+  DCF") maps cleanly to our teleological economics lens.
+extraction_hints:
+  - "ZIPP (Zero Illiquidity Premium Period) — thesis that token illiquidity premiums are ending, which changes valuation frameworks for all crypto"
+  - "Token Problem: time-based vesting is hedgeable, making lockups meaningless — this is a mechanism design claim we don't have"
+  - "Internet Financial System thesis — check against our existing 'internet finance generates 50-100 bps additional GDP growth' claim"
+  - "AI displacement creates crypto opportunity — parallel to Theseus's AI labor displacement claims, potential cross-domain connection"
+  - "MetaDAO + Futardio as capital formation innovation — enriches existing MetaDAO claims"
+  - "Enrichment target: 'cryptos primary use case is capital formation not payments' — Felipe's framing directly supports this"
+  - "DAS keynote 'The Token Problem' — upcoming source to track for extraction"
+  - "Connection to Aschenbrenner pattern: Felipe publishing thesis openly before/while raising capital, same playbook as Situational Awareness"
+priority: high
+---
+
+# @TheiaResearch X Archive (March 2026)
+
+## Substantive Tweets
+
+### Internet Financial System Thesis
+- "Everything is DCF" — core analytical framework, applies traditional valuation to crypto assets
+- Internet Financial System (IFS) as the macro frame: crypto is rebuilding finance natively on the internet
+- Token markets have a structural problem: most tokens are "futility tokens" with no real economic/governance/legal rights
+- "Ownership tokens" solve this by attaching real rights to token holders — MetaDAO's implementation is the leading example
+
+### The Token Problem (DAS NYC Keynote Preview)
+- Presenting "The Token Problem and Proposed Solutions" at Blockworks DAS NYC, March 25
+- Core argument: time-based vesting is hedgeable — investors can short-sell to neutralize lockups, making standard vesting meaningless
+- This means standard token launches provide no real alignment between teams and investors
+- Ownership coins with futarchy governance solve this because you can't hedge away governance rights that are actively pricing your decisions
+
+### ZIPP — Zero Illiquidity Premium Period
+- Thesis that the era of illiquidity premiums in crypto is ending
+- As markets mature, the premium paid for illiquid assets disappears
+- Implications for token valuation: tokens should be priced on fundamentals (DCF), not on scarcity/lockup dynamics
+- This is a structural shift in how crypto assets are valued
+
+### MetaDAO / Futardio as Capital Formation Innovation
+- "$9.9M from 6MV/Variant/Paradigm to MetaDAO at spot" — institutional validation
+- Futardio permissionless launches as the scalable version of MetaDAO ICOs
+- First Futardio raise massively oversubscribed — proving permissionless demand
+- Framing: MetaDAO solved the quality problem (unruggable), Futardio solves the scale problem (permissionless)
+
+### AI + Crypto Convergence
+- AI displacement creates opportunity for crypto: as AI replaces knowledge workers, permissionless capital formation becomes more important
+- AI agents will need financial infrastructure — crypto is the only permissionless option
+- Connection to broader macro thesis: AI deflation + crypto capital formation = new economic paradigm
+
+### Bitcoin / Macro Commentary
+- Bitcoin's core improvement over gold: portability and confiscation resistance
+- These properties matter most in crisis situations (Iran, Egypt, Argentina)
+- Stablecoin adoption as leading indicator of crypto utility
+
+## Noise Filtered Out
+- ~62 tweets were RTs (many promoting Theia portfolio companies), casual engagement, event promotion
+- High RT-to-original ratio — Felipe amplifies ecosystem voices more than he originates

inbox/archive/2026-03-09-turbine-cash-x-archive.md

@@ -0,0 +1,49 @@
+---
+type: source
+title: "@turbine_cash X archive — 100 most recent tweets"
+author: "Turbine Cash (@turbine_cash)"
+url: https://x.com/turbine_cash
+date: 2026-03-09
+domain: internet-finance
+format: tweet
+status: unprocessed
+tags: [turbine, privacy, privacyfi, futardio, solana, metadao-ecosystem]
+linked_set: metadao-x-landscape-2026-03
+curator_notes: |
+  Privacy infrastructure on Solana — first project to successfully raise via Futardio's
+  on-chain auction. This makes Turbine the proof-of-concept for permissionless ownership
+  coin launches. "Leading the PrivacyFi revolution" — positioning privacy as a DeFi
+  primitive rather than a standalone feature. Private DCA is the initial product.
+  Connection to 01Resolved's analysis of Turbine buyback TWAP threshold filtering
+  provides a mechanism design data point.
+extraction_hints:
+  - "First successful Futardio raise — evidence for permissionless launch viability"
+  - "Privacy as DeFi primitive (PrivacyFi) — potential new claim about privacy infrastructure in internet finance"
+  - "TWAP buyback mechanics — connects to 01Resolved's analysis, evidence for automated treasury management"
+  - "Cross-domain flag for Theseus: privacy infrastructure intersects with AI alignment (encrypted computation, data sovereignty)"
+priority: low
+---
+
+# @turbine_cash X Archive (March 2026)
+
+## Substantive Tweets
+
+### First Futardio Raise
+- Successfully raised capital through Futardio's permissionless on-chain auction
+- First proof-of-concept for the permissionless ownership coin launch model
+- Demonstrates that projects outside MetaDAO's curated pipeline can raise effectively
+
+### PrivacyFi Positioning
+- Privacy as infrastructure primitive, not standalone product
+- Private DCA (dollar-cost averaging) as initial product
+- "Accelerating privacy" via protocol design on Solana
+- Integration with Soladex discovery platform
+
+### Buyback Mechanics
+- Automated TWAP threshold-based buybacks for treasury management
+- Price signal-driven: buybacks trigger at specific thresholds
+- Connects to broader ownership coin treasury management patterns
+
+## Noise Filtered Out
+- ~16% noise — mostly community engagement and promotional content
+- Relatively high signal for a project account

ops/evaluate-trigger.sh

@@ -1,15 +1,21 @@
 #!/usr/bin/env bash
-# evaluate-trigger.sh — Find unreviewed PRs and run 2-agent review on each.
+# evaluate-trigger.sh — Find unreviewed PRs, run 2-agent review, auto-merge if approved.
 #
 # Reviews each PR with TWO agents:
 #   1. Leo (evaluator) — quality gates, cross-domain connections, coherence
 #   2. Domain agent — domain expertise, duplicate check, technical accuracy
 #
+# After both reviews, auto-merges if:
+#   - Leo's comment contains "**Verdict:** approve"
+#   - Domain agent's comment contains "**Verdict:** approve"
+#   - No territory violations (files outside proposer's domain)
+#
 # Usage:
-#   ./ops/evaluate-trigger.sh              # review all unreviewed open PRs
+#   ./ops/evaluate-trigger.sh              # review + auto-merge approved PRs
 #   ./ops/evaluate-trigger.sh 47           # review a specific PR by number
 #   ./ops/evaluate-trigger.sh --dry-run    # show what would be reviewed, don't run
 #   ./ops/evaluate-trigger.sh --leo-only   # skip domain agent, just run Leo
+#   ./ops/evaluate-trigger.sh --no-merge   # review only, don't auto-merge (old behavior)
 #
 # Requirements:
 #   - claude CLI (claude -p for headless mode)
@@ -18,10 +24,16 @@
 #
 # Safety:
 #   - Lockfile prevents concurrent runs
-#   - Neither agent auto-merges — reviews only
+#   - Auto-merge requires ALL reviewers to approve + no territory violations
 #   - Each PR runs sequentially to avoid branch conflicts
-#   - Timeout: 10 minutes per agent per PR
+#   - Timeout: 20 minutes per agent per PR
 #   - Pre-flight checks: clean working tree, gh auth
+#
+# Verdict protocol:
+#   All agents use `gh pr comment` (NOT `gh pr review`) because all agents
+#   share the m3taversal GitHub account — `gh pr review --approve` fails
+#   when the PR author and reviewer are the same user. The merge check
+#   parses issue comments for structured verdict markers instead.
 
 set -euo pipefail
 
@@ -33,9 +45,10 @@ cd "$REPO_ROOT"
 
 LOCKFILE="/tmp/evaluate-trigger.lock"
 LOG_DIR="$REPO_ROOT/ops/sessions"
-TIMEOUT_SECONDS=600
+TIMEOUT_SECONDS=1200
 DRY_RUN=false
 LEO_ONLY=false
+NO_MERGE=false
 SPECIFIC_PR=""
 
 # --- Domain routing map ---
@@ -53,23 +66,32 @@ detect_domain_agent() {
     clay/*|*/entertainment*)   agent="clay"; domain="entertainment" ;;
     theseus/*|logos/*|*/ai-alignment*) agent="theseus"; domain="ai-alignment" ;;
     vida/*|*/health*)          agent="vida"; domain="health" ;;
+    astra/*|*/space-development*) agent="astra"; domain="space-development" ;;
     leo/*|*/grand-strategy*)   agent="leo"; domain="grand-strategy" ;;
+    contrib/*)
+      # External contributor — detect domain from changed files (fall through to file check)
+      agent=""; domain=""
+      ;;
     *)
-      # Fall back to checking which domain directory has changed files
-      if echo "$files" | grep -q "domains/internet-finance/"; then
-        agent="rio"; domain="internet-finance"
-      elif echo "$files" | grep -q "domains/entertainment/"; then
-        agent="clay"; domain="entertainment"
-      elif echo "$files" | grep -q "domains/ai-alignment/"; then
-        agent="theseus"; domain="ai-alignment"
-      elif echo "$files" | grep -q "domains/health/"; then
-        agent="vida"; domain="health"
-      else
-        agent=""; domain=""
-      fi
+      agent=""; domain=""
       ;;
   esac
 
+  # If no agent detected from branch prefix, check changed files
+  if [ -z "$agent" ]; then
+    if echo "$files" | grep -q "domains/internet-finance/"; then
+      agent="rio"; domain="internet-finance"
+    elif echo "$files" | grep -q "domains/entertainment/"; then
+      agent="clay"; domain="entertainment"
+    elif echo "$files" | grep -q "domains/ai-alignment/"; then
+      agent="theseus"; domain="ai-alignment"
+    elif echo "$files" | grep -q "domains/health/"; then
+      agent="vida"; domain="health"
+    elif echo "$files" | grep -q "domains/space-development/"; then
+      agent="astra"; domain="space-development"
+    fi
+  fi
+
   echo "$agent $domain"
 }
 
@@ -78,6 +100,7 @@ for arg in "$@"; do
   case "$arg" in
     --dry-run) DRY_RUN=true ;;
     --leo-only) LEO_ONLY=true ;;
+    --no-merge) NO_MERGE=true ;;
     [0-9]*) SPECIFIC_PR="$arg" ;;
     --help|-h)
       head -23 "$0" | tail -21
@@ -101,8 +124,8 @@ if ! command -v claude >/dev/null 2>&1; then
   exit 1
 fi
 
-# Check for dirty working tree (ignore ops/ and .claude/ which may contain uncommitted scripts)
-DIRTY_FILES=$(git status --porcelain | grep -v '^?? ops/' | grep -v '^ M ops/' | grep -v '^?? \.claude/' | grep -v '^ M \.claude/' || true)
+# Check for dirty working tree (ignore ops/, .claude/, .github/ which may contain local-only files)
+DIRTY_FILES=$(git status --porcelain | grep -v '^?? ops/' | grep -v '^ M ops/' | grep -v '^?? \.claude/' | grep -v '^ M \.claude/' | grep -v '^?? \.github/' | grep -v '^ M \.github/' || true)
 if [ -n "$DIRTY_FILES" ]; then
   echo "ERROR: Working tree is dirty. Clean up before running."
   echo "$DIRTY_FILES"
@@ -134,7 +157,8 @@ if [ -n "$SPECIFIC_PR" ]; then
   fi
   PRS_TO_REVIEW="$SPECIFIC_PR"
 else
-  OPEN_PRS=$(gh pr list --state open --json number --jq '.[].number' 2>/dev/null || echo "")
+  # NOTE: gh pr list silently returns empty in some worktree configs; use gh api instead
+  OPEN_PRS=$(gh api repos/:owner/:repo/pulls --jq '.[].number' 2>/dev/null || echo "")
 
   if [ -z "$OPEN_PRS" ]; then
     echo "No open PRs found. Nothing to review."
@@ -143,17 +167,23 @@ else
 
   PRS_TO_REVIEW=""
   for pr in $OPEN_PRS; do
-    LAST_REVIEW_DATE=$(gh api "repos/{owner}/{repo}/pulls/$pr/reviews" \
-      --jq 'map(select(.state != "DISMISSED")) | sort_by(.submitted_at) | last | .submitted_at' 2>/dev/null || echo "")
+    # Check if this PR already has a Leo verdict comment (avoid re-reviewing)
+    LEO_COMMENTED=$(gh pr view "$pr" --json comments \
+      --jq '[.comments[] | select(.body | test("VERDICT:LEO:(APPROVE|REQUEST_CHANGES)"))] | length' 2>/dev/null || echo "0")
     LAST_COMMIT_DATE=$(gh pr view "$pr" --json commits --jq '.commits[-1].committedDate' 2>/dev/null || echo "")
 
-    if [ -z "$LAST_REVIEW_DATE" ]; then
-      PRS_TO_REVIEW="$PRS_TO_REVIEW $pr"
-    elif [ -n "$LAST_COMMIT_DATE" ] && [[ "$LAST_COMMIT_DATE" > "$LAST_REVIEW_DATE" ]]; then
-      echo "PR #$pr: New commits since last review. Queuing for re-review."
+    if [ "$LEO_COMMENTED" = "0" ]; then
       PRS_TO_REVIEW="$PRS_TO_REVIEW $pr"
     else
-      echo "PR #$pr: No new commits since last review. Skipping."
+      # Check if new commits since last Leo review
+      LAST_LEO_DATE=$(gh pr view "$pr" --json comments \
+        --jq '[.comments[] | select(.body | test("VERDICT:LEO:")) | .createdAt] | last' 2>/dev/null || echo "")
+      if [ -n "$LAST_COMMIT_DATE" ] && [ -n "$LAST_LEO_DATE" ] && [[ "$LAST_COMMIT_DATE" > "$LAST_LEO_DATE" ]]; then
+        echo "PR #$pr: New commits since last review. Queuing for re-review."
+        PRS_TO_REVIEW="$PRS_TO_REVIEW $pr"
+      else
+        echo "PR #$pr: Already reviewed. Skipping."
+      fi
     fi
   done
 
@@ -184,7 +214,7 @@ run_agent_review() {
   log_file="$LOG_DIR/${agent_name}-review-pr${pr}-${timestamp}.log"
   review_file="/tmp/${agent_name}-review-pr${pr}.md"
 
-  echo "  Running ${agent_name}..."
+  echo "  Running ${agent_name} (model: ${model})..."
   echo "  Log: $log_file"
 
   if perl -e "alarm $TIMEOUT_SECONDS; exec @ARGV" claude -p \
@@ -208,8 +238,123 @@ run_agent_review() {
   fi
 }
 
+# --- Territory violation check ---
+# Verifies all changed files are within the proposer's expected territory
+check_territory_violations() {
+  local pr_number="$1"
+  local branch files proposer violations
+
+  branch=$(gh pr view "$pr_number" --json headRefName --jq '.headRefName' 2>/dev/null || echo "")
+  files=$(gh pr view "$pr_number" --json files --jq '.files[].path' 2>/dev/null || echo "")
+
+  # Determine proposer from branch prefix
+  proposer=$(echo "$branch" | cut -d'/' -f1)
+
+  # Map proposer to allowed directories
+  local allowed_domains=""
+  case "$proposer" in
+    rio)     allowed_domains="domains/internet-finance/" ;;
+    clay)    allowed_domains="domains/entertainment/" ;;
+    theseus) allowed_domains="domains/ai-alignment/" ;;
+    vida)    allowed_domains="domains/health/" ;;
+    astra)   allowed_domains="domains/space-development/" ;;
+    leo)     allowed_domains="core/|foundations/" ;;
+    contrib) echo ""; return 0 ;;  # External contributors — skip territory check
+    *)       echo ""; return 0 ;;  # Unknown proposer — skip check
+  esac
+
+  # Check each file — allow inbox/archive/, agents/{proposer}/, schemas/, foundations/, and the agent's domain
+  violations=""
+  while IFS= read -r file; do
+    [ -z "$file" ] && continue
+    # Always allowed: inbox/archive, own agent dir, maps/, foundations/ (any agent can propose foundation claims)
+    if echo "$file" | grep -qE "^inbox/archive/|^agents/${proposer}/|^maps/|^foundations/"; then
+      continue
+    fi
+    # Check against allowed domain directories
+    if echo "$file" | grep -qE "^${allowed_domains}"; then
+      continue
+    fi
+    violations="${violations}  - ${file}\n"
+  done <<< "$files"
+
+  if [ -n "$violations" ]; then
+    echo -e "$violations"
+  else
+    echo ""
+  fi
+}
+
+# --- Auto-merge check ---
+# Parses issue comments for structured verdict markers.
+# Verdict protocol: agents post `<!-- VERDICT:AGENT_KEY:APPROVE -->` or
+# `<!-- VERDICT:AGENT_KEY:REQUEST_CHANGES -->` as HTML comments in their review.
+# This is machine-parseable and invisible in the rendered comment.
+check_merge_eligible() {
+  local pr_number="$1"
+  local domain_agent="$2"
+  local leo_passed="$3"
+
+  # Gate 1: Leo must have completed without timeout/error
+  if [ "$leo_passed" != "true" ]; then
+    echo "BLOCK: Leo review failed or timed out"
+    return 1
+  fi
+
+  # Gate 2: Check Leo's verdict from issue comments
+  local leo_verdict
+  leo_verdict=$(gh pr view "$pr_number" --json comments \
+    --jq '[.comments[] | select(.body | test("VERDICT:LEO:")) | .body] | last' 2>/dev/null || echo "")
+
+  if echo "$leo_verdict" | grep -q "VERDICT:LEO:APPROVE"; then
+    echo "Leo: APPROVED"
+  elif echo "$leo_verdict" | grep -q "VERDICT:LEO:REQUEST_CHANGES"; then
+    echo "BLOCK: Leo requested changes"
+    return 1
+  else
+    echo "BLOCK: Could not find Leo's verdict marker in PR comments"
+    return 1
+  fi
+
+  # Gate 3: Check domain agent verdict (if applicable)
+  if [ -n "$domain_agent" ] && [ "$domain_agent" != "leo" ]; then
+    local domain_key
+    domain_key=$(echo "$domain_agent" | tr '[:lower:]' '[:upper:]')
+    local domain_verdict
+    domain_verdict=$(gh pr view "$pr_number" --json comments \
+      --jq "[.comments[] | select(.body | test(\"VERDICT:${domain_key}:\")) | .body] | last" 2>/dev/null || echo "")
+
+    if echo "$domain_verdict" | grep -q "VERDICT:${domain_key}:APPROVE"; then
+      echo "Domain agent ($domain_agent): APPROVED"
+    elif echo "$domain_verdict" | grep -q "VERDICT:${domain_key}:REQUEST_CHANGES"; then
+      echo "BLOCK: $domain_agent requested changes"
+      return 1
+    else
+      echo "BLOCK: No verdict marker found for $domain_agent"
+      return 1
+    fi
+  else
+    echo "Domain agent: N/A (leo-only or grand-strategy)"
+  fi
+
+  # Gate 4: Territory violations
+  local violations
+  violations=$(check_territory_violations "$pr_number")
+
+  if [ -n "$violations" ]; then
+    echo "BLOCK: Territory violations detected:"
+    echo -e "$violations"
+    return 1
+  else
+    echo "Territory: clean"
+  fi
+
+  return 0
+}
+
 REVIEWED=0
 FAILED=0
+MERGED=0
 
 for pr in $PRS_TO_REVIEW; do
   echo ""
@@ -235,7 +380,7 @@ Before evaluating, scan the existing knowledge base for duplicate and contradict
 - Read titles to check for semantic duplicates
 - Check for contradictions with existing claims in that domain and in foundations/
 
-For each proposed claim, evaluate against these 8 quality criteria from CLAUDE.md:
+For each proposed claim, evaluate against these 11 quality criteria from CLAUDE.md:
 1. Specificity — Is this specific enough to disagree with?
 2. Evidence — Is there traceable evidence in the body?
 3. Description quality — Does the description add info beyond the title?
@@ -244,6 +389,9 @@ For each proposed claim, evaluate against these 8 quality criteria from CLAUDE.m
 6. Contradiction check — Does this contradict an existing claim? If so, is the contradiction explicit?
 7. Value add — Does this genuinely expand what the knowledge base knows?
 8. Wiki links — Do all [[links]] point to real files?
+9. Scope qualification — Does the claim specify structural vs functional, micro vs macro, causal vs correlational?
+10. Universal quantifier check — Does the title use unwarranted universals (all, always, never, the only)?
+11. Counter-evidence acknowledgment — For likely or higher: is opposing evidence acknowledged?
 
 Also check:
 - Source archive updated correctly (status field)
@@ -252,12 +400,16 @@ Also check:
 - Cross-domain connections that the proposer may have missed
 
 Write your complete review to ${LEO_REVIEW_FILE}
-Then post it with: gh pr review ${pr} --comment --body-file ${LEO_REVIEW_FILE}
 
-If ALL claims pass quality gates: gh pr review ${pr} --approve --body-file ${LEO_REVIEW_FILE}
-If ANY claim needs changes: gh pr review ${pr} --request-changes --body-file ${LEO_REVIEW_FILE}
+CRITICAL — Verdict format: Your review MUST end with exactly one of these verdict markers (as an HTML comment on its own line):
+  <!-- VERDICT:LEO:APPROVE -->
+  <!-- VERDICT:LEO:REQUEST_CHANGES -->
 
-DO NOT merge. Leave the merge decision to Cory.
+Then post the review as an issue comment:
+  gh pr comment ${pr} --body-file ${LEO_REVIEW_FILE}
+
+IMPORTANT: Use 'gh pr comment' NOT 'gh pr review'. We use a shared GitHub account so gh pr review --approve fails.
+DO NOT merge — the orchestrator handles merge decisions after all reviews are posted.
 Work autonomously. Do not ask for confirmation."
 
   if run_agent_review "$pr" "leo" "$LEO_PROMPT" "opus"; then
@@ -281,6 +433,7 @@ Work autonomously. Do not ask for confirmation."
   else
     DOMAIN_REVIEW_FILE="/tmp/${DOMAIN_AGENT}-review-pr${pr}.md"
     AGENT_NAME_UPPER=$(echo "${DOMAIN_AGENT}" | awk '{print toupper(substr($0,1,1)) substr($0,2)}')
+    AGENT_KEY_UPPER=$(echo "${DOMAIN_AGENT}" | tr '[:lower:]' '[:upper:]')
     DOMAIN_PROMPT="You are ${AGENT_NAME_UPPER}. Read agents/${DOMAIN_AGENT}/identity.md, agents/${DOMAIN_AGENT}/beliefs.md, and skills/evaluate.md.
 
 You are reviewing PR #${pr} as the domain expert for ${DOMAIN}.
@@ -301,11 +454,18 @@ Your review focuses on DOMAIN EXPERTISE — things only a ${DOMAIN} specialist w
 6. **Confidence calibration** — From your domain expertise, is the confidence level right?
 
 Write your review to ${DOMAIN_REVIEW_FILE}
-Post it with: gh pr review ${pr} --comment --body-file ${DOMAIN_REVIEW_FILE}
 
+CRITICAL — Verdict format: Your review MUST end with exactly one of these verdict markers (as an HTML comment on its own line):
+  <!-- VERDICT:${AGENT_KEY_UPPER}:APPROVE -->
+  <!-- VERDICT:${AGENT_KEY_UPPER}:REQUEST_CHANGES -->
+
+Then post the review as an issue comment:
+  gh pr comment ${pr} --body-file ${DOMAIN_REVIEW_FILE}
+
+IMPORTANT: Use 'gh pr comment' NOT 'gh pr review'. We use a shared GitHub account so gh pr review --approve fails.
 Sign your review as ${AGENT_NAME_UPPER} (domain reviewer for ${DOMAIN}).
 DO NOT duplicate Leo's quality gate checks — he covers those.
-DO NOT merge.
+DO NOT merge — the orchestrator handles merge decisions after all reviews are posted.
 Work autonomously. Do not ask for confirmation."
 
     run_agent_review "$pr" "$DOMAIN_AGENT" "$DOMAIN_PROMPT" "sonnet"
@@ -321,6 +481,31 @@ Work autonomously. Do not ask for confirmation."
     FAILED=$((FAILED + 1))
   fi
 
+  # --- Auto-merge decision ---
+  if [ "$NO_MERGE" = true ]; then
+    echo "  Auto-merge: skipped (--no-merge)"
+  elif [ "$LEO_PASSED" != "true" ]; then
+    echo "  Auto-merge: skipped (Leo review failed)"
+  else
+    echo ""
+    echo "  --- Merge eligibility check ---"
+    MERGE_LOG=$(check_merge_eligible "$pr" "$DOMAIN_AGENT" "$LEO_PASSED")
+    MERGE_RESULT=$?
+    echo "$MERGE_LOG" | sed 's/^/    /'
+
+    if [ "$MERGE_RESULT" -eq 0 ]; then
+      echo "  Auto-merge: ALL GATES PASSED — merging PR #$pr"
+      if gh pr merge "$pr" --squash 2>&1; then
+        echo "  PR #$pr: MERGED successfully."
+        MERGED=$((MERGED + 1))
+      else
+        echo "  PR #$pr: Merge FAILED. May need manual intervention."
+      fi
+    else
+      echo "  Auto-merge: BLOCKED — see reasons above"
+    fi
+  fi
+
   echo "Finished: $(date)"
 done
 
@@ -328,4 +513,5 @@ echo ""
 echo "=== Summary ==="
 echo "Reviewed: $REVIEWED"
 echo "Failed: $FAILED"
+echo "Merged: $MERGED"
 echo "Logs: $LOG_DIR"

ops/extract-cron.sh

@@ -0,0 +1,179 @@
+#!/bin/bash
+# Extract claims from unprocessed sources in inbox/archive/
+# Runs via cron on VPS every 15 minutes.
+#
+# Concurrency model:
+#   - Lockfile prevents overlapping runs
+#   - MAX_SOURCES=5 per cycle (works through backlog over multiple runs)
+#   - Sequential processing (one source at a time)
+#   - 50 sources landing at once = ~10 cron cycles to clear, not 50 parallel agents
+#
+# Domain routing:
+#   - Reads domain: field from source frontmatter
+#   - Maps to the domain agent (rio, clay, theseus, vida, astra, leo)
+#   - Runs extraction AS that agent — their territory, their extraction
+#   - Skips sources with status: processing (agent handling it themselves)
+#
+# Flow:
+#   1. Pull latest main
+#   2. Find sources with status: unprocessed (skip processing/processed/null-result)
+#   3. For each: run Claude headless to extract claims as the domain agent
+#   4. Commit extractions, push, open PR
+#   5. Update source status to processed
+#
+# The eval pipeline (webhook.py) handles review and merge separately.
+
+set -euo pipefail
+
+REPO_DIR="/opt/teleo-eval/workspaces/extract"
+REPO_URL="http://m3taversal:$(cat /opt/teleo-eval/secrets/forgejo-admin-token)@localhost:3000/teleo/teleo-codex.git"
+CLAUDE_BIN="/home/teleo/.local/bin/claude"
+LOG_DIR="/opt/teleo-eval/logs"
+LOG="$LOG_DIR/extract-cron.log"
+LOCKFILE="/tmp/extract-cron.lock"
+MAX_SOURCES=5  # Process at most 5 sources per run to limit cost
+
+log() { echo "[$(date -Iseconds)] $*" >> "$LOG"; }
+
+# --- Lock ---
+if [ -f "$LOCKFILE" ]; then
+    pid=$(cat "$LOCKFILE" 2>/dev/null)
+    if kill -0 "$pid" 2>/dev/null; then
+        log "SKIP: already running (pid $pid)"
+        exit 0
+    fi
+    log "WARN: stale lockfile, removing"
+    rm -f "$LOCKFILE"
+fi
+echo $$ > "$LOCKFILE"
+trap 'rm -f "$LOCKFILE"' EXIT
+
+# --- Ensure repo clone ---
+if [ ! -d "$REPO_DIR/.git" ]; then
+    log "Cloning repo..."
+    git clone "$REPO_URL" "$REPO_DIR" >> "$LOG" 2>&1
+fi
+
+cd "$REPO_DIR"
+
+# --- Pull latest main ---
+git checkout main >> "$LOG" 2>&1
+git pull --rebase >> "$LOG" 2>&1
+
+# --- Find unprocessed sources ---
+UNPROCESSED=$(grep -rl '^status: unprocessed' inbox/archive/ 2>/dev/null | head -n "$MAX_SOURCES" || true)
+
+if [ -z "$UNPROCESSED" ]; then
+    log "No unprocessed sources found"
+    exit 0
+fi
+
+COUNT=$(echo "$UNPROCESSED" | wc -l | tr -d ' ')
+log "Found $COUNT unprocessed source(s)"
+
+# --- Process each source ---
+for SOURCE_FILE in $UNPROCESSED; do
+    SLUG=$(basename "$SOURCE_FILE" .md)
+    BRANCH="extract/$SLUG"
+
+    log "Processing: $SOURCE_FILE → branch $BRANCH"
+
+    # Create branch from main
+    git checkout main >> "$LOG" 2>&1
+    git branch -D "$BRANCH" 2>/dev/null || true
+    git checkout -b "$BRANCH" >> "$LOG" 2>&1
+
+    # Read domain from frontmatter
+    DOMAIN=$(grep '^domain:' "$SOURCE_FILE" | head -1 | sed 's/domain: *//' | tr -d '"' | tr -d "'" | xargs)
+
+    # Map domain to agent
+    case "$DOMAIN" in
+        internet-finance) AGENT="rio" ;;
+        entertainment) AGENT="clay" ;;
+        ai-alignment) AGENT="theseus" ;;
+        health) AGENT="vida" ;;
+        space-development) AGENT="astra" ;;
+        *) AGENT="leo" ;;
+    esac
+
+    AGENT_TOKEN=$(cat "/opt/teleo-eval/secrets/forgejo-${AGENT}-token" 2>/dev/null || cat /opt/teleo-eval/secrets/forgejo-leo-token)
+
+    log "Domain: $DOMAIN, Agent: $AGENT"
+
+    # Run Claude headless to extract claims
+    EXTRACT_PROMPT="You are $AGENT, a Teleo knowledge base agent. Extract claims from this source.
+
+READ these files first:
+- skills/extract.md (extraction process)
+- schemas/claim.md (claim format)
+- $SOURCE_FILE (the source to extract from)
+
+Then scan domains/$DOMAIN/ to check for duplicate claims.
+
+EXTRACT claims following the process in skills/extract.md:
+1. Read the source completely
+2. Separate evidence from interpretation
+3. Extract candidate claims (specific, disagreeable, evidence-backed)
+4. Check for duplicates against existing claims in domains/$DOMAIN/
+5. Write claim files to domains/$DOMAIN/ with proper YAML frontmatter
+6. Update $SOURCE_FILE: set status to 'processed', add processed_by: $AGENT, processed_date: $(date +%Y-%m-%d), and claims_extracted list
+
+If no claims can be extracted, update $SOURCE_FILE: set status to 'null-result' and add notes explaining why.
+
+IMPORTANT: Use the Edit tool to update the source file status. Use the Write tool to create new claim files. Do not create claims that duplicate existing ones."
+
+    # Run extraction with timeout (10 minutes)
+    timeout 600 "$CLAUDE_BIN" -p "$EXTRACT_PROMPT" \
+        --allowedTools 'Read,Write,Edit,Glob,Grep' \
+        --model sonnet \
+        >> "$LOG" 2>&1 || {
+        log "WARN: Claude extraction failed or timed out for $SOURCE_FILE"
+        git checkout main >> "$LOG" 2>&1
+        continue
+    }
+
+    # Check if any files were created/modified
+    CHANGES=$(git status --porcelain | wc -l | tr -d ' ')
+    if [ "$CHANGES" -eq 0 ]; then
+        log "No changes produced for $SOURCE_FILE"
+        git checkout main >> "$LOG" 2>&1
+        continue
+    fi
+
+    # Stage and commit
+    git add inbox/archive/ "domains/$DOMAIN/" >> "$LOG" 2>&1
+    git commit -m "$AGENT: extract claims from $(basename "$SOURCE_FILE")
+
+- Source: $SOURCE_FILE
+- Domain: $DOMAIN
+- Extracted by: headless extraction cron
+
+Pentagon-Agent: $(echo "$AGENT" | sed 's/./\U&/') <HEADLESS>" >> "$LOG" 2>&1
+
+    # Push branch
+    git push -u "$REPO_URL" "$BRANCH" --force >> "$LOG" 2>&1
+
+    # Open PR
+    PR_TITLE="$AGENT: extract claims from $(basename "$SOURCE_FILE" .md)"
+    PR_BODY="## Automated Extraction\n\nSource: \`$SOURCE_FILE\`\nDomain: $DOMAIN\nExtracted by: headless cron on VPS\n\nThis PR was created automatically by the extraction cron job. Claims were extracted using \`skills/extract.md\` process via Claude headless."
+
+    curl -s -X POST "http://localhost:3000/api/v1/repos/teleo/teleo-codex/pulls" \
+        -H "Authorization: token $AGENT_TOKEN" \
+        -H "Content-Type: application/json" \
+        -d "{
+            \"title\": \"$PR_TITLE\",
+            \"body\": \"$PR_BODY\",
+            \"base\": \"main\",
+            \"head\": \"$BRANCH\"
+        }" >> "$LOG" 2>&1
+
+    log "PR opened for $SOURCE_FILE"
+
+    # Back to main for next source
+    git checkout main >> "$LOG" 2>&1
+
+    # Brief pause between extractions
+    sleep 5
+done
+
+log "Extraction run complete: processed $COUNT source(s)"

ops/extract-graph-data.py

@@ -0,0 +1,520 @@
+#!/usr/bin/env python3
+"""
+extract-graph-data.py — Extract knowledge graph from teleo-codex markdown files.
+
+Reads all .md claim/conviction files, parses YAML frontmatter and wiki-links,
+and outputs graph-data.json matching the teleo-app GraphData interface.
+
+Usage:
+    python3 ops/extract-graph-data.py [--output path/to/graph-data.json]
+
+Must be run from the teleo-codex repo root.
+"""
+
+import argparse
+import json
+import os
+import re
+import subprocess
+import sys
+from datetime import datetime, timezone
+from pathlib import Path
+
+# ---------------------------------------------------------------------------
+# Config
+# ---------------------------------------------------------------------------
+
+SCAN_DIRS = ["core", "domains", "foundations", "convictions"]
+
+# Only extract these content types (from frontmatter `type` field).
+# If type is missing, include the file anyway (many claims lack explicit type).
+INCLUDE_TYPES = {"claim", "conviction", "analysis", "belief", "position", None}
+
+# Domain → default agent mapping (fallback when git attribution unavailable)
+DOMAIN_AGENT_MAP = {
+    "internet-finance": "rio",
+    "entertainment": "clay",
+    "health": "vida",
+    "ai-alignment": "theseus",
+    "space-development": "astra",
+    "grand-strategy": "leo",
+    "mechanisms": "leo",
+    "living-capital": "leo",
+    "living-agents": "leo",
+    "teleohumanity": "leo",
+    "critical-systems": "leo",
+    "collective-intelligence": "leo",
+    "teleological-economics": "leo",
+    "cultural-dynamics": "clay",
+}
+
+DOMAIN_COLORS = {
+    "internet-finance": "#4A90D9",
+    "entertainment": "#9B59B6",
+    "health": "#2ECC71",
+    "ai-alignment": "#E74C3C",
+    "space-development": "#F39C12",
+    "grand-strategy": "#D4AF37",
+    "mechanisms": "#1ABC9C",
+    "living-capital": "#3498DB",
+    "living-agents": "#E67E22",
+    "teleohumanity": "#F1C40F",
+    "critical-systems": "#95A5A6",
+    "collective-intelligence": "#BDC3C7",
+    "teleological-economics": "#7F8C8D",
+    "cultural-dynamics": "#C0392B",
+}
+
+KNOWN_AGENTS = {"leo", "rio", "clay", "vida", "theseus", "astra"}
+
+# Regex patterns
+FRONTMATTER_RE = re.compile(r"^---\s*\n(.*?)\n---", re.DOTALL)
+WIKILINK_RE = re.compile(r"\[\[([^\]]+)\]\]")
+YAML_FIELD_RE = re.compile(r"^(\w[\w_]*):\s*(.+)$", re.MULTILINE)
+YAML_LIST_ITEM_RE = re.compile(r'^\s*-\s+"?(.+?)"?\s*$', re.MULTILINE)
+COUNTER_EVIDENCE_RE = re.compile(r"^##\s+Counter[\s-]?evidence", re.MULTILINE | re.IGNORECASE)
+COUNTERARGUMENT_RE = re.compile(r"^\*\*Counter\s*argument", re.MULTILINE | re.IGNORECASE)
+
+
+# ---------------------------------------------------------------------------
+# Lightweight YAML-ish frontmatter parser (avoids PyYAML dependency)
+# ---------------------------------------------------------------------------
+
+def parse_frontmatter(text: str) -> dict:
+    """Parse YAML frontmatter from markdown text. Returns dict of fields."""
+    m = FRONTMATTER_RE.match(text)
+    if not m:
+        return {}
+    yaml_block = m.group(1)
+    result = {}
+    for field_match in YAML_FIELD_RE.finditer(yaml_block):
+        key = field_match.group(1)
+        val = field_match.group(2).strip().strip('"').strip("'")
+        # Handle list fields
+        if val.startswith("["):
+            # Inline YAML list: [item1, item2]
+            items = re.findall(r'"([^"]+)"', val)
+            if not items:
+                items = [x.strip().strip('"').strip("'")
+                         for x in val.strip("[]").split(",") if x.strip()]
+            result[key] = items
+        else:
+            result[key] = val
+    # Handle multi-line list fields (depends_on, challenged_by, secondary_domains)
+    for list_key in ("depends_on", "challenged_by", "secondary_domains", "claims_extracted"):
+        if list_key not in result:
+            # Check for block-style list
+            pattern = re.compile(
+                rf"^{list_key}:\s*\n((?:\s+-\s+.+\n?)+)", re.MULTILINE
+            )
+            lm = pattern.search(yaml_block)
+            if lm:
+                items = YAML_LIST_ITEM_RE.findall(lm.group(1))
+                result[list_key] = [i.strip('"').strip("'") for i in items]
+    return result
+
+
+def extract_body(text: str) -> str:
+    """Return the markdown body after frontmatter."""
+    m = FRONTMATTER_RE.match(text)
+    if m:
+        return text[m.end():]
+    return text
+
+
+# ---------------------------------------------------------------------------
+# Git-based agent attribution
+# ---------------------------------------------------------------------------
+
+def build_git_agent_map(repo_root: str) -> dict[str, str]:
+    """Map file paths → agent name using git log commit message prefixes.
+
+    Commit messages follow: '{agent}: description'
+    We use the commit that first added each file.
+    """
+    file_agent = {}
+    try:
+        result = subprocess.run(
+            ["git", "log", "--all", "--diff-filter=A", "--name-only",
+             "--format=COMMIT_MSG:%s"],
+            capture_output=True, text=True, cwd=repo_root, timeout=30,
+        )
+        current_agent = None
+        for line in result.stdout.splitlines():
+            line = line.strip()
+            if not line:
+                continue
+            if line.startswith("COMMIT_MSG:"):
+                msg = line[len("COMMIT_MSG:"):]
+                # Parse "agent: description" pattern
+                if ":" in msg:
+                    prefix = msg.split(":")[0].strip().lower()
+                    if prefix in KNOWN_AGENTS:
+                        current_agent = prefix
+                    else:
+                        current_agent = None
+                else:
+                    current_agent = None
+            elif current_agent and line.endswith(".md"):
+                # Only set if not already attributed (first add wins)
+                if line not in file_agent:
+                    file_agent[line] = current_agent
+    except (subprocess.TimeoutExpired, FileNotFoundError):
+        pass
+    return file_agent
+
+
+# ---------------------------------------------------------------------------
+# Wiki-link resolution
+# ---------------------------------------------------------------------------
+
+def build_title_index(all_files: list[str], repo_root: str) -> dict[str, str]:
+    """Map lowercase claim titles → file paths for wiki-link resolution."""
+    index = {}
+    for fpath in all_files:
+        # Title = filename without .md extension
+        fname = os.path.basename(fpath)
+        if fname.endswith(".md"):
+            title = fname[:-3].lower()
+            index[title] = fpath
+        # Also index by relative path
+        index[fpath.lower()] = fpath
+    return index
+
+
+def resolve_wikilink(link_text: str, title_index: dict, source_dir: str) -> str | None:
+    """Resolve a [[wiki-link]] target to a file path (node ID)."""
+    text = link_text.strip()
+    # Skip map links and non-claim references
+    if text.startswith("_") or text == "_map":
+        return None
+    # Direct path match (with or without .md)
+    for candidate in [text, text + ".md"]:
+        if candidate.lower() in title_index:
+            return title_index[candidate.lower()]
+    # Title-only match
+    title = text.lower()
+    if title in title_index:
+        return title_index[title]
+    # Fuzzy: try adding .md to the basename
+    basename = os.path.basename(text)
+    if basename.lower() in title_index:
+        return title_index[basename.lower()]
+    return None
+
+
+# ---------------------------------------------------------------------------
+# PR/merge event extraction from git log
+# ---------------------------------------------------------------------------
+
+def extract_events(repo_root: str) -> list[dict]:
+    """Extract PR merge events from git log for the events timeline."""
+    events = []
+    try:
+        result = subprocess.run(
+            ["git", "log", "--merges", "--format=%H|%s|%ai", "-50"],
+            capture_output=True, text=True, cwd=repo_root, timeout=15,
+        )
+        for line in result.stdout.strip().splitlines():
+            parts = line.split("|", 2)
+            if len(parts) < 3:
+                continue
+            sha, msg, date_str = parts
+            # Parse "Merge pull request #N from ..." or agent commit patterns
+            pr_match = re.search(r"#(\d+)", msg)
+            if not pr_match:
+                continue
+            pr_num = int(pr_match.group(1))
+            # Try to determine agent from merge commit
+            agent = "collective"
+            for a in KNOWN_AGENTS:
+                if a in msg.lower():
+                    agent = a
+                    break
+            # Count files changed in this merge
+            diff_result = subprocess.run(
+                ["git", "diff", "--name-only", f"{sha}^..{sha}"],
+                capture_output=True, text=True, cwd=repo_root, timeout=10,
+            )
+            claims_added = sum(
+                1 for f in diff_result.stdout.splitlines()
+                if f.endswith(".md") and any(f.startswith(d) for d in SCAN_DIRS)
+            )
+            if claims_added > 0:
+                events.append({
+                    "type": "pr-merge",
+                    "number": pr_num,
+                    "agent": agent,
+                    "claims_added": claims_added,
+                    "date": date_str[:10],
+                })
+    except (subprocess.TimeoutExpired, FileNotFoundError):
+        pass
+    return events
+
+
+# ---------------------------------------------------------------------------
+# Main extraction
+# ---------------------------------------------------------------------------
+
+def find_markdown_files(repo_root: str) -> list[str]:
+    """Find all .md files in SCAN_DIRS, return relative paths."""
+    files = []
+    for scan_dir in SCAN_DIRS:
+        dirpath = os.path.join(repo_root, scan_dir)
+        if not os.path.isdir(dirpath):
+            continue
+        for root, _dirs, filenames in os.walk(dirpath):
+            for fname in filenames:
+                if fname.endswith(".md") and not fname.startswith("_"):
+                    rel = os.path.relpath(os.path.join(root, fname), repo_root)
+                    files.append(rel)
+    return sorted(files)
+
+
+def _get_domain_cached(fpath: str, repo_root: str, cache: dict) -> str:
+    """Get the domain of a file, caching results."""
+    if fpath in cache:
+        return cache[fpath]
+    abs_path = os.path.join(repo_root, fpath)
+    domain = ""
+    try:
+        text = open(abs_path, encoding="utf-8").read()
+        fm = parse_frontmatter(text)
+        domain = fm.get("domain", "")
+    except (OSError, UnicodeDecodeError):
+        pass
+    cache[fpath] = domain
+    return domain
+
+
+def extract_graph(repo_root: str) -> dict:
+    """Extract the full knowledge graph from the codex."""
+    all_files = find_markdown_files(repo_root)
+    git_agents = build_git_agent_map(repo_root)
+    title_index = build_title_index(all_files, repo_root)
+    domain_cache: dict[str, str] = {}
+
+    nodes = []
+    edges = []
+    node_ids = set()
+    all_files_set = set(all_files)
+
+    for fpath in all_files:
+        abs_path = os.path.join(repo_root, fpath)
+        try:
+            text = open(abs_path, encoding="utf-8").read()
+        except (OSError, UnicodeDecodeError):
+            continue
+
+        fm = parse_frontmatter(text)
+        body = extract_body(text)
+
+        # Filter by type
+        ftype = fm.get("type")
+        if ftype and ftype not in INCLUDE_TYPES:
+            continue
+
+        # Build node
+        title = os.path.basename(fpath)[:-3]  # filename without .md
+        domain = fm.get("domain", "")
+        if not domain:
+            # Infer domain from directory path
+            parts = fpath.split(os.sep)
+            if len(parts) >= 2:
+                domain = parts[1] if parts[0] == "domains" else parts[1] if len(parts) > 2 else parts[0]
+
+        # Agent attribution: git log → domain mapping → "collective"
+        agent = git_agents.get(fpath, "")
+        if not agent:
+            agent = DOMAIN_AGENT_MAP.get(domain, "collective")
+
+        created = fm.get("created", "")
+        confidence = fm.get("confidence", "speculative")
+
+        # Detect challenged status
+        challenged_by_raw = fm.get("challenged_by", [])
+        if isinstance(challenged_by_raw, str):
+            challenged_by_raw = [challenged_by_raw] if challenged_by_raw else []
+        has_challenged_by = bool(challenged_by_raw and any(c for c in challenged_by_raw))
+        has_counter_section = bool(COUNTER_EVIDENCE_RE.search(body) or COUNTERARGUMENT_RE.search(body))
+        is_challenged = has_challenged_by or has_counter_section
+
+        # Extract challenge descriptions for the node
+        challenges = []
+        if isinstance(challenged_by_raw, list):
+            for c in challenged_by_raw:
+                if c and isinstance(c, str):
+                    # Strip wiki-link syntax for display
+                    cleaned = WIKILINK_RE.sub(lambda m: m.group(1), c)
+                    # Strip markdown list artifacts: leading "- ", surrounding quotes
+                    cleaned = re.sub(r'^-\s*', '', cleaned).strip()
+                    cleaned = cleaned.strip('"').strip("'").strip()
+                    if cleaned:
+                        challenges.append(cleaned[:200])  # cap length
+
+        node = {
+            "id": fpath,
+            "title": title,
+            "domain": domain,
+            "agent": agent,
+            "created": created,
+            "confidence": confidence,
+            "challenged": is_challenged,
+        }
+        if challenges:
+            node["challenges"] = challenges
+        nodes.append(node)
+        node_ids.add(fpath)
+        domain_cache[fpath] = domain  # cache for edge lookups
+        for link_text in WIKILINK_RE.findall(body):
+            target = resolve_wikilink(link_text, title_index, os.path.dirname(fpath))
+            if target and target != fpath and target in all_files_set:
+                target_domain = _get_domain_cached(target, repo_root, domain_cache)
+                edges.append({
+                    "source": fpath,
+                    "target": target,
+                    "type": "wiki-link",
+                    "cross_domain": domain != target_domain and bool(target_domain),
+                })
+
+        # Conflict edges from challenged_by (may contain [[wiki-links]] or prose)
+        challenged_by = fm.get("challenged_by", [])
+        if isinstance(challenged_by, str):
+            challenged_by = [challenged_by]
+        if isinstance(challenged_by, list):
+            for challenge in challenged_by:
+                if not challenge:
+                    continue
+                # Check for embedded wiki-links
+                for link_text in WIKILINK_RE.findall(challenge):
+                    target = resolve_wikilink(link_text, title_index, os.path.dirname(fpath))
+                    if target and target != fpath and target in all_files_set:
+                        target_domain = _get_domain_cached(target, repo_root, domain_cache)
+                        edges.append({
+                            "source": fpath,
+                            "target": target,
+                            "type": "conflict",
+                            "cross_domain": domain != target_domain and bool(target_domain),
+                        })
+
+    # Deduplicate edges
+    seen_edges = set()
+    unique_edges = []
+    for e in edges:
+        key = (e["source"], e["target"], e.get("type", ""))
+        if key not in seen_edges:
+            seen_edges.add(key)
+            unique_edges.append(e)
+
+    # Only keep edges where both endpoints exist as nodes
+    edges_filtered = [
+        e for e in unique_edges
+        if e["source"] in node_ids and e["target"] in node_ids
+    ]
+
+    events = extract_events(repo_root)
+
+    return {
+        "nodes": nodes,
+        "edges": edges_filtered,
+        "events": sorted(events, key=lambda e: e.get("date", "")),
+        "domain_colors": DOMAIN_COLORS,
+    }
+
+
+def build_claims_context(repo_root: str, nodes: list[dict]) -> dict:
+    """Build claims-context.json for chat system prompt injection.
+
+    Produces a lightweight claim index: title + description + domain + agent + confidence.
+    Sorted by domain, then alphabetically within domain.
+    Target: ~37KB for ~370 claims. Truncates descriptions at 100 chars if total > 100KB.
+    """
+    claims = []
+    for node in nodes:
+        fpath = node["id"]
+        abs_path = os.path.join(repo_root, fpath)
+        description = ""
+        try:
+            text = open(abs_path, encoding="utf-8").read()
+            fm = parse_frontmatter(text)
+            description = fm.get("description", "")
+        except (OSError, UnicodeDecodeError):
+            pass
+
+        claims.append({
+            "title": node["title"],
+            "description": description,
+            "domain": node["domain"],
+            "agent": node["agent"],
+            "confidence": node["confidence"],
+        })
+
+    # Sort by domain, then title
+    claims.sort(key=lambda c: (c["domain"], c["title"]))
+
+    context = {
+        "generated": datetime.now(tz=timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ"),
+        "claimCount": len(claims),
+        "claims": claims,
+    }
+
+    # Progressive description truncation if over 100KB.
+    # Never drop descriptions entirely — short descriptions are better than none.
+    for max_desc in (120, 100, 80, 60):
+        test_json = json.dumps(context, ensure_ascii=False)
+        if len(test_json) <= 100_000:
+            break
+        for c in claims:
+            if len(c["description"]) > max_desc:
+                c["description"] = c["description"][:max_desc] + "..."
+
+    return context
+
+
+def main():
+    parser = argparse.ArgumentParser(description="Extract graph data from teleo-codex")
+    parser.add_argument("--output", "-o", default="graph-data.json",
+                        help="Output file path (default: graph-data.json)")
+    parser.add_argument("--context-output", "-c", default=None,
+                        help="Output claims-context.json path (default: same dir as --output)")
+    parser.add_argument("--repo", "-r", default=".",
+                        help="Path to teleo-codex repo root (default: current dir)")
+    args = parser.parse_args()
+
+    repo_root = os.path.abspath(args.repo)
+    if not os.path.isdir(os.path.join(repo_root, "core")):
+        print(f"Error: {repo_root} doesn't look like a teleo-codex repo (no core/ dir)", file=sys.stderr)
+        sys.exit(1)
+
+    print(f"Scanning {repo_root}...")
+    graph = extract_graph(repo_root)
+
+    print(f"  Nodes: {len(graph['nodes'])}")
+    print(f"  Edges: {len(graph['edges'])}")
+    print(f"  Events: {len(graph['events'])}")
+    challenged_count = sum(1 for n in graph["nodes"] if n.get("challenged"))
+    print(f"  Challenged: {challenged_count}")
+
+    # Write graph-data.json
+    output_path = os.path.abspath(args.output)
+    with open(output_path, "w", encoding="utf-8") as f:
+        json.dump(graph, f, indent=2, ensure_ascii=False)
+    size_kb = os.path.getsize(output_path) / 1024
+    print(f"  graph-data.json: {output_path} ({size_kb:.1f} KB)")
+
+    # Write claims-context.json
+    context_path = args.context_output
+    if not context_path:
+        context_path = os.path.join(os.path.dirname(output_path), "claims-context.json")
+    context_path = os.path.abspath(context_path)
+
+    context = build_claims_context(repo_root, graph["nodes"])
+    with open(context_path, "w", encoding="utf-8") as f:
+        json.dump(context, f, indent=2, ensure_ascii=False)
+    ctx_kb = os.path.getsize(context_path) / 1024
+    print(f"  claims-context.json: {context_path} ({ctx_kb:.1f} KB)")
+
+
+if __name__ == "__main__":
+    main()

schemas/conviction.md

@@ -0,0 +1,82 @@
+# Conviction Schema
+
+Convictions are high-confidence assertions staked on personal reputation. They bypass the normal extraction and review pipeline — the evidence is the staker's judgment, not external sources. Convictions enter the knowledge base immediately when staked.
+
+Convictions are load-bearing inputs: agents can reference them in beliefs and positions the same way they reference claims. The provenance is transparent — "Cory stakes this" is different from "the evidence shows this."
+
+## YAML Frontmatter
+
+```yaml
+---
+type: conviction
+domain: internet-finance | entertainment | health | ai-alignment | grand-strategy | mechanisms | living-capital | living-agents | teleohumanity | critical-systems | collective-intelligence | teleological-economics | cultural-dynamics
+description: "one sentence adding context beyond the title"
+staked_by: "who is staking their reputation on this"
+stake: high | medium  # how much credibility is on the line
+created: YYYY-MM-DD
+---
+```
+
+## Required Fields
+
+| Field | Type | Description |
+|-------|------|-------------|
+| type | enum | Always `conviction` |
+| domain | enum | Primary domain |
+| description | string | Context beyond title (~150 chars) |
+| staked_by | string | Who is staking reputation. Currently: Cory |
+| stake | enum | `high` (would be shocked if wrong) or `medium` (strong belief, open to evidence) |
+| created | date | When staked |
+
+## Optional Fields
+
+| Field | Type | Description |
+|-------|------|-------------|
+| secondary_domains | list | Other domains this conviction is relevant to |
+| horizon | string | When this should be evaluable (e.g., "2027", "5 years") |
+| falsified_by | string | What evidence would change the staker's mind |
+
+## Governance
+
+- **Who can stake:** Cory (founder). May extend to other humans as the collective grows.
+- **No review required:** Convictions enter the knowledge base on stake. That's the point — they represent founder direction, not collective consensus.
+- **Agents respond, not gatekeep:** When a conviction is staked, agents in the relevant domain should assess implications for their beliefs and positions. A conviction may trigger new claims, belief updates, or research directions.
+- **Falsification:** If evidence emerges that contradicts a conviction, agents flag it. The staker decides whether to update, downgrade, or retire the conviction. Intellectual honesty applies — staking reputation means accepting when you're wrong.
+
+## Title Format
+
+Same as claims: prose propositions that pass the claim test.
+
+**Good:** "AI-automated software development is certain and will radically change how software is built"
+**Bad:** "AI and software development"
+
+## Body Format
+
+```markdown
+# [prose conviction title]
+
+[Why I believe this — personal reasoning, pattern recognition, experience]
+
+[What I'd stake on it — what would I bet, what would change my mind]
+
+---
+
+Relevant Notes:
+- [[related-claim-or-conviction]] — relationship description
+
+Topics:
+- [[domain-topic-map]]
+```
+
+## How Agents Use Convictions
+
+Convictions function as strong priors in the collective's reasoning:
+
+1. **Belief grounding:** An agent can cite a conviction in their beliefs.md alongside claims. The belief should note the source type: "grounded in Cory conviction + [supporting claims]"
+2. **Research direction:** A conviction signals where to invest extraction and synthesis effort. If Cory stakes "AI-automated software development is certain," agents should prioritize building the evidence base around it.
+3. **Position anchoring:** Convictions can anchor positions, but agents should seek independent evidence. A position built entirely on conviction without supporting claims is fragile.
+4. **Disagreement:** Agents can disagree with convictions in their musings or beliefs. The conviction stays in the KB regardless — it represents the staker's view, not consensus.
+
+## Where They Live
+
+`convictions/` at the repository root. One file per conviction.

skills/coordinate.md

@@ -0,0 +1,146 @@
+# Skill: Coordinate
+
+Structure inter-agent communication so information transfers without human routing.
+
+## When to Use
+
+- Discovering something relevant to another agent's domain
+- Passing a working artifact (analysis, draft, data) to a collaborator
+- Flagging a claim for cross-domain synthesis
+- Handing off work that spans agent boundaries
+- Starting or continuing a multi-agent collaboration
+
+## Shared Workspace
+
+Active collaboration artifacts live at `~/.pentagon/workspace/`:
+
+```
+workspace/
+├── {agent1}-{agent2}/    # Bilateral collaboration dirs
+├── collective/           # Cross-domain flags, synthesis queue
+└── drafts/               # Pre-PR working documents
+```
+
+Use the workspace for artifacts that need iteration between agents. Use the knowledge base (repo) for finished work that passes quality gates.
+
+## Cross-Domain Flag
+
+When you find something in your domain relevant to another agent's domain.
+
+### Format
+
+Write to `~/.pentagon/workspace/collective/flag-{your-name}-{topic}.md`:
+
+```markdown
+## Cross-Domain Flag: [your name] → [target agent]
+**Date**: [date]
+**What I found**: [specific claim, evidence, or pattern]
+**What it means for your domain**: [interpretation in their context]
+**Recommended action**: extract | enrich | review | synthesize | none
+**Relevant files**: [paths to claims, sources, or artifacts]
+**Priority**: high | medium | low
+```
+
+### When to flag
+
+- New evidence that strengthens or weakens a claim outside your domain
+- A pattern in your domain that mirrors or contradicts a pattern in theirs
+- A source that contains extractable claims for their territory
+- A connection between your claims and theirs that nobody has made explicit
+
+## Artifact Transfer
+
+When passing a working document, analysis, or tool to another agent.
+
+### Format
+
+Write the artifact to `~/.pentagon/workspace/{your-name}-{their-name}/` with a companion context file:
+
+```markdown
+## Artifact: [name]
+**From**: [your name]
+**Date**: [date]
+**Context**: [what this is and why it matters]
+**How to use**: [what the receiving agent should do with it]
+**Dependencies**: [what claims/beliefs this connects to]
+**State**: draft | ready-for-review | final
+```
+
+The artifact itself is a separate file in the same directory. The context file tells the receiving agent what they're looking at and what to do with it.
+
+### Key principle
+
+Transfer the artifact AND the context. In the Claude's Cycles evidence, the orchestrator didn't just send Agent C's fiber tables to Agent O — the protocol told Agent O what to look for. An artifact without context is noise.
+
+## Synthesis Request
+
+When you notice a cross-domain pattern that needs Leo's synthesis attention.
+
+### Format
+
+Append to `~/.pentagon/workspace/collective/synthesis-queue.md`:
+
+```markdown
+### [date] — [your name]
+**Pattern**: [what you noticed]
+**Domains involved**: [which domains]
+**Claims that connect**: [wiki links or file paths]
+**Why this matters**: [what insight the synthesis would produce]
+```
+
+### Triggers
+
+Flag for synthesis when:
+- 10+ claims added to a domain since last synthesis
+- A claim has been enriched 3+ times (it's load-bearing, check dependents)
+- Two agents independently arrive at similar conclusions from different evidence
+- A contradiction between domains hasn't been explicitly addressed
+
+## PR Cross-Domain Tagging
+
+When opening a PR that touches claims relevant to other agents' domains.
+
+### Format
+
+Add to PR description:
+
+```markdown
+## Cross-Domain Impact
+- **[agent name]**: [what this PR means for their domain, what they should review]
+```
+
+This replaces ad-hoc "hey, look at this" messages with structured notification through the existing review flow.
+
+## Handoff Protocol
+
+When transferring ongoing work to another agent (e.g., handing off a research thread, passing a partially-complete analysis).
+
+### Format
+
+Write to `~/.pentagon/workspace/{your-name}-{their-name}/handoff-{topic}.md`:
+
+```markdown
+## Handoff: [your name] → [their name]
+**Date**: [date]
+**What I did**: [summary of work completed]
+**What remains**: [specific next steps]
+**Open questions**: [unresolved issues they should be aware of]
+**Key files**: [paths to relevant claims, sources, artifacts]
+**Context they'll need**: [background that isn't obvious from the files]
+```
+
+## Session Start Checklist
+
+Add to your session startup:
+
+1. Check `~/.pentagon/workspace/collective/` for new flags addressed to you
+2. Check `~/.pentagon/workspace/{collaborator}-{your-name}/` for new artifacts
+3. Check `~/.pentagon/workspace/collective/synthesis-queue.md` for patterns in your domain
+
+## Quality Gate
+
+- Every flag includes a recommended action (not just "FYI")
+- Every artifact includes context (not just the file)
+- Every synthesis request identifies specific claims that connect
+- Every handoff includes open questions (not just completed work)
+- Flags older than 5 sessions without action get triaged: act or archive

skills/ingest.md

@@ -0,0 +1,201 @@
+# Skill: Ingest
+
+Research your domain, find source material, and archive it in inbox/. You choose whether to extract claims yourself or let the VPS handle it.
+
+**Archive everything.** The inbox is a library, not a filter. If it's relevant to any Teleo domain, archive it. Null-result sources (no extractable claims) are still valuable — they prevent duplicate work and build domain context.
+
+## Usage
+
+```
+/ingest                    # Research loop: pull tweets, find sources, archive with notes
+/ingest @username          # Pull and archive a specific X account's content
+/ingest url <url>          # Archive a paper, article, or thread from URL
+/ingest scan               # Scan your network for new content since last pull
+/ingest extract            # Extract claims from sources you've already archived (Track A)
+```
+
+## Two Tracks
+
+### Track A: Agent-driven extraction (full control)
+
+You research, archive, AND extract. You see exactly what you're proposing before it goes up.
+
+1. Archive sources with `status: processing`
+2. Extract claims yourself using `skills/extract.md`
+3. Open a PR with both source archives and claim files
+4. Eval pipeline reviews your claims
+
+**Use when:** You're doing a deep dive on a specific topic, care about extraction quality, or want to control the narrative around new claims.
+
+### Track B: VPS extraction (hands-off)
+
+You research and archive. The VPS extracts headlessly.
+
+1. Archive sources with `status: unprocessed`
+2. Push source-only PR (merges fast — no claim changes)
+3. VPS cron picks up unprocessed sources every 15 minutes
+4. Extracts claims via Claude headless, opens a separate PR
+5. Eval pipeline reviews the extraction
+
+**Use when:** You're batch-archiving many sources, the content is straightforward, or you want to focus your session time on research rather than extraction.
+
+### The switch is the status field
+
+| Status | What happens |
+|--------|-------------|
+| `unprocessed` | VPS will extract (Track B) |
+| `processing` | You're handling it (Track A) — VPS skips this source |
+| `processed` | Already extracted — no further action |
+| `null-result` | Reviewed, no claims — no further action |
+
+You can mix tracks freely. Archive 10 sources as `unprocessed` for the VPS, then set 2 high-priority ones to `processing` and extract those yourself.
+
+## Prerequisites
+
+- API key at `~/.pentagon/secrets/twitterapi-io-key`
+- Your network file at `~/.pentagon/workspace/collective/x-ingestion/{your-name}-network.json`
+- Forgejo token at `~/.pentagon/secrets/forgejo-{your-name}-token`
+
+## The Loop
+
+### Step 1: Research
+
+Find source material relevant to your domain. Sources include:
+- **X/Twitter** — tweets, threads, debates from your network accounts
+- **Papers** — academic papers, preprints, whitepapers
+- **Articles** — blog posts, newsletters, news coverage
+- **Reports** — industry reports, data releases, government filings
+- **Conversations** — podcast transcripts, interview notes, voicenote transcripts
+
+For X accounts, use `/x-research pull @{username}` to pull tweets, then scan for anything worth archiving. Don't just archive the "best" tweets — archive anything substantive. A thread arguing a wrong position is as valuable as one arguing a right one.
+
+### Step 2: Archive with notes
+
+For each source, create an archive file on your branch:
+
+**Filename:** `inbox/archive/YYYY-MM-DD-{author-handle}-{brief-slug}.md`
+
+```yaml
+---
+type: source
+title: "Descriptive title of the content"
+author: "Display Name (@handle)"
+twitter_id: "numeric_id_from_author_object"  # X sources only
+url: https://original-url
+date: YYYY-MM-DD
+domain: internet-finance | entertainment | ai-alignment | health | space-development | grand-strategy
+secondary_domains: [other-domain]  # if cross-domain
+format: tweet | thread | essay | paper | whitepaper | report | newsletter | news | transcript
+status: unprocessed | processing    # unprocessed = VPS extracts; processing = you extract
+priority: high | medium | low
+tags: [topic1, topic2]
+flagged_for_rio: ["reason"]  # if relevant to another agent's domain
+---
+```
+
+**Body:** Include the full source text, then your research notes.
+
+```markdown
+## Content
+
+[Full text of tweet/thread/article. For long papers, include abstract + key sections.]
+
+## Agent Notes
+
+**Why this matters:** [1-2 sentences — what makes this worth archiving]
+
+**KB connections:** [Which existing claims does this relate to, support, or challenge?]
+
+**Extraction hints:** [What claims might the extractor pull from this? Flag specific passages.]
+
+**Context:** [Anything the extractor needs to know — who the author is, what debate this is part of, etc.]
+```
+
+The "Agent Notes" section is critical for Track B. The VPS extractor is good at mechanical extraction but lacks your domain context. Your notes guide it. For Track A, you still benefit from writing notes — they organize your thinking before extraction.
+
+### Step 3: Extract claims (Track A only)
+
+If you set `status: processing`, follow `skills/extract.md`:
+
+1. Read the source completely
+2. Separate evidence from interpretation
+3. Extract candidate claims (specific, disagreeable, evidence-backed)
+4. Check for duplicates against existing KB
+5. Write claim files to `domains/{your-domain}/`
+6. Update source: `status: processed`, `processed_by`, `processed_date`, `claims_extracted`
+
+### Step 4: Cross-domain flagging
+
+When you find sources outside your domain:
+- Archive them anyway (you're already reading them)
+- Set the `domain` field to the correct domain, not yours
+- Add `flagged_for_{agent}: ["brief reason"]` to frontmatter
+- Set `priority: high` if it's urgent or challenges existing claims
+
+### Step 5: Branch, commit, push
+
+```bash
+# Branch
+git checkout -b {your-name}/sources-{date}-{brief-slug}
+
+# Stage — sources only (Track B) or sources + claims (Track A)
+git add inbox/archive/*.md
+git add domains/{your-domain}/*.md  # Track A only
+
+# Commit
+git commit -m "{your-name}: archive {N} sources — {brief description}
+
+- What: {N} sources from {list of authors/accounts}
+- Domains: {which domains these cover}
+- Track: A (agent-extracted) | B (VPS extraction pending)
+
+Pentagon-Agent: {Name} <{UUID}>"
+
+# Push
+FORGEJO_TOKEN=$(cat ~/.pentagon/secrets/forgejo-{your-name}-token)
+git push -u https://{your-name}:${FORGEJO_TOKEN}@git.livingip.xyz/teleo/teleo-codex.git {branch-name}
+```
+
+Open a PR:
+```bash
+curl -s -X POST "https://git.livingip.xyz/api/v1/repos/teleo/teleo-codex/pulls" \
+  -H "Authorization: token ${FORGEJO_TOKEN}" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "title": "{your-name}: {archive N sources | extract N claims} — {brief description}",
+    "body": "## Sources\n{numbered list with titles and domains}\n\n## Claims (Track A only)\n{claim titles}\n\n## Track B sources (VPS extraction pending)\n{list of unprocessed sources}",
+    "base": "main",
+    "head": "{branch-name}"
+  }'
+```
+
+## Network Management
+
+Your network file (`{your-name}-network.json`) lists X accounts to monitor:
+
+```json
+{
+  "agent": "your-name",
+  "domain": "your-domain",
+  "accounts": [
+    {"username": "example", "tier": "core", "why": "Reason this account matters"},
+    {"username": "example2", "tier": "extended", "why": "Secondary but useful"}
+  ]
+}
+```
+
+**Tiers:**
+- `core` — Pull every session. High signal-to-noise.
+- `extended` — Pull weekly or when specifically relevant.
+- `watch` — Pull once to evaluate, then promote or drop.
+
+Agents without a network file should create one as their first task. Start with 5-10 seed accounts.
+
+## Quality Controls
+
+- **Archive everything substantive.** Don't self-censor. The extractor decides what yields claims.
+- **Write good notes.** Your domain context is the difference between a useful source and a pile of text.
+- **Check for duplicates.** Don't re-archive sources already in `inbox/archive/`.
+- **Flag cross-domain.** If you see something relevant to another agent, flag it — don't assume they'll find it.
+- **Log API costs.** Every X pull gets logged to `~/.pentagon/workspace/collective/x-ingestion/pull-log.jsonl`.
+- **Source diversity.** If you're archiving 10+ items from one account in a batch, note it — the extractor should be aware of monoculture risk.