leo: add divergence schema, update CLAUDE.md and README for game mechanic

- What: new divergence schema (structured disagreements between 2-5 claims), README rewrite with game framing, CLAUDE.md integration (knowledge structure, review checklist, quality gates)
- Why: divergences are the core multiplayer mechanic — open questions that invite contributor evidence. Reviewed by Ganymede, Rhea, and Epimetheus across two rounds. Slimmed from 200 to 77 lines after over-engineering feedback.
- Connections: unblocks seeding first divergences, enables importance-weighted scoring (coming soon)

Pentagon-Agent: Leo <A3DC172B-F0A4-4408-9E3B-CF842616AAE1>

CLAUDE.md

@@ -46,13 +46,15 @@ This gets them into conversation immediately. If they push back on a claim, you'
 
 ### 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.
+1. **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.
 
-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.
+2. **Resolve a divergence** — The highest-value move. Divergences are open disagreements where the KB has competing claims about the same question. Provide evidence that settles one and you've changed beliefs and positions downstream. Check `domains/{domain}/divergence-*` files for open questions.
 
 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.
+4. **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.
+
+5. **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
 
@@ -154,6 +156,7 @@ teleo-codex/
 │   └── astra/
 ├── schemas/                      # How content is structured
 │   ├── claim.md
+│   ├── divergence.md             # Structured disagreements (2-5 competing claims)
 │   ├── belief.md
 │   ├── position.md
 │   ├── musing.md
@@ -201,6 +204,13 @@ Arguable assertions backed by evidence. Live in `core/`, `foundations/`, and `do
 
 Claims feed beliefs. Beliefs feed positions. When claims change, beliefs get flagged for review. When beliefs change, positions get flagged.
 
+### Divergences (structured disagreements)
+When 2-5 claims offer competing answers to the same question, create a divergence file at `domains/{domain}/divergence-{slug}.md`. Divergences are the core game mechanic — they're open invitations for contributors to provide evidence that resolves the disagreement. See `schemas/divergence.md` for the full spec. Key rules:
+- Links 2-5 existing claims, doesn't contain them
+- Must include "What Would Resolve This" section (the research agenda)
+- ~85% of apparent tensions are scope mismatches, not real divergences — fix the scope first
+- Resolved by evidence, never by authority
+
 ### Musings (per-agent exploratory thinking)
 Pre-claim brainstorming that lives in `agents/{name}/musings/`. Musings are where agents develop ideas before they're ready for extraction — connecting dots, flagging questions, building toward claims. See `schemas/musing.md` for the full spec. Key rules:
 - One-way linking: musings link to claims, never the reverse
@@ -346,12 +356,13 @@ For each proposed claim, check:
 3. **Description quality** — Does the description add info beyond the title?
 4. **Confidence calibration** — Does the confidence level match the evidence?
 5. **Duplicate check** — Does this already exist in the knowledge base? (semantic, not just title match)
-6. **Contradiction check** — Does this contradict an existing claim? If so, is the contradiction explicit and argued?
+6. **Contradiction check** — Does this contradict an existing claim? If so, is the contradiction explicit and argued? If the contradiction represents genuine competing evidence (not a scope mismatch), flag it as a divergence candidate.
 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 what it measures? Claims should be explicit about whether they assert structural vs functional, micro vs macro, individual vs collective, or causal vs correlational relationships. Unscoped claims are the primary source of false tensions in the KB.
 10. **Universal quantifier check** — Does the title use universals ("all", "always", "never", "the fundamental", "the only")? Universals make claims appear to contradict each other when they're actually about different scopes. If a universal is used, verify it's warranted — otherwise scope it.
 11. **Counter-evidence acknowledgment** — For claims rated `likely` or higher: does counter-evidence or a counter-argument exist elsewhere in the KB? If so, the claim should acknowledge it in a `challenged_by` field or Challenges section. The absence of `challenged_by` on a high-confidence claim is a review smell — it suggests the proposer didn't check for opposing claims.
+12. **Divergence check** — Does this claim, combined with an existing claim, create a genuine divergence (competing answers to the same question with real evidence on both sides)? If so, propose a `divergence-{slug}.md` file linking them. Remember: ~85% of apparent contradictions are scope mismatches — verify it's a real disagreement before creating a divergence.
 
 ### Comment with reasoning
 Leave a review comment explaining your evaluation. Be specific:
@@ -378,6 +389,7 @@ A claim enters the knowledge base only if:
 - [ ] PR body explains reasoning
 - [ ] Scope is explicit (structural/functional, micro/macro, etc.) — no unscoped universals
 - [ ] Counter-evidence acknowledged if claim is rated `likely` or higher and opposing evidence exists in KB
+- [ ] Divergence flagged if claim creates genuine competing evidence with existing claim(s)
 
 ## Enriching Existing Claims
 

README.md

@@ -1,36 +1,31 @@
 # 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.
+Prove us wrong — and earn credit for it.
 
-**~400 claims** across 14 knowledge areas. **6 agents** with distinct perspectives. **Every link is real.**
+A collective intelligence built by 6 AI domain agents. ~400 claims across 14 knowledge areas — all linked, all traceable, all challengeable. Every claim traces from evidence through argument to public commitments. Nothing is asserted without a reason. And some of it is probably wrong.
 
-## How it works
+That's where you come in.
 
-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 game
+
+The knowledge base has open disagreements — places where the evidence genuinely supports competing claims. These are **divergences**, and resolving them is the highest-value move a contributor can make.
+
+Challenge a claim. Teach us something new. Provide evidence that settles an open question. Your contributions are attributed and traced through the knowledge graph — when a claim you contributed changes an agent's beliefs, that impact is visible.
+
+Importance-weighted contribution scoring is coming soon.
 
 ## 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 |
+| Agent | Domain | What they know |
+|-------|--------|----------------|
+| **Rio** | Internet finance | DeFi, prediction markets, futarchy, MetaDAO, token economics |
+| **Theseus** | AI / alignment | AI safety, collective intelligence, multi-agent systems, coordination |
 | **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 |
+| **Vida** | Health | Healthcare economics, AI in medicine, GLP-1s, prevention-first systems |
 | **Astra** | Space | Launch economics, cislunar infrastructure, space governance, ISRU |
+| **Leo** | Grand strategy | Cross-domain synthesis — what connects the domains |
 
-## 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.
+## How to play
 
 ```bash
 git clone https://github.com/living-ip/teleo-codex.git
@@ -38,9 +33,24 @@ cd teleo-codex
 claude
 ```
 
+Tell the agent what you work on or think about. They'll load the right domain lens and show you claims you might disagree with.
+
+**Challenge** — Push back on a claim. The agent steelmans the existing position, then engages seriously with your counter-evidence. If you shift the argument, that's a contribution.
+
+**Teach** — Share something we don't know. The agent drafts a claim and shows it to you. You approve. Your attribution stays on everything.
+
+**Resolve a divergence** — The highest-value move. Divergences are open disagreements where the KB has competing claims. Provide evidence that settles one and you've changed beliefs and positions downstream.
+
+## Where to start
+
+- **See what's contested** — `domains/{domain}/divergence-*` files show where we disagree
+- **Explore a domain** — `domains/{domain}/_map.md`
+- **See what an agent believes** — `agents/{name}/beliefs.md`
+- **Understand the structure** — `core/epistemology.md`
+
 ## 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).
+Talk to an agent and they'll handle the mechanics. Or do it manually — see [CONTRIBUTING.md](CONTRIBUTING.md).
 
 ## Built by
 

schemas/divergence.md

@@ -0,0 +1,79 @@
+# Divergence Schema
+
+A divergence links 2-5 claims that offer competing answers to the same question. Not a bug — the most valuable part of the knowledge base. Every divergence is an open invitation: "We disagree about this — who's right?"
+
+## Where they live
+
+`domains/{domain}/divergence-{slug}.md` — alongside the claims they reference. Cross-domain divergences go in the primary domain with `secondary_domains`.
+
+## YAML Frontmatter
+
+```yaml
+---
+type: divergence
+title: "the question these claims disagree about"
+domain: internet-finance | entertainment | health | ai-alignment | space-development | grand-strategy | mechanisms | living-capital | living-agents | teleohumanity | critical-systems | collective-intelligence | teleological-economics | cultural-dynamics
+description: "why this disagreement matters and what resolving it would unlock"
+status: open | resolved
+claims: []  # 2-5 claim filenames
+surfaced_by: "who identified this divergence"
+created: YYYY-MM-DD
+---
+```
+
+## Body Format
+
+```markdown
+# [question or tension]
+
+[Why this matters. What changes if we knew the answer.]
+
+## Divergent Claims
+
+### [claim title]
+**File:** [[claim-filename]]
+**Core argument:** [1-2 sentences]
+**Strongest evidence:** [what makes this credible]
+
+### [claim title]
+**File:** [[claim-filename]]
+**Core argument:** [1-2 sentences]
+**Strongest evidence:** [what makes this credible]
+
+## What Would Resolve This
+
+[Specific evidence contributors should look for. This is the research agenda — the game hook.]
+
+## Cascade Impact
+
+[What beliefs and positions change depending on which claim wins. This is the importance signal.]
+
+---
+
+Relevant Notes:
+- [[related-claim]] — relationship
+
+Topics:
+- [[domain-map]]
+```
+
+## Governance
+
+- **Who can propose:** Any agent, any contributor, or surfaced during PR review
+- **Review:** Leo reviews for genuine disagreement (not scope mismatch). Domain agents review claim summaries for accuracy.
+- **Resolution:** Evidence-based only. No authority-based resolution.
+
+## When NOT to create a divergence
+
+- **Scope mismatch:** Two claims about different scopes (structural vs functional, micro vs macro) aren't in tension. Fix the scope. ~85% of apparent tensions dissolve with better wording.
+- **Evidence gap:** One claim simply lacks evidence. Strengthen or weaken the claim — don't create a divergence.
+- **False opposition:** Complementary claims aren't contradictory. "AI helps diagnosis" and "AI doesn't help treatment" aren't in tension.
+
+## Divergences as game mechanic
+
+Divergences are the highest-value contribution targets. Resolving one means:
+- Changing claims in the KB
+- Triggering cascade re-evaluation of beliefs and positions
+- Demonstrating consequential knowledge
+
+Importance-weighted contribution scoring is coming — the importance of a contribution will be proportional to the cascade impact of the divergence it helps resolve.