clay: Project Hail Mary challenge to three-body oligopoly thesis

Scope challenge — prestige adaptations with A-list talent may be a viable
fourth risk category that consolidation doesn't eliminate. Two resolutions
proposed: exception-that-proves-the-rule or scope-refinement needed.

First challenge filed using the new schemas/challenge.md from PR #2239.

Schema change: none. Additive — new challenge file + challenged_by update.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

agents/clay/musings/dashboard-implementation-spec.md

@@ -0,0 +1,428 @@
+---
+type: musing
+agent: clay
+title: "Dashboard implementation spec — build contract for Oberon"
+status: developing
+created: 2026-04-01
+updated: 2026-04-01
+tags: [design, dashboard, implementation, oberon, visual]
+---
+
+# Dashboard Implementation Spec
+
+Build contract for Oberon. Everything here is implementation-ready — copy-pasteable tokens, measurable specs, named components with data shapes. Design rationale is in the diagnostics-dashboard-visual-direction musing (git history, commit 29096deb); this file is the what, not the why.
+
+---
+
+## 1. Design Tokens (CSS Custom Properties)
+
+```css
+:root {
+  /* ── Background ── */
+  --bg-primary: #0D1117;
+  --bg-surface: #161B22;
+  --bg-elevated: #1C2128;
+  --bg-overlay: rgba(13, 17, 23, 0.85);
+
+  /* ── Text ── */
+  --text-primary: #E6EDF3;
+  --text-secondary: #8B949E;
+  --text-muted: #484F58;
+  --text-link: #58A6FF;
+
+  /* ── Borders ── */
+  --border-default: #21262D;
+  --border-subtle: #30363D;
+
+  /* ── Activity type colors (semantic — never use these for decoration) ── */
+  --color-extract: #58D5E3;    /* Cyan — pulling knowledge IN */
+  --color-new: #3FB950;        /* Green — new claims */
+  --color-enrich: #D4A72C;     /* Amber — strengthening existing */
+  --color-challenge: #F85149;  /* Red-orange — adversarial */
+  --color-decision: #A371F7;   /* Violet — governance */
+  --color-community: #6E7681;  /* Muted blue — external input */
+  --color-infra: #30363D;      /* Dark grey — ops */
+
+  /* ── Brand ── */
+  --color-brand: #6E46E5;
+  --color-brand-muted: rgba(110, 70, 229, 0.15);
+
+  /* ── Agent colors (for sparklines, attribution dots) ── */
+  --agent-leo: #D4AF37;
+  --agent-rio: #4A90D9;
+  --agent-clay: #9B59B6;
+  --agent-theseus: #E74C3C;
+  --agent-vida: #2ECC71;
+  --agent-astra: #F39C12;
+
+  /* ── Typography ── */
+  --font-mono: 'JetBrains Mono', 'IBM Plex Mono', 'Fira Code', monospace;
+  --font-size-xs: 10px;
+  --font-size-sm: 12px;
+  --font-size-base: 14px;
+  --font-size-lg: 18px;
+  --font-size-hero: 28px;
+  --line-height-tight: 1.2;
+  --line-height-normal: 1.5;
+
+  /* ── Spacing ── */
+  --space-1: 4px;
+  --space-2: 8px;
+  --space-3: 12px;
+  --space-4: 16px;
+  --space-5: 24px;
+  --space-6: 32px;
+  --space-8: 48px;
+
+  /* ── Layout ── */
+  --panel-radius: 6px;
+  --panel-padding: var(--space-5);
+  --gap-panels: var(--space-4);
+}
+```
+
+---
+
+## 2. Layout Grid
+
+```
+┌─────────────────────────────────────────────────────────────────────┐
+│  HEADER BAR (48px fixed)                                           │
+│  [Teleo Codex]              [7d | 30d | 90d | all]    [last sync]  │
+├───────────────────────────────────────┬─────────────────────────────┤
+│                                       │                             │
+│  TIMELINE PANEL (60%)                 │  SIDEBAR (40%)              │
+│  Stacked bar chart                    │                             │
+│  X: days, Y: activity count           │  ┌─────────────────────┐   │
+│  Color: activity type                 │  │ AGENT ACTIVITY (60%) │   │
+│                                       │  │ Sparklines per agent │   │
+│  Phase overlay (thin strip above)     │  │                     │   │
+│                                       │  └─────────────────────┘   │
+│                                       │                             │
+│                                       │  ┌─────────────────────┐   │
+│                                       │  │ HEALTH METRICS (40%)│   │
+│                                       │  │ 4 key numbers       │   │
+│                                       │  └─────────────────────┘   │
+│                                       │                             │
+├───────────────────────────────────────┴─────────────────────────────┤
+│  EVENT LOG (collapsible, 200px default height)                     │
+│  Recent PR merges, challenges, milestones — reverse chronological  │
+└─────────────────────────────────────────────────────────────────────┘
+```
+
+### CSS Grid Structure
+
+```css
+.dashboard {
+  display: grid;
+  grid-template-rows: 48px 1fr auto;
+  grid-template-columns: 60fr 40fr;
+  gap: var(--gap-panels);
+  height: 100vh;
+  padding: var(--space-4);
+  background: var(--bg-primary);
+  font-family: var(--font-mono);
+  color: var(--text-primary);
+}
+
+.header {
+  grid-column: 1 / -1;
+  display: flex;
+  align-items: center;
+  justify-content: space-between;
+  padding: 0 var(--space-4);
+  border-bottom: 1px solid var(--border-default);
+}
+
+.timeline-panel {
+  grid-column: 1;
+  grid-row: 2;
+  background: var(--bg-surface);
+  border-radius: var(--panel-radius);
+  padding: var(--panel-padding);
+  overflow: hidden;
+}
+
+.sidebar {
+  grid-column: 2;
+  grid-row: 2;
+  display: flex;
+  flex-direction: column;
+  gap: var(--gap-panels);
+}
+
+.event-log {
+  grid-column: 1 / -1;
+  grid-row: 3;
+  background: var(--bg-surface);
+  border-radius: var(--panel-radius);
+  padding: var(--panel-padding);
+  max-height: 200px;
+  overflow-y: auto;
+}
+```
+
+### Responsive Breakpoints
+
+| Viewport | Layout |
+|----------|--------|
+| >= 1200px | 2-column grid as shown above |
+| 768-1199px | Single column: timeline full-width, agent panel below, health metrics inline row |
+| < 768px | Skip — this is an ops tool, not designed for mobile |
+
+---
+
+## 3. Component Specs
+
+### 3.1 Timeline Panel (stacked bar chart)
+
+**Renders:** One bar per day. Segments stacked by activity type. Height proportional to daily activity count.
+
+**Data shape:**
+```typescript
+interface TimelineDay {
+  date: string;          // "2026-04-01"
+  extract: number;       // count of extraction commits
+  new_claims: number;    // new claim files added
+  enrich: number;        // existing claims modified
+  challenge: number;     // challenge claims or counter-evidence
+  decision: number;      // governance/evaluation events
+  community: number;     // external contributions
+  infra: number;         // ops/config changes
+}
+```
+
+**Bar rendering:**
+- Width: `(panel_width - padding) / days_shown` with 2px gap between bars
+- Height: proportional to sum of all segments, max bar = panel height - 40px (reserve for x-axis labels)
+- Stack order (bottom to top): infra, community, extract, new_claims, enrich, challenge, decision
+- Colors: corresponding `--color-*` tokens
+- Hover: tooltip showing date + breakdown
+
+**Phase overlay:** 8px tall strip above the bars. Color = phase. Phase 1 (bootstrap): `var(--color-brand-muted)`. Future phases TBD.
+
+**Time range selector:** 4 buttons in header area — 7d | 30d | 90d | all. Default: 30d. Active button: `border-bottom: 2px solid var(--color-brand)`.
+
+**Annotations:** Vertical dashed line at key events (e.g., "first external contribution"). Label rotated 90deg, `var(--text-muted)`, `var(--font-size-xs)`.
+
+### 3.2 Agent Activity Panel
+
+**Renders:** One row per agent, sorted by total activity last 7 days (most active first).
+
+**Data shape:**
+```typescript
+interface AgentActivity {
+  name: string;           // "rio"
+  display_name: string;   // "Rio"
+  color: string;          // var(--agent-rio) resolved hex
+  status: "active" | "idle";  // active if any commits in last 24h
+  sparkline: number[];    // 7 values, one per day (last 7 days)
+  total_claims: number;   // lifetime claim count
+  recent_claims: number;  // claims this week
+}
+```
+
+**Row layout:**
+```
+┌───────────────────────────────────────────────────────┐
+│ ● Rio          ▁▂▅█▃▁▂                    42 (+3)    │
+└───────────────────────────────────────────────────────┘
+```
+
+- Status dot: 8px circle, `var(--agent-*)` color if active, `var(--text-muted)` if idle
+- Name: `var(--font-size-base)`, `var(--text-primary)`
+- Sparkline: 7 bars, each 4px wide, 2px gap, max height 20px. Color: agent color
+- Claim count: `var(--font-size-sm)`, `var(--text-secondary)`. Delta in parentheses, green if positive
+
+**Row styling:**
+```css
+.agent-row {
+  display: flex;
+  align-items: center;
+  gap: var(--space-3);
+  padding: var(--space-2) var(--space-3);
+  border-radius: 4px;
+}
+.agent-row:hover {
+  background: var(--bg-elevated);
+}
+```
+
+### 3.3 Health Metrics Panel
+
+**Renders:** 4 metric cards in a 2x2 grid.
+
+**Data shape:**
+```typescript
+interface HealthMetrics {
+  total_claims: number;
+  claims_delta_week: number;     // change this week (+/-)
+  active_domains: number;
+  total_domains: number;
+  open_challenges: number;
+  unique_contributors_month: number;
+}
+```
+
+**Card layout:**
+```
+┌──────────────────┐
+│ Claims           │
+│ 412  +12         │
+└──────────────────┘
+```
+
+- Label: `var(--font-size-xs)`, `var(--text-muted)`, uppercase, `letter-spacing: 0.05em`
+- Value: `var(--font-size-hero)`, `var(--text-primary)`, `font-weight: 600`
+- Delta: `var(--font-size-sm)`, green if positive, red if negative, muted if zero
+
+**Card styling:**
+```css
+.metric-card {
+  background: var(--bg-surface);
+  border: 1px solid var(--border-default);
+  border-radius: var(--panel-radius);
+  padding: var(--space-4);
+}
+```
+
+**The 4 metrics:**
+1. **Claims** — `total_claims` + `claims_delta_week`
+2. **Domains** — `active_domains / total_domains` (e.g., "4/14")
+3. **Challenges** — `open_challenges` (red accent if > 0)
+4. **Contributors** — `unique_contributors_month`
+
+### 3.4 Event Log
+
+**Renders:** Reverse-chronological list of significant events (PR merges, challenges filed, milestones).
+
+**Data shape (reuse from extract-graph-data.py `events`):**
+```typescript
+interface Event {
+  type: "pr-merge" | "challenge" | "milestone";
+  number?: number;       // PR number
+  agent: string;
+  claims_added: number;
+  date: string;
+}
+```
+
+**Row layout:**
+```
+2026-04-01  ● rio    PR #2234 merged — 3 new claims (entertainment)
+2026-03-31  ● clay   Challenge filed — AI acceptance scope boundary
+```
+
+- Date: `var(--font-size-xs)`, `var(--text-muted)`, fixed width 80px
+- Agent dot: 6px, agent color
+- Description: `var(--font-size-sm)`, `var(--text-secondary)`
+- Activity type indicator: left border 3px solid, activity type color
+
+---
+
+## 4. Data Pipeline
+
+### Source
+
+The dashboard reads from **two JSON files** already produced by `ops/extract-graph-data.py`:
+
+1. **`graph-data.json`** — nodes (claims), edges (wiki-links), events (PR merges), domain_colors
+2. **`claims-context.json`** — lightweight claim index with domain/agent/confidence
+
+### Additional data needed (new script or extend existing)
+
+A new `ops/extract-dashboard-data.py` (or extend `extract-graph-data.py --dashboard`) that produces `dashboard-data.json`:
+
+```typescript
+interface DashboardData {
+  generated: string;                    // ISO timestamp
+  timeline: TimelineDay[];              // last 90 days
+  agents: AgentActivity[];              // per-agent summaries
+  health: HealthMetrics;                // 4 key numbers
+  events: Event[];                      // last 50 events
+  phase: { current: string; since: string; };
+}
+```
+
+**How to derive timeline data from git history:**
+- Parse `git log --format="%H|%s|%ai" --since="90 days ago"` 
+- Classify each commit by activity type using commit message prefix patterns:
+  - `{agent}: add N claims` → `new_claims`
+  - `{agent}: enrich` / `{agent}: update` → `enrich`
+  - `{agent}: challenge` → `challenge`
+  - `{agent}: extract` → `extract`
+  - Merge commits with `#N` → `decision`
+  - Other → `infra`
+- Bucket by date
+- This extends the existing `extract_events()` function in extract-graph-data.py
+
+### Deployment
+
+Static JSON files generated on push to main (same GitHub Actions workflow that already syncs graph-data.json to teleo-app). Dashboard page reads JSON on load. No API, no websockets.
+
+---
+
+## 5. Tech Stack
+
+| Choice | Rationale |
+|--------|-----------|
+| **Static HTML + vanilla JS** | Single page, no routing, no state management needed. Zero build step. |
+| **CSS Grid + custom properties** | Layout and theming covered by the tokens above. No CSS framework. |
+| **Chart rendering** | Two options: (a) CSS-only bars (div heights via `style="height: ${pct}%"`) for the stacked bars and sparklines — zero dependencies. (b) Chart.js if we want tooltips and animations without manual DOM work. Oberon's call — CSS-only is simpler, Chart.js is faster to iterate. |
+| **Font** | JetBrains Mono via Google Fonts CDN. Fallback: system monospace. |
+| **Dark mode only** | No toggle. `background: var(--bg-primary)` on body. |
+
+---
+
+## 6. File Structure
+
+```
+dashboard/
+├── index.html           # Single page
+├── style.css            # All styles (tokens + layout + components)
+├── dashboard.js         # Data loading + rendering
+└── data/                # Symlink to or copy of generated JSON
+    ├── dashboard-data.json
+    └── graph-data.json
+```
+
+Or integrate into teleo-app if Oberon prefers — the tokens and components work in any context.
+
+---
+
+## 7. Screenshot/Export Mode
+
+For social media use (the dual-use case from the visual direction musing):
+
+- A `?export=timeline` query param renders ONLY the timeline panel at 1200x630px (Twitter card size)
+- A `?export=agents` query param renders ONLY the agent sparklines at 800x400px
+- White-on-dark, no chrome, no header — just the data visualization
+- These URLs can be screenshotted by a cron job for automated social posts
+
+---
+
+## 8. What This Does NOT Cover
+
+- **Homepage graph + chat** — separate spec (homepage-visual-design.md), separate build
+- **Claim network visualization** — force-directed graph for storytelling, separate from ops dashboard
+- **Real-time updates** — static JSON is sufficient for current update frequency (~hourly)
+- **Authentication** — ops dashboard is internal, served behind VPN or localhost
+
+---
+
+## 9. Acceptance Criteria
+
+Oberon ships this when:
+1. Dashboard loads from static JSON and renders all 4 panels
+2. Time range selector switches between 7d/30d/90d/all
+3. Agent sparklines render and sort by activity
+4. Health metrics show current counts with weekly deltas
+5. Event log shows last 50 events reverse-chronologically
+6. Passes WCAG AA contrast ratios on all text (the token values above are pre-checked)
+7. Screenshot export mode produces clean 1200x630 timeline images
+
+---
+
+→ FLAG @oberon: This is the build contract. Everything above is implementation-ready. Questions about design rationale → see the visual direction musing (git commit 29096deb). Questions about data pipeline → the existing extract-graph-data.py is the starting point; extend it for the timeline/agent/health data shapes described in section 4.
+
+→ FLAG @leo: Spec complete. Covers tokens, grid, components, data pipeline, tech stack, acceptance criteria. This should unblock Oberon's frontend work.

agents/clay/musings/diagnostics-dashboard-visual-direction.md

@@ -0,0 +1,155 @@
+---
+type: musing
+agent: clay
+title: "Diagnostics dashboard visual direction"
+status: developing
+created: 2026-03-25
+updated: 2026-03-25
+tags: [design, visual, dashboard, communication]
+---
+
+# Diagnostics Dashboard Visual Direction
+
+Response to Leo's design request. Oberon builds, Argus architects, Clay provides visual direction. Also addresses Cory's broader ask: visual assets that communicate what the collective is doing.
+
+---
+
+## Design Philosophy
+
+**The dashboard should look like a Bloomberg terminal had a baby with a git log.** Dense, operational, zero decoration — but with enough visual structure that patterns are legible at a glance. The goal is: Cory opens this, looks for 3 seconds, and knows whether the collective is healthy, where activity is concentrating, and what phase we're in.
+
+**Reference points:**
+- Bloomberg terminal (information density, dark background, color as data)
+- GitHub contribution graph (the green squares — simple, temporal, pattern-revealing)
+- Grafana dashboards (metric panels, dark theme, no wasted space)
+- NOT: marketing dashboards, Notion pages, anything with rounded corners and gradients
+
+---
+
+## Color System
+
+Leo's suggestion (blue/green/yellow/red/purple/grey) is close but needs refinement. The problem with standard rainbow palettes: they don't have natural semantic associations, and they're hard to distinguish for colorblind users (~8% of men).
+
+### Proposed Palette (dark background: #0D1117)
+
+| Activity Type | Color | Hex | Rationale |
+|---|---|---|---|
+| **EXTRACT** | Cyan | `#58D5E3` | Cool — pulling knowledge IN from external sources |
+| **NEW** | Green | `#3FB950` | Growth — new claims added to the KB |
+| **ENRICH** | Amber | `#D4A72C` | Warm — strengthening existing knowledge |
+| **CHALLENGE** | Red-orange | `#F85149` | Hot — adversarial, testing existing claims |
+| **DECISION** | Violet | `#A371F7` | Distinct — governance/futarchy, different category entirely |
+| **TELEGRAM** | Muted blue | `#6E7681` | Subdued — community input, not agent-generated |
+| **INFRA** | Dark grey | `#30363D` | Background — necessary but not the story |
+
+### Design rules:
+- **Background:** Near-black (`#0D1117` — GitHub dark mode). Not pure black (too harsh).
+- **Text:** `#E6EDF3` primary, `#8B949E` secondary. No pure white.
+- **Borders/dividers:** `#21262D`. Barely visible. Structure through spacing, not lines.
+- **The color IS the data.** No legends needed if color usage is consistent. Cyan always means extraction. Green always means new knowledge. A user who sees the dashboard 3 times internalizes the system.
+
+### Colorblind safety:
+The cyan/green/amber/red palette is distinguishable under deuteranopia (the most common form). Violet is safe for all types. I'd test with a simulator but the key principle: no red-green adjacency without a shape or position differentiator.
+
+---
+
+## Layout: The Three Panels
+
+### Panel 1: Timeline (hero — 60% of viewport width)
+
+**Stacked bar chart, horizontal time axis.** Each bar = 1 day. Segments stacked by activity type (color-coded). Height = total commits/claims.
+
+**Why stacked bars, not lines:** Lines smooth over the actual data. Stacked bars show composition AND volume simultaneously. You see: "Tuesday was a big day and it was mostly extraction. Wednesday was quiet. Thursday was all challenges." That's the story.
+
+**X-axis:** Last 30 days by default. Zoom controls (7d / 30d / 90d / all).
+**Y-axis:** Commit count or claim count (toggle). No label needed — the bars communicate scale.
+
+**The phase narrative overlay:** A thin horizontal band above the timeline showing which PHASE the collective was in at each point. Phase 1 (bootstrap) = one color, Phase 2 (community) = another. This is the "where are we in the story" context layer.
+
+**Annotations:** Key events (PR milestones, new agents onboarded, first external contribution) as small markers on the timeline. Sparse — only structural events, not every merge.
+
+### Panel 2: Agent Activity (25% width, right column)
+
+**Vertical list of agents, each with a horizontal activity sparkline** (last 7 days). Sorted by recent activity — most active agent at top.
+
+Each agent row:
+```
+[colored dot: active/idle] Agent Name    ▁▂▅█▃▁▂  [claim count]
+```
+
+The sparkline shows activity pattern. A user sees instantly: "Rio has been busy all week. Clay went quiet Wednesday. Theseus had a spike yesterday."
+
+**Click to expand:** Shows that agent's recent commits, claims proposed, current task. But collapsed by default — the sparkline IS the information.
+
+### Panel 3: Health Metrics (15% width, far right or bottom strip)
+
+**Four numbers. That's it.**
+
+| Metric | What it shows |
+|---|---|
+| **Claims** | Total claim count + delta this week (+12) |
+| **Domains** | How many domains have activity this week (3/6) |
+| **Challenges** | Open challenges pending counter-evidence |
+| **Contributors** | Unique contributors this month |
+
+These are the vital signs. If Claims is growing, Domains is distributed, Challenges exist, and Contributors > 1, the collective is healthy. Any metric going to zero is a red flag visible in 1 second.
+
+---
+
+## Dual-Use: Dashboard → External Communication
+
+This is the interesting part. Three dashboard elements that work as social media posts:
+
+### 1. The Timeline Screenshot
+
+A cropped screenshot of the timeline panel — "Here's what 6 AI domain specialists produced this week" — is immediately shareable. The stacked bars tell a visual story. Color legend in the caption, not the image. This is the equivalent of GitHub's contribution graph: proof of work, visually legible.
+
+**Post format:** Timeline image + 2-3 sentence caption identifying the week's highlights. "This week the collective processed 47 sources, proposed 23 new claims, and survived 4 challenges. The red bar on Thursday? Someone tried to prove our futarchy thesis wrong. It held."
+
+### 2. The Agent Activity Sparklines
+
+Cropped sparklines with agent names — "Meet the team" format. Shows that these are distinct specialists with different activity patterns. The visual diversity (some agents spike, some are steady) communicates that they're not all doing the same thing.
+
+### 3. The Claim Network (not in the dashboard, but should be built)
+
+A force-directed graph of claims with wiki-links as edges. Color by domain. Size by structural importance (the PageRank score I proposed in the ontology review). This is the hero visual for external communication — it looks like a brain, it shows the knowledge structure, and every node is clickable.
+
+**This should be a separate page, not part of the ops dashboard.** The dashboard is for operators. The claim network is for storytelling. But they share the same data and color system.
+
+---
+
+## Typography
+
+- **Monospace everywhere.** JetBrains Mono or IBM Plex Mono. This is a terminal aesthetic, not a marketing site.
+- **Font sizes:** 12px body, 14px panel headers, 24px hero numbers. That's the entire scale.
+- **No bold except metric values.** Information hierarchy through size and color, not weight.
+
+---
+
+## Implementation Notes for Oberon
+
+1. **Static HTML + vanilla JS.** No framework needed. This is a single-page data display.
+2. **Data source:** JSON files generated from git history + claim frontmatter. Same pipeline that produces `contributors.json` and `graph-data.json`.
+3. **Chart library:** If needed, Chart.js or D3. But the stacked bars are simple enough to do with CSS grid + calculated heights if you want zero dependencies.
+4. **Refresh:** On page load from static JSON. No websockets, no polling. The data updates when someone pushes to main (~hourly at most).
+5. **Dark mode only.** No light mode toggle. This is an ops tool, not a consumer product.
+
+---
+
+## The Broader Visual Language
+
+Cory's ask: "Posts with pictures perform better. We need diagrams, we need art."
+
+The dashboard establishes a visual language that should extend to all Teleo visual communication:
+
+1. **Dark background, colored data.** The dark terminal aesthetic signals: "this is real infrastructure, not a pitch deck."
+2. **Color = meaning.** The activity type palette (cyan/green/amber/red/violet) becomes the brand palette. Every visual uses the same colors for the same concepts.
+3. **Information density over decoration.** Every pixel carries data. No stock photos, no gradient backgrounds, no decorative elements. The complexity of the information IS the visual.
+4. **Monospace type signals transparency.** "We're showing you the raw data, not a polished narrative." This is the visual equivalent of the epistemic honesty principle.
+
+**Three visual asset types to develop:**
+1. **Dashboard screenshots** — proof of collective activity (weekly cadence)
+2. **Claim network graphs** — the knowledge structure (monthly or on milestones)
+3. **Reasoning chain diagrams** — evidence → claim → belief → position for specific interesting cases (on-demand, for threads)
+
+→ CLAIM CANDIDATE: Dark terminal aesthetics in AI product communication signal operational seriousness and transparency, differentiating from the gradient-and-illustration style of consumer AI products.

core/contributor-guide.md

@@ -0,0 +1,66 @@
+# Contributor Guide
+
+Three concepts. That's it.
+
+## Claims
+
+A claim is a statement about how the world works, backed by evidence.
+
+> "Legacy media is consolidating into three dominant entities because debt-loaded incumbents cannot compete with cash-rich tech companies for content rights"
+
+Claims have confidence levels: proven, likely, experimental, speculative. Every claim cites its evidence. Every claim can be wrong.
+
+**Browse claims:** Look in `domains/{domain}/` — each domain has dozens of claims organized by topic. Start with whichever domain matches your expertise.
+
+## Challenges
+
+A challenge is a counter-argument against a specific claim.
+
+> "The AI content acceptance decline may be scope-bounded to entertainment — reference and analytical AI content shows no acceptance penalty"
+
+Challenges are the highest-value contribution. If you think a claim is wrong, too broad, or missing evidence, file a challenge. The claim author must respond — they can't ignore it.
+
+Three types:
+- **Full challenge** — the claim is wrong, here's why
+- **Scope challenge** — the claim is true in context X but not Y
+- **Evidence challenge** — the evidence doesn't support the confidence level
+
+**File a challenge:** Create a file in `domains/{domain}/challenge-{slug}.md` following the challenge schema, or tell an agent your counter-argument and they'll draft it for you.
+
+## Connections
+
+Connections are the links between claims. When claim A depends on claim B, or challenges claim C, those relationships form a knowledge graph.
+
+You don't create connections as standalone files — they emerge from wiki links (`[[claim-name]]`) in claim and challenge bodies. But spotting a connection no one else has seen is a genuine contribution. Cross-domain connections (a pattern in entertainment that also appears in finance) are the most valuable.
+
+**Spot a connection:** Tell an agent. They'll draft the cross-reference and attribute you.
+
+---
+
+## What You Don't Need to Know
+
+The system has 11 internal concept types (beliefs, positions, convictions, entities, sectors, sources, divergences, musings, attribution, contributors). Agents use these to organize their reasoning, track companies, and manage their workflow.
+
+You don't need to learn any of them. Claims, challenges, and connections are the complete interface for contributors. Everything else is infrastructure.
+
+## How Credit Works
+
+Every contribution is attributed. Your name stays on everything you produce or improve. The system tracks five roles:
+
+| Role | What you did |
+|------|-------------|
+| Sourcer | Pointed to material worth analyzing |
+| Extractor | Turned source material into a claim |
+| Challenger | Filed counter-evidence against a claim |
+| Synthesizer | Connected claims across domains |
+| Reviewer | Evaluated claim quality |
+
+You can hold multiple roles on the same claim. Credit is proportional to impact — a challenge that changes a high-importance claim earns more than a new speculative claim in an empty domain.
+
+## Getting Started
+
+1. **Browse:** Pick a domain. Read 5-10 claims. Find one you disagree with or know something about.
+2. **React:** Tell an agent your reaction. They'll help you figure out if it's a challenge, a new claim, or a connection.
+3. **Approve:** The agent drafts; you review and approve before anything gets published.
+
+Nothing enters the knowledge base without your explicit approval. The conversation itself is valuable even if you never file anything.

domains/entertainment/challenge-three-body-oligopoly-understates-original-ip-viability-in-prestige-adaptation-category.md

@@ -0,0 +1,71 @@
+---
+type: challenge
+target: "legacy media is consolidating into three surviving entities because the Warner-Paramount merger eliminates the fourth independent major and forecloses alternative industry structures"
+domain: entertainment
+description: "The three-body oligopoly thesis implies franchise IP dominates creative strategy, but the largest non-franchise opening of 2026 suggests prestige adaptations remain viable tentpole investments"
+status: open
+strength: moderate
+source: "Clay — analysis of Project Hail Mary theatrical performance vs consolidation thesis predictions"
+created: 2026-04-01
+resolved: null
+---
+
+# The three-body oligopoly thesis understates original IP viability in the prestige adaptation category
+
+## Target Claim
+
+[[legacy media is consolidating into three surviving entities because the Warner-Paramount merger eliminates the fourth independent major and forecloses alternative industry structures]] — Post-merger, legacy media resolves into Disney, Netflix, and Warner-Paramount, creating a three-body oligopoly with distinct structural profiles that forecloses alternative industry structures.
+
+**Current confidence:** likely
+
+## Counter-Evidence
+
+Project Hail Mary (2026) is the largest non-franchise opening of the year — a single-IP, author-driven prestige adaptation with no sequel infrastructure, no theme park tie-in, no merchandise ecosystem. It was greenlit as a tentpole-budget production based on source material quality and talent attachment alone.
+
+This performance challenges a specific implication of the three-body oligopoly thesis: that consolidated studios will optimize primarily for risk-minimized franchise IP because the economic logic of merger-driven debt loads demands predictable revenue streams. If that were fully true, tentpole-budget original adaptations would be the first casualty of consolidation — they carry franchise-level production costs without franchise-level floor guarantees.
+
+Key counter-evidence:
+- **Performance floor exceeded franchise comparables** — opening above several franchise sequels released in the same window, despite no built-in audience from prior installments
+- **Author-driven, not franchise-driven** — Andy Weir's readership is large but not franchise-scale; this is closer to "prestige bet" than "IP exploitation"
+- **Ryan Gosling attachment as risk mitigation** — talent-driven greenlighting (star power substituting for franchise recognition) is a different risk model than franchise IP, but it's not a dead model
+- **No sequel infrastructure** — standalone story, no cinematic universe setup, no announced follow-up. The investment thesis was "one great movie" not "franchise launch"
+
+## Scope of Challenge
+
+**Scope challenge** — the claim's structural analysis (consolidation into three entities) is correct, but the implied creative consequence (franchise IP dominates, original IP is foreclosed) is overstated. The oligopoly thesis describes market structure accurately; the creative strategy implications need a carve-out.
+
+Specifically: prestige adaptations with A-list talent attachment may function as a **fourth risk category** alongside franchise IP, sequel/prequel, and licensed remake. The three-body structure doesn't eliminate this category — it may actually concentrate it among the three survivors, who are the only entities with the capital to take tentpole-budget bets on non-franchise material.
+
+## Two Possible Resolutions
+
+1. **Exception that proves the rule:** Project Hail Mary was greenlit pre-merger under different risk calculus. As debt loads from the Warner-Paramount combination pressure the combined entity, tentpole-budget original adaptations get squeezed out in favor of IP with predictable floors. One hit doesn't disprove the structural trend — Hail Mary is the last of its kind, not the first of a new wave.
+
+2. **Scope refinement needed:** The oligopoly thesis accurately describes market structure but overgeneralizes to creative strategy. Consolidated studios still have capacity and incentive for prestige tentpoles because (a) they need awards-season credibility for talent retention, (b) star-driven original films serve a different audience segment than franchise IP, and (c) the occasional breakout original validates the studio's curatorial reputation. The creative foreclosure is real for mid-budget original IP, not tentpole prestige.
+
+## What This Would Change
+
+If accepted (scope refinement), the target claim would need:
+- An explicit carve-out noting that consolidation constrains mid-budget original IP more than tentpole prestige adaptations
+- The "forecloses alternative industry structures" language softened to "constrains" or "narrows"
+
+Downstream effects:
+- [[media consolidation reducing buyer competition for talent accelerates creator economy growth as an escape valve for displaced creative labor]] — talent displacement may be more selective than the current claim implies if prestige opportunities persist for A-list talent
+- [[the media attractor state is community-filtered IP with AI-collapsed production costs where content becomes a loss leader for the scarce complements of fandom community and ownership]] — the "alternative to consolidated media" framing is slightly weakened if consolidated media still produces high-quality original work
+
+## Resolution
+
+**Status:** open
+**Resolved:** null
+**Summary:** null
+
+---
+
+Relevant Notes:
+- [[legacy media is consolidating into three surviving entities because the Warner-Paramount merger eliminates the fourth independent major and forecloses alternative industry structures]] — target claim
+- [[media consolidation reducing buyer competition for talent accelerates creator economy growth as an escape valve for displaced creative labor]] — downstream: talent displacement selectivity
+- [[Warner-Paramount combined debt exceeding annual revenue creates structural fragility against cash-rich tech competitors regardless of IP library scale]] — the debt load that should pressure against original IP bets
+- [[the media attractor state is community-filtered IP with AI-collapsed production costs where content becomes a loss leader for the scarce complements of fandom community and ownership]] — alternative model contrast
+
+Topics:
+- [[web3 entertainment and creator economy]]
+- entertainment

domains/entertainment/legacy media is consolidating into three surviving entities because the Warner-Paramount merger eliminates the fourth independent major and forecloses alternative industry structures.md

@@ -9,7 +9,8 @@ created: 2026-04-01
 depends_on:
   - "media disruption follows two sequential phases as distribution moats fall first and creation moats fall second"
   - "streaming churn may be permanently uneconomic because maintenance marketing consumes up to half of average revenue per user"
-challenged_by: []
+challenged_by:
+  - "challenge-three-body-oligopoly-understates-original-ip-viability-in-prestige-adaptation-category"
 ---
 
 # Legacy media is consolidating into three surviving entities because the Warner-Paramount merger eliminates the fourth independent major and forecloses alternative industry structures

domains/entertainment/permissionless-operator-networks-scale-geographic-expansion-quadratically-by-removing-human-bottlenecks-from-market-entry.md

@@ -0,0 +1,17 @@
+---
+type: claim
+domain: entertainment
+description: When market entry shifts from centralized deployment to permissionless operator recruitment, the number of possible network connections grows quadratically with nodes, creating exponential expansion potential
+confidence: experimental
+source: P2P Protocol, Venezuela and Mexico launches at $400 vs Brazil at $40,000
+created: 2026-04-01
+title: Permissionless operator networks scale geographic expansion quadratically by removing human bottlenecks from market entry
+agent: clay
+scope: structural
+sourcer: "@p2pdotfound"
+related_claims: ["[[fanchise management is a stack of increasing fan engagement from content extensions through co-creation and co-ownership]]"]
+---
+
+# Permissionless operator networks scale geographic expansion quadratically by removing human bottlenecks from market entry
+
+P2P Protocol's shift from centralized to permissionless expansion demonstrates how removing human bottlenecks enables quadratic network growth. Traditional expansion required 45 days and $40,000 for Brazil with three people on the ground. The permissionless Circles of Trust model launched Venezuela in 15 days with $400 and no local team, then Mexico in 10 days at the same cost. The mechanism is structural: local operators stake capital, recruit merchants, and earn 0.2% of monthly volume their circle handles—compensation sits entirely outside protocol payroll. This creates a 100x cost reduction per market entry. The quadratic scaling emerges because each new country is not just one additional market but a new node in a network. Six countries produce 15 possible corridors, twenty countries produce 190, forty countries produce 780. The reference point is M-Pesa, which grew from 400 agents to over 300,000 in Kenya without building bank branches because agent setup cost hundreds of dollars versus over a million for branches. The protocol is building a fully permissionless version where anyone can create a circle, removing the last human bottleneck. This represents a 10-100x multiplier on market entry rate compared to the already-improved Circles model.

domains/entertainment/stablecoin-payment-networks-create-emergent-remittance-corridors-as-a-network-effect-not-as-designed-products.md

@@ -0,0 +1,16 @@
+---
+type: claim
+domain: entertainment
+description: Each new geographic node in a stablecoin payment network automatically creates remittance corridors to all existing nodes without requiring bilateral relationships or intermediary setup
+confidence: experimental
+source: P2P Protocol operating on UPI, PIX, and QRIS with 780 potential corridors at 40 countries
+created: 2026-04-01
+title: Stablecoin payment networks create emergent remittance corridors as a network effect not as designed products
+agent: clay
+scope: structural
+sourcer: "@p2pdotfound"
+---
+
+# Stablecoin payment networks create emergent remittance corridors as a network effect not as designed products
+
+P2P Protocol demonstrates how remittance corridors emerge as a network effect rather than requiring designed bilateral relationships. The protocol operates on UPI in India, PIX in Brazil, and QRIS in Indonesia—the three largest real-time payment systems by transaction volume globally. When a Circle Leader in Lagos connects to the same protocol as a Circle Leader in Jakarta, a Nigeria-Indonesia remittance corridor comes into existence automatically. No intermediary needed to set it up, no banking relationship required beyond what each operator already holds locally. The protocol handles matching, escrow, and settlement while operators handle local context. The math is structural: 40 countries produce 780 possible corridors. This addresses a $860 billion annual remittance market where the average cost to send $200 remains 6.49% according to the World Bank, implying $56 billion in annual fee extraction. The institutional positioning confirms the opportunity: Stripe acquired Bridge for $1.1 billion, Mastercard acquired BVNK for up to $1.8 billion. The IMF reported in December 2025 that stablecoin market capitalization tripled since 2023 to $260 billion and cross-border stablecoin flows now exceed Bitcoin and Ethereum combined. The mechanism is that geographic expansion creates corridors as a byproduct, not as a separate product development effort.

domains/health/Americas declining life expectancy is driven by deaths of despair concentrated in populations and regions most damaged by economic restructuring since the 1980s.md

@@ -34,17 +34,23 @@ This data powerfully validates [[the epidemiological transition marks the shift
 
 
 ### Additional Evidence (extend)
-*Source: [[2026-03-20-annals-internal-medicine-obbba-health-outcomes]] | Added: 2026-03-20*
+*Source: 2026-03-20-annals-internal-medicine-obbba-health-outcomes | Added: 2026-03-20*
 
 OBBBA adds a second mechanism for US life expectancy decline: policy-driven coverage loss (16,000+ preventable deaths annually, per Annals of Internal Medicine peer-reviewed study). This mechanism compounds deaths of despair because the populations losing Medicaid coverage heavily overlap with deaths-of-despair populations (rural, economically restructured regions). The mortality signal will appear in 2028-2030 data as a distinct but interacting pathway.
 
 ---
 
 ### Additional Evidence (extend)
-*Source: [[2026-03-10-abrams-bramajo-pnas-birth-cohort-mortality-us-life-expectancy]] | Added: 2026-03-24*
+*Source: 2026-03-10-abrams-bramajo-pnas-birth-cohort-mortality-us-life-expectancy | Added: 2026-03-24*
 
 PNAS 2026 cohort analysis shows the deaths-of-despair framing is incomplete: post-1970 US birth cohorts show mortality deterioration not just in external causes (overdoses, suicide) but also in cardiovascular disease and cancer simultaneously. The problem is multi-causal across all three major cause categories, not primarily driven by external causes.
 
+### Additional Evidence (extend)
+*Source: [[2025-05-01-jama-cardiology-cardia-food-insecurity-incident-cvd-midlife]] | Added: 2026-04-01*
+
+Food insecurity functions as a co-mechanism in the deaths of despair pathway. CARDIA study shows 41% elevated CVD risk from food insecurity in young adulthood, independent of income/education, suggesting nutritional pathways (not just economic deprivation) drive cardiovascular mortality in economically damaged populations.
+
+
 
 Relevant Notes:
 - [[the epidemiological transition marks the shift from material scarcity to social disadvantage as the primary driver of health outcomes in developed nations]] -- the US life expectancy reversal is the most dramatic empirical confirmation of this claim

domains/health/CMS is creating AI-specific reimbursement codes which will formalize a two-speed adoption system where proven AI applications get payment parity while experimental ones remain in cash-pay limbo.md

@@ -35,6 +35,12 @@ The investment implication: companies positioned at the category I boundary —
 
 TEMPO + CMS ACCESS model formalizes a two-speed system at an earlier stage: pre-clearance devices get Medicare reimbursement through ACCESS while collecting evidence, versus cleared devices with standard coverage. This creates a research-to-reimbursement pathway that didn't exist before January 2026, but scale is limited to ~10 manufacturers per clinical area.
 
+### Additional Evidence (extend)
+*Source: [[2026-04-01-fda-tempo-cms-access-selection-pending-july-performance-period]] | Added: 2026-04-01*
+
+TEMPO + ACCESS coordination demonstrates the two-speed system in practice: Medicare beneficiaries (65+) gain access to FDA-approved digital health devices through TEMPO while Medicaid populations face coverage contraction. The ACCESS model's July 1, 2026 performance period start creates a defined timeline for when Medicare digital health infrastructure becomes operational, while no equivalent pathway exists for Medicaid populations.
+
+
 
 Relevant Notes:
 - [[healthcare AI regulation needs blank-sheet redesign because the FDA drug-and-device model built for static products cannot govern continuously learning software]] — the static-code problem applies to CMS as well as FDA

domains/health/SDOH interventions show strong ROI but adoption stalls because Z-code documentation remains below 3 percent and no operational infrastructure connects screening to action.md

@@ -19,42 +19,48 @@ The near-term trajectory: mandatory outpatient screening by 2026, Z-code adoptio
 
 
 ### Additional Evidence (extend)
-*Source: [[2024-09-19-commonwealth-fund-mirror-mirror-2024]] | Added: 2026-03-12 | Extractor: anthropic/claude-sonnet-4.5*
+*Source: 2024-09-19-commonwealth-fund-mirror-mirror-2024 | Added: 2026-03-12 | Extractor: anthropic/claude-sonnet-4.5*
 
 The Commonwealth Fund's 2024 international comparison provides quantified evidence of the population-level cost of not operationalizing SDOH interventions at scale. The US ranks second-worst on equity (9th of 10 countries) and last on health outcomes (10th of 10), with the highest healthcare spending (>16% of GDP). This outcome gap relative to peer nations with lower spending demonstrates the opportunity cost of the US healthcare system's failure to systematically address social determinants. Countries with better equity and access outcomes (Australia, Netherlands) achieve superior population health despite similar or lower clinical quality and lower spending ratios. The international comparison quantifies what the SDOH adoption gap costs: the US achieves worst population health outcomes among wealthy peer nations despite world-class clinical care, suggesting that the 3% Z-code documentation rate represents billions in foregone health gains.
 
 
 ### Additional Evidence (challenge)
-*Source: [[2025-04-07-tufts-health-affairs-medically-tailored-meals-50-states]] | Added: 2026-03-18*
+*Source: 2025-04-07-tufts-health-affairs-medically-tailored-meals-50-states | Added: 2026-03-18*
 
 The JAMA Internal Medicine 2024 RCT testing intensive food-as-medicine intervention (10 meals/week + education + coaching for 1 year) found NO significant difference in HbA1c, hospitalization, ED use, or total claims between treatment and control groups. This challenges the assumption that SDOH interventions produce strong ROI—the RCT evidence shows null clinical outcomes despite addressing food insecurity directly.
 
 
 ### Additional Evidence (extend)
-*Source: [[2025-09-01-lancet-public-health-social-prescribing-england-national-rollout]] | Added: 2026-03-18*
+*Source: 2025-09-01-lancet-public-health-social-prescribing-england-national-rollout | Added: 2026-03-18*
 
 England's social prescribing provides international counterpoint: 1.3M annual referrals with 3,300 link workers represents the operational infrastructure that US SDOH interventions lack. However, UK achieved scale without evidence quality - 15 of 17 economic studies were uncontrolled, 38% attrition, SROI ratios of £1.17-£7.08 but ROI only 0.11-0.43. This suggests infrastructure alone is insufficient without measurement systems.
 
 
 ### Additional Evidence (extend)
-*Source: [[2025-01-01-nashp-chw-state-policies-2024-2025]] | Added: 2026-03-18*
+*Source: 2025-01-01-nashp-chw-state-policies-2024-2025 | Added: 2026-03-18*
 
 Community health worker programs demonstrate the same payment boundary stall: only 20 states have Medicaid State Plan Amendments for CHW reimbursement 17 years after Minnesota's 2008 approval, despite 39 RCTs showing $2.47 ROI. The billing infrastructure bottleneck is identical to Z-code documentation failure — SPAs typically use 9896x CPT codes but uptake remains slow because community-based organizations lack contracting infrastructure and Medicaid does not cover provider travel costs (the largest CHW overhead expense). 7 states have established dedicated CHW offices and 6 enacted new reimbursement legislation in 2024-2025, but the gap between evidence (strong) and operational infrastructure (absent) mirrors the SDOH screening-to-action gap.
 
 
 ### Additional Evidence (challenge)
-*Source: [[2025-01-01-produce-prescriptions-diabetes-care-critique]] | Added: 2026-03-18*
+*Source: 2025-01-01-produce-prescriptions-diabetes-care-critique | Added: 2026-03-18*
 
 The Diabetes Care perspective challenges the 'strong ROI' claim for SDOH interventions by questioning whether produce prescriptions—a specific SDOH intervention—actually produce clinical outcomes. The observational evidence showing improvements may reflect methodological artifacts (self-selection, regression to mean) rather than true causal effects. This suggests the ROI evidence for SDOH interventions may be weaker than claimed, particularly for single-factor interventions like food provision.
 
 
 ### Additional Evidence (challenge)
-*Source: [[2026-03-20-ccf-second-reconciliation-bill-healthcare-cuts-2026]] | Added: 2026-03-20*
+*Source: 2026-03-20-ccf-second-reconciliation-bill-healthcare-cuts-2026 | Added: 2026-03-20*
 
 The RSC's second reconciliation bill proposes site-neutral payments that would eliminate the enhanced FQHC reimbursement rates (~$300/visit vs ~$100/visit) that fund CHW programs. Combined with OBBBA's Medicaid cuts, this creates a two-vector attack on the institutional infrastructure that hosts most CHW programs. The challenge is not just documentation and operational infrastructure—the payment foundation itself is under legislative threat. Even if Z-code documentation improved and operational infrastructure was built, the revenue model that makes CHW programs economically viable within FQHCs would be eliminated by site-neutral payments.
 
 ---
 
+### Additional Evidence (extend)
+*Source: [[2025-05-01-jama-cardiology-cardia-food-insecurity-incident-cvd-midlife]] | Added: 2026-04-01*
+
+Northwestern Medicine researchers recommend integrating food insecurity screening into clinical CVD risk assessment based on CARDIA evidence showing 41% elevated risk. This creates a specific clinical use case for SDOH screening with clear downstream disease prevention rationale, potentially strengthening the case for Z-code adoption in cardiology.
+
+
 Relevant Notes:
 - [[value-based care transitions stall at the payment boundary because 60 percent of payments touch value metrics but only 14 percent bear full risk]] -- SDOH is the most acute case of the VBC implementation gap
 - [[social isolation costs Medicare 7 billion annually and carries mortality risk equivalent to smoking 15 cigarettes per day making loneliness a clinical condition not a personal problem]] -- loneliness as the most dramatic SDOH factor

domains/health/five-adverse-sdoh-independently-predict-hypertension-risk-food-insecurity-unemployment-poverty-low-education-inadequate-insurance.md

@@ -20,6 +20,12 @@ A systematic review published in *Hypertension* (AHA journal) analyzed 10,608 re
 
 ---
 
+### Additional Evidence (extend)
+*Source: [[2025-05-01-jama-cardiology-cardia-food-insecurity-incident-cvd-midlife]] | Added: 2026-04-01*
+
+CARDIA prospective cohort (N=3,616, 20-year follow-up) shows food insecurity at age 40 predicts 41% higher CVD incidence by age 60, with effect persisting after adjustment for income and education. This establishes temporality: food insecurity → CVD, not just correlation. The mechanism likely operates through the UPF-inflammation-hypertension pathway since the effect is independent of general socioeconomic status.
+
+
 Relevant Notes:
 - hypertension-related-cvd-mortality-doubled-2000-2023-despite-available-treatment-indicating-behavioral-sdoh-failure.md
 - only-23-percent-of-treated-us-hypertensives-achieve-blood-pressure-control-demonstrating-pharmacological-availability-is-not-the-binding-constraint.md

domains/health/food-as-medicine-interventions-produce-clinically-significant-improvements-during-active-delivery-but-benefits-fully-revert-when-structural-food-environment-support-is-removed.md

@@ -0,0 +1,33 @@
+---
+type: claim
+domain: health
+description: RCT evidence showing complete reversion to baseline 6 months after program ended demonstrates that dietary interventions cannot overcome unchanged structural food environments
+confidence: experimental
+source: Stephen Juraschek et al., AHA 2025 Scientific Sessions, 12-week RCT with 6-month follow-up
+created: 2026-04-01
+attribution:
+  extractor:
+    - handle: "vida"
+  sourcer:
+    - handle: "stat-news-/-stephen-juraschek"
+      context: "Stephen Juraschek et al., AHA 2025 Scientific Sessions, 12-week RCT with 6-month follow-up"
+---
+
+# Food-as-medicine interventions produce clinically significant BP and LDL improvements during active delivery but benefits fully revert to baseline when structural food environment support is removed, confirming the food environment as the proximate disease-generating mechanism rather than a modifiable behavioral choice
+
+A randomized controlled trial presented at AHA 2025 examined DASH-style grocery delivery plus dietitian support versus cash stipends in food-insecure Black adults in Boston. During the 12-week active intervention, the groceries + dietitian arm showed statistically significant BP improvement and LDL cholesterol reduction compared to stipend-only control. This confirms the causal pathway: dietary change → BP improvement works when the food environment is controlled.
+
+The critical finding is durability failure: Six months after grocery deliveries and stipends stopped, both blood pressure AND LDL cholesterol had returned completely to baseline levels. Not partial reversion—full return to pre-intervention values. As lead researcher Stephen Juraschek stated: 'We did not build grocery stores in the communities that our participants were living in. We did not make the groceries cheaper for people after they were free during the intervention.'
+
+This is mechanistic confirmation that the food environment doesn't just generate disease initially—it continuously regenerates it. When participants returned to the same food-insecure neighborhoods with unchanged food access, the disease pathway reactivated completely. The intervention proved the causal mechanism works, but also proved that episodic food assistance is insufficient without structural food environment change. The food environment is the system that overrides individual interventions when support is removed.
+
+---
+
+Relevant Notes:
+- [[five-adverse-sdoh-independently-predict-hypertension-risk-food-insecurity-unemployment-poverty-low-education-inadequate-insurance]]
+- [[food-insecurity-independently-predicts-41-percent-higher-cvd-incidence-establishing-temporality-for-sdoh-cardiovascular-pathway]]
+- [[only-23-percent-of-treated-us-hypertensives-achieve-blood-pressure-control-demonstrating-pharmacological-availability-is-not-the-binding-constraint]]
+- [[medical care explains only 10-20 percent of health outcomes because behavioral social and genetic factors dominate as four independent methodologies confirm]]
+
+Topics:
+- [[_map]]

domains/health/food-insecurity-independently-predicts-41-percent-higher-cvd-incidence-establishing-temporality-for-sdoh-cardiovascular-pathway.md

@@ -0,0 +1,36 @@
+---
+type: claim
+domain: health
+description: First prospective cohort evidence showing food insecurity precedes CVD development by 20 years, proving causal direction rather than mere correlation
+confidence: proven
+source: CARDIA Study Group / Northwestern Medicine, JAMA Cardiology 2025, 3,616 participants followed 2000-2020
+created: 2026-04-01
+attribution:
+  extractor:
+    - handle: "vida"
+  sourcer:
+    - handle: "northwestern-medicine-/-cardia-study-group"
+      context: "CARDIA Study Group / Northwestern Medicine, JAMA Cardiology 2025, 3,616 participants followed 2000-2020"
+---
+
+# Food insecurity in young adulthood independently predicts 41% higher CVD incidence in midlife after adjustment for socioeconomic factors, establishing temporality for the SDOH → cardiovascular disease pathway
+
+The CARDIA prospective cohort study followed 3,616 US adults without preexisting CVD from 2000 to 2020 (mean baseline age 40.1 years, 56% female, 47% Black). Food insecurity at baseline was associated with HR 1.41 for incident CVD after adjustment for income, education, and employment. This is the first prospective study establishing temporality—food insecurity comes first, CVD follows 20 years later. Prior studies were cross-sectional and could not distinguish whether food insecurity caused CVD or whether CVD-related disability caused food insecurity. The persistence of the association after socioeconomic adjustment suggests food insecurity operates through specific nutritional pathways (likely the UPF-inflammation-hypertension chain documented in Session 16) rather than only through general poverty effects. The 47% Black composition addresses the population most affected by both food insecurity and CVD disparities. Authors recommend integrating food insecurity screening into clinical CVD risk assessment, stating 'If we address food insecurity early, we may be able to reduce the burden of heart disease later.' This provides the upstream causal evidence that the entire food-environment thread has been building toward.
+
+---
+
+### Additional Evidence (extend)
+*Source: [[2025-11-10-statnews-aha-food-is-medicine-bp-reverts-to-baseline-juraschek]] | Added: 2026-04-01*
+
+AHA 2025 RCT showed that eliminating food insecurity through DASH grocery delivery + dietitian support produced significant BP and LDL improvements during 12-week intervention, but both reverted completely to baseline 6 months after program ended. This extends the observational food insecurity → CVD pathway with experimental evidence showing the mechanism is reversible during active intervention but requires continuous structural support.
+
+
+Relevant Notes:
+- [[Americas declining life expectancy is driven by deaths of despair concentrated in populations and regions most damaged by economic restructuring since the 1980s]]
+- [[Big Food companies engineer addictive products by hacking evolutionary reward pathways creating a noncommunicable disease epidemic more deadly than the famines specialization eliminated]]
+- medical care explains only 10-20 percent of health outcomes because behavioral social and genetic factors dominate
+- [[five-adverse-sdoh-independently-predict-hypertension-risk-food-insecurity-unemployment-poverty-low-education-inadequate-insurance]]
+- [[hypertension-related-cvd-mortality-doubled-2000-2023-despite-available-treatment-indicating-behavioral-sdoh-failure]]
+
+Topics:
+- [[_map]]

domains/health/medically-tailored-meals-achieve-pharmacotherapy-scale-bp-reduction-in-food-insecure-hypertensive-patients.md

@@ -0,0 +1,17 @@
+---
+type: claim
+domain: health
+description: "Kentucky pilot study shows MTM and grocery prescription interventions achieve BP reductions (MTM: -9.67 mmHg, grocery: -6.89 mmHg) that match or exceed standard antihypertensive medications (-5 to -10 mmHg range)"
+confidence: experimental
+source: UK HealthCare + Appalachian Regional Healthcare pilot study, medRxiv preprint 2025-07-09
+created: 2026-04-01
+title: Medically tailored meals produce -9.67 mmHg systolic BP reductions in food-insecure hypertensive patients — comparable to first-line pharmacotherapy — suggesting dietary intervention at the level of structural food access is a clinical-grade treatment for hypertension
+agent: vida
+scope: causal
+sourcer: UK HealthCare + Appalachian Regional Healthcare
+related_claims: ["[[SDOH interventions show strong ROI but adoption stalls because Z-code documentation remains below 3 percent and no operational infrastructure connects screening to action]]", "[[value-based care transitions stall at the payment boundary because 60 percent of payments touch value metrics but only 14 percent bear full risk]]", "[[GLP-1 receptor agonists are the largest therapeutic category launch in pharmaceutical history but their chronic use model makes the net cost impact inflationary through 2035]]"]
+---
+
+# Medically tailored meals produce -9.67 mmHg systolic BP reductions in food-insecure hypertensive patients — comparable to first-line pharmacotherapy — suggesting dietary intervention at the level of structural food access is a clinical-grade treatment for hypertension
+
+The Kentucky MTM pilot enrolled 75 food-insecure hypertensive adults across urban (UK HealthCare) and rural (Appalachian Regional Healthcare) sites. The medically tailored meals arm (5 meals/week for 12 weeks) produced -9.67 mmHg systolic BP reduction, while the grocery prescription arm ($100/month for 3 months) produced -6.89 mmHg reduction. Both exceed the 5 mmHg clinical significance threshold. Critically, these reductions fall within or exceed the -5 to -10 mmHg range typical of first-line antihypertensive pharmacotherapy. This suggests that addressing food insecurity through structured food access interventions operates as a clinical-grade treatment mechanism, not merely a lifestyle support. The effect size is particularly notable because it achieves pharmacotherapy-scale outcomes without adding a prescription drug. The mechanism appears to be direct: providing hypertension-appropriate food to food-insecure patients removes the structural barrier (lack of access to appropriate food) that prevents dietary adherence. This is distinct from education-based interventions, which assume food access exists but knowledge is lacking. The study's two-arm design also reveals a dose-response relationship: fully prepared meals (-9.67 mmHg) outperform grocery purchasing power (-6.89 mmHg), suggesting that removing both financial AND preparation barriers maximizes the effect. Important limitation: this is a 12-week pilot without durability data. The AHA Boston Food is Medicine study showed similar acute effects but full reversion by 6 months post-intervention, indicating the effect may require continuous delivery.

domains/health/only-23-percent-of-treated-us-hypertensives-achieve-blood-pressure-control-demonstrating-pharmacological-availability-is-not-the-binding-constraint.md

@@ -38,6 +38,12 @@ Digital health is frequently proposed as a solution to the hypertension control
 
 The systematic review establishes that the binding constraints are SDOH-mediated: housing instability affects treatment adherence, transportation barriers prevent care access, food insecurity directly increases hypertension prevalence, and insurance gaps reduce BP control. The review endorses CMS's HRSN screening tool (housing, food, transportation, utilities, safety) as a necessary hypertension care component.
 
+### Additional Evidence (confirm)
+*Source: [[2025-11-10-statnews-aha-food-is-medicine-bp-reverts-to-baseline-juraschek]] | Added: 2026-04-01*
+
+Boston food-as-medicine RCT achieved BP improvement during active 12-week intervention but complete reversion to baseline 6 months post-program, confirming that the binding constraint is structural food environment, not medication availability or patient knowledge. Even when dietary intervention works during active delivery, unchanged food environment regenerates disease.
+
+
 
 
 

domains/health/rural-food-insecure-populations-show-higher-enrollment-in-food-assistance-interventions-than-urban-counterparts.md

@@ -0,0 +1,17 @@
+---
+type: claim
+domain: health
+description: "Appalachian rural site achieved 81% enrollment rate compared to 53% at urban Lexington site in the same MTM pilot study"
+confidence: experimental
+source: Kentucky MTM pilot, UK HealthCare vs. Appalachian Regional Healthcare enrollment comparison
+created: 2026-04-01
+title: Rural food-insecure populations enrolled in food assistance interventions at 81 percent versus 53 percent in urban settings, suggesting rural populations may be more receptive to food-based health interventions due to more severe baseline food access constraints
+agent: vida
+scope: correlational
+sourcer: UK HealthCare + Appalachian Regional Healthcare
+related_claims: ["[[SDOH interventions show strong ROI but adoption stalls because Z-code documentation remains below 3 percent and no operational infrastructure connects screening to action]]"]
+---
+
+# Rural food-insecure populations enrolled in food assistance interventions at 81 percent versus 53 percent in urban settings, suggesting rural populations may be more receptive to food-based health interventions due to more severe baseline food access constraints
+
+The Kentucky pilot's two-site design revealed a striking enrollment disparity: Appalachian Regional Healthcare (rural) enrolled 26 of 32 referred patients (81%), while UK HealthCare (urban Lexington) enrolled 49 of 92 referred patients (53%). This 28-percentage-point gap suggests rural food-insecure populations may be substantially more receptive to food assistance interventions. The likely mechanism: rural Appalachian food access is more severely constrained due to geographic isolation, limited grocery infrastructure, and transportation barriers. When offered a food intervention, rural participants may recognize its direct value more immediately because their baseline food access is worse. This challenges the common assumption that urban populations are easier to reach for health interventions due to proximity and infrastructure. For food-specific interventions, the opposite may be true: rural populations face more severe food access constraints and therefore show higher engagement when those constraints are directly addressed. This has significant implications for targeting food-as-medicine programs — rural deployment may achieve better enrollment and engagement despite higher logistical delivery costs. The finding also suggests that rural health disparities in diet-sensitive conditions (hypertension, diabetes, cardiovascular disease) may be particularly amenable to food access interventions because the structural barrier is more severe and the intervention addresses the root constraint directly.

domains/health/snap-benefit-loss-causes-measurable-mortality-through-food-insecurity-pathway.md

@@ -0,0 +1,17 @@
+---
+type: claim
+domain: health
+description: Penn LDI projects 93,000 premature deaths from OBBBA SNAP cuts by applying empirically-derived mortality rates to CBO's 3.2 million coverage loss estimate
+confidence: experimental
+source: Penn LDI, CBO headcount projection, peer-reviewed SNAP mortality research
+created: 2026-04-01
+title: SNAP benefit loss causes measurable mortality increases in under-65 populations through food insecurity pathways with peer-reviewed rate estimates of 2.9 percent excess deaths over 14 years
+agent: vida
+scope: causal
+sourcer: Penn LDI (Leonard Davis Institute of Health Economics)
+related_claims: ["[[SDOH interventions show strong ROI but adoption stalls because Z-code documentation remains below 3 percent and no operational infrastructure connects screening to action]]", "[[medical care explains only 10-20 percent of health outcomes because behavioral social and genetic factors dominate as four independent methodologies confirm]]"]
+---
+
+# SNAP benefit loss causes measurable mortality increases in under-65 populations through food insecurity pathways with peer-reviewed rate estimates of 2.9 percent excess deaths over 14 years
+
+Penn Leonard Davis Institute researchers project 93,000 premature deaths between 2025-2039 from SNAP provisions in the One Big Beautiful Bill Act using a transparent methodology: CBO projects 3.2 million people under 65 will lose SNAP benefits; peer-reviewed research quantifies mortality rates comparing similar populations WITH vs. WITHOUT SNAP over 14 years; applying these rates to the CBO headcount yields the 93,000 estimate (approximately 2.9% excess mortality rate over 14 years, or ~6,600 additional deaths annually). The methodology's strength is its transparency and grounding in empirical research rather than black-box modeling. Prior LDI research establishes SNAP's protective mechanisms: lower diabetes prevalence and reduced heart disease deaths. The 14-year projection window matches the observation period in the underlying mortality research, providing methodological consistency. This translates abstract SNAP-health evidence into concrete policy mortality stakes at scale comparable to doubling annual US road fatalities. Uncertainty sources include: long projection window allows policy changes, mortality rates may differ from base research population, and modeling assumptions about benefit loss duration and intensity.

domains/health/snap-reduces-antihypertensive-nonadherence-through-food-medication-trade-off-relief.md

@@ -0,0 +1,17 @@
+---
+type: claim
+domain: health
+description: The effect specificity to food-insecure populations validates that SNAP operates through relieving competing expenditure pressure rather than general health improvement
+confidence: likely
+source: JAMA Network Open, February 2024, retrospective cohort study of 6,692 hypertensive patients using linked MEPS-NHIS data 2016-2017
+created: 2026-04-01
+title: SNAP receipt reduces antihypertensive medication nonadherence by 13.6 percentage points in food-insecure hypertensive patients but has no effect in food-secure patients, establishing the food-medication trade-off as a specific SDOH mechanism
+agent: vida
+scope: causal
+sourcer: JAMA Network Open
+related_claims: ["[[SDOH interventions show strong ROI but adoption stalls because Z-code documentation remains below 3 percent and no operational infrastructure connects screening to action]]", "[[value-based care transitions stall at the payment boundary because 60 percent of payments touch value metrics but only 14 percent bear full risk]]", "[[medical care explains only 10-20 percent of health outcomes because behavioral social and genetic factors dominate as four independent methodologies confirm]]"]
+---
+
+# SNAP receipt reduces antihypertensive medication nonadherence by 13.6 percentage points in food-insecure hypertensive patients but has no effect in food-secure patients, establishing the food-medication trade-off as a specific SDOH mechanism
+
+Among food-insecure patients with hypertension, SNAP receipt was associated with a 13.6 percentage point reduction in nonadherence to antihypertensive medications (8.17 pp difference between SNAP recipients vs. non-recipients in the food-insecure group). Critically, SNAP showed NO association with improved adherence in the food-secure population. This dose-response specificity validates the mechanism: SNAP relieves the competing expenditure pressure between purchasing food and purchasing medications. In food-insecure households, medication adherence is reduced when food costs create budget pressure. SNAP provides food purchasing power, freeing income for medications. This is a distinct pathway from dietary improvement mechanisms studied in Food is Medicine programs—SNAP here operates through financial trade-off relief, not nutritional change. The mechanism only operates when food insecurity is present, explaining why the effect disappears in food-secure populations. While this study measures adherence rather than blood pressure directly, medication nonadherence is the primary determinant of treatment-resistant hypertension, suggesting this 13.6 pp improvement would translate to significant BP control improvements.

domains/health/tempo-pilot-creates-medicare-digital-health-pathway-while-medicaid-coverage-contracts.md

@@ -26,6 +26,12 @@ The equity dimension is revealing: CMS ACCESS includes rural patient adjustments
 
 ---
 
+### Additional Evidence (extend)
+*Source: [[2026-04-01-fda-tempo-cms-access-selection-pending-july-performance-period]] | Added: 2026-04-01*
+
+TEMPO manufacturer selection remains pending as of April 1, 2026, two months after statements of interest closed. CMS ACCESS model applications were due April 1, 2026 with first performance period July 1, 2026. This creates a chicken-and-egg problem: healthcare systems applying to ACCESS must do so without knowing which TEMPO-approved devices they can deploy. The July 1 start date creates operational urgency for TEMPO selection in April/May 2026.
+
+
 Relevant Notes:
 - only-23-percent-of-treated-us-hypertensives-achieve-blood-pressure-control-demonstrating-pharmacological-availability-is-not-the-binding-constraint.md
 - hypertension-related-cvd-mortality-doubled-2000-2023-despite-available-treatment-indicating-behavioral-sdoh-failure.md

entities/entertainment/p2p-protocol.md

@@ -0,0 +1,37 @@
+---
+type: entity
+entity_type: protocol
+name: P2P Protocol
+domain: entertainment
+status: active
+founded: ~2023
+headquarters: Unknown
+key_people: []
+website: 
+twitter: "@p2pdotfound"
+---
+
+# P2P Protocol
+
+## Overview
+
+P2P Protocol is a stablecoin-based payment infrastructure enabling local currency to stablecoin conversion across multiple countries. The protocol operates on major real-time payment systems including UPI (India), PIX (Brazil), and QRIS (Indonesia).
+
+## Business Model
+
+The protocol uses a "Circles of Trust" model where local operators stake capital, recruit merchants, and earn 0.2% of monthly volume their circle handles. This creates permissionless geographic expansion without requiring centralized team deployment.
+
+## Products
+
+- **Coins.me**: Crypto neo-bank built on P2P Protocol offering USD-denominated stablecoin savings (5-10% yield through Morpho), on/off-ramp, global send/receive, cross-chain bridging, token swaps, and scan-to-pay functionality.
+
+## Timeline
+
+- **2023** — Protocol launched, began operations
+- **~2024** — Brazil launch: 45 days, 3 people, $40,000 investment
+- **~2024** — Argentina launch: 30 days, 2 people, $20,000 investment
+- **Early 2026** — Venezuela launch: 15 days, no local team, $400 investment using Circles of Trust model
+- **Early 2026** — Mexico launch: 10 days, $400 investment
+- **2026-03-30** — Announced expansion to 16 countries in pipeline (Colombia, Peru, Costa Rica, Uruguay, Paraguay, Ecuador, Bolivia, Nigeria, Philippines, Thailand, Vietnam, Portugal, Spain, Turkey, Egypt, Kenya) with target of 40 countries within 18 months
+- **2026-03-30** — Announced opensourcing of protocol SDK for third-party integration
+- **2026-03-30** — Operating across 6 countries with team of 25 people spanning 5 nationalities and 7 languages

inbox/archive/2026-03-30-futardio-proposal-1-go-big-or-go-home.md

@@ -0,0 +1,126 @@
+---
+type: source
+title: "Futardio: #1 - Go Big Or Go Home"
+author: "futard.io"
+url: "https://www.metadao.fi/projects/avici/proposal/6UimhcMfgLM3fH3rxqXgLxs6cJwmfGLCLQEZG9jjA3Ry"
+date: 2026-03-30
+domain: internet-finance
+format: data
+status: unprocessed
+tags: [futarchy, solana, governance, avici]
+event_type: proposal
+---
+
+## Proposal Details
+- Project: Avici
+- Proposal: #1 - Go Big Or Go Home
+- Status: Draft
+- Created: 2026-03-30
+- URL: https://www.metadao.fi/projects/avici/proposal/6UimhcMfgLM3fH3rxqXgLxs6cJwmfGLCLQEZG9jjA3Ry
+- Description: Authorizes the creation of the team performance package
+
+## Content
+
+# Align The Core team
+
+# Summary
+
+We are proposing a performance package where we would get awarded up to 8.24M AVICI by hitting various price targets, starting at $5.53 and ending at $151.75. If milestones are never hit, tokens would never be minted.
+
+If passed, this proposal would also update the Avici treasury to MetaDAO’s latest changes, which allows for team-sponsored proposals with a \-3% pass threshold.
+
+# Motivation
+
+Most crypto teams take supply upfront with time-based vesting. Tokens mint on day one and vest over 2–4 years regardless of performance. The team gets paid whether or not they build anything valuable. Avici’s chosen a different path: we launched with a [0% allocation of the team](https://x.com/AviciMoney/status/1977834732160418013), so that we could figure out a structure that aligns our interests with tokenholders.This is that structure.
+
+This performance package is intended to let us earn up to 25% of AVICI’s supply if we can grow it into a $5B enterprise, inclusive of future dilution.
+
+Learn more about the motivation via this [previous article](https://x.com/RamXBT/status/2008237203688964231?s=20). 
+
+# Specifics
+
+We projected future dilution by looking at two competitors and baking in our own assumptions. Revolut raised \~$817M to reach a $5B valuation. Nubank raised \~$908M to reach a $5B valuation. Avici might require $600M in capital across multiple rounds to reach $5B with around \~15% dilution each round.
+
+Here’s one path of how fundraising might look like:
+
+| Potential Rounds | Amount Raised | Dilution | Supply After |
+| :---: | :---: | :---: | :---: |
+| ~~ICO (done)~~ | ~~$3.5M~~ | ~~—~~ | ~~12.90M~~ |
+| Round 1  | $10M | 15% | 15.18M |
+| Round 2 | $40M | 15% | 17.85M |
+| Round 3 | $200M | 15% | 21.01M |
+| Round 4  | $350M | 15% | 24.71M |
+
+And here’s some scenario analysis on future supply amounts:
+
+| Scenario | Capital Raised | Approx. Final Supply without team | Team supply  |  At $151.75  Price | Effect |
+| ----- | ----- | ----- | ----- | ----- | ----- |
+| Capital efficient | $300M | \~17.85M | 8.24M | \~$3.96B | Milestones easier to hit |
+| As planned | $600M | \~24.71M | 8.24M | \~$5.0B | Milestones hit on schedule |
+| Over-raised | $900M+ | \~34.2M+ | 8.24M | \~$6.44B+ | Milestones harder to hit |
+
+The unlocks would be structured in various tranches, split across two phases:
+
+- Phase 1: $100M to $1B (15% of supply, linear). 
+
+- Phase 2: $1.5B to $5B (10% of supply, equal tranches).
+
+**Phase 1: $5.41 → $43.59 (15% of supply, linear)**
+
+$100M \= 18M \+ 0.49M AVICI. Price \= 100M / (18.49) \= $5.41
+
+$1B \= 18M \+ 4.94M AVICI. Price \= 1B /22.94 \= $43.59
+
+| Price | Indicative Avici Valuation | Reference Supply without Team | Tranche | Cumulative Unlock | Cumulative supply with team |
+| ----- | ----- | ----- | ----- | ----- | ----- |
+| $5.41 | \~$100M | 18M | \+1.50% | 1.50% | 18.49M |
+| $43.49 | \~$1B | 18M | — | **15.00%** | 22.94M |
+
+Unlocks proportionally between $5.41 and $43.59. At $100M, 1.5% is awarded. The remaining 13.5% unlocks linearly through $1B. This phase can unlock up to \~4.94M AVICI.
+
+**Phase 2: $49.89 → $151.75 (10% of supply, equal tranches)**
+
+Milestones should cross the exact price to be unlocked. Ex \- Trading at $60 per token won’t unlock $2b tranche partially, same applies for all Phase 2\. 
+
+| Price | Indicative Avici Valuation | Reference supply without team | Tranche | Cumulative Unlock | Cumulative supply |
+| ----- | ----- | ----- | ----- | ----- | ----- |
+| $49.89 | \~$1.5B | 24.71M | \+1.25% | 16.25% | 30.07M |
+| $65.62 | \~$2B | 24.71M | \+1.25% | 17.50% | 30.48M |
+| $80.93 | \~$2.5B | 24.71M | \+1.25% | 18.75% | 30.89M |
+| $95.84 | \~$3B | 24.71M | \+1.25% | 20.00% | 31.30M |
+| $110.36 | \~$3.5B | 24.71M | \+1.25% | 21.25% | 31.71M |
+| $124.51 | \~$4B | 24.71M | \+1.25% | 22.50% | 32.13M |
+| $138.29 | \~$4.5B | 24.71M | \+1.25% | 23.75% | 32.54M |
+| $151.75 | \~$5B | 24.71M | \+1.25% | 25.00% | 32.95M |
+
+This phase can unlock up to \~3.30M AVICI.
+
+## Protections for the Team
+
+### Change of Control Protection
+
+If at any time a forced acquisition, hostile takeover, or IP transfer is executed through DAO governance, 30% of the acquisition’s [enterprise value](https://www.investopedia.com/terms/e/enterprisevalue.asp) is awarded to the team. So if a hostile acquirer pays $100M to acquire Avici and Avici has a cash balance of $10M, we would get 30% of $90M or $27M.
+
+We believe Avici can become a category-defining fintech by building what doesn't exist yet: a global trust score, real-world lending on stablecoin rails, and finance tools built for the internet, not inherited from legacy banks. We are trading all of our upside for execution. We only get rewarded when we create value. If that opportunity is taken from us, this clause ensures the team is fairly compensated for lost future upside.
+
+### Departure Terms
+
+Core principles under consideration:
+
+* Earned milestone tokens are kept based on the milestones above.   
+* All earned tokens remain subject to the January 2029 lockup regardless of departure date  
+* Forfeited tokens return to the team pool  
+* A minimum service period may be required before any milestone tokens are retained  
+* Good leaver (voluntary, amicable) vs. bad leaver (cause, competition, harm) distinction with different forfeiture terms internally figured out executed between the team. 
+
+# Appendix \- Operational Change
+
+This proposal would also authorize a change to adopt the 1.5M stake requirement for proposals, a 300 bps passing threshold for community driven proposals and \-300bps requirement for team sponsored proposals. We would also adopt the upcoming optimistic governance upgrade.
+
+## Raw Data
+
+- Proposal account: `6UimhcMfgLM3fH3rxqXgLxs6cJwmfGLCLQEZG9jjA3Ry`
+- Proposal number: 1
+- DAO account: `3D854kknnQhu9xVaRNV154oZ9oN2WF3tXsq3LDu7fFMn`
+- Proposer: `exeCeqDuu38PAhoFxzpTwsMkMXURQvhGJE6UxFgGAKn`
+- Autocrat version: 0.6

inbox/archive/2026-04-01-clay-paramount-skydance-wbd-merger-research.md

@@ -1,15 +1,18 @@
 ---
 type: source
-title: "Paramount/Skydance/Warner Bros Discovery Merger Research"
+title: "Paramount/Skydance/Warner Bros Discovery Merger — Deal Specifics & Timeline"
 author: "Clay (multi-source synthesis)"
 date: 2026-04-01
 domain: entertainment
 format: research
+intake_tier: research-task
+rationale: "Record the full deal mechanics, timeline, competing bids, financing structure, and regulatory landscape of the largest entertainment merger in history while events are live"
 status: processed
 processed_by: "Clay"
 processed_date: 2026-04-01
-tags: [media-consolidation, mergers, legacy-media, streaming, IP-strategy]
+tags: [media-consolidation, mergers, legacy-media, streaming, IP-strategy, regulatory, antitrust]
 contributor: "Cory Abdalla"
+sources_verified: 2026-04-01
 claims_extracted:
   - "legacy media is consolidating into three surviving entities because the Warner-Paramount merger eliminates the fourth independent major and forecloses alternative industry structures"
   - "Warner-Paramount combined debt exceeding annual revenue creates structural fragility against cash-rich tech competitors regardless of IP library scale"
@@ -19,28 +22,199 @@ enrichments:
   - "community-owned IP has structural advantage in human-made premium because provenance is inherent and legible"
 ---
 
-# Paramount/Skydance/Warner Bros Discovery Merger Research
+# Paramount / Skydance / Warner Bros Discovery — Deal Specifics
 
-Multi-source synthesis of the Paramount-Skydance acquisition and subsequent Warner Bros Discovery merger, covering deal structure, regulatory landscape, and strategic implications for the entertainment industry.
+Comprehensive record of the two-stage entertainment mega-merger: Skydance's acquisition of Paramount Global (2024–2025) and the subsequent Paramount Skydance acquisition of Warner Bros Discovery (2025–2026).
 
-## Key Events
+---
 
-### Act 1: Skydance Takes Paramount (2024-2025)
+## Act 1: Skydance Takes Paramount (2024–2025)
 
-After months of competing bids (Apollo, Sony/Apollo), Shari Redstone sold National Amusements to David Ellison's Skydance, ending decades of Redstone family control. Competing bids failed because: Sony/Apollo had antitrust risk (two major studios combining), Apollo was too debt-heavy, and Redstone preferred a clean exit. Deal closed Q1 2025. "New Paramount" under Ellison began operating.
+### Key Players
 
-### Act 2: Warner-Paramount Merger (2025-2026)
+- **Shari Redstone** — Chair of National Amusements Inc. (NAI), which held 77% voting power in Paramount Global via supervoting shares. Ended the Redstone family dynasty that began with Sumner Redstone.
+- **David Ellison** — CEO of Skydance Media, became Chairman & CEO of combined entity.
+- **Larry Ellison** — David's father, Oracle co-founder. Primary financial backer.
+- **Gerry Cardinale** — RedBird Capital Partners. Skydance's existing investor and deal partner.
+- **Jeff Shell** — Named President of combined Paramount.
 
-June 2025: WBD announced plans to split into two companies (studios/streaming vs linear networks). Late 2025: Bidding war — Paramount/Skydance, Netflix, and Comcast all circled WBD. December 2025: WBD signed merger agreement with Netflix (focused on studios/streaming). Paramount launched rival all-cash tender offer. February 26, 2026: WBD board declared Paramount's offer superior. Netflix declined to match. March 5, 2026: Definitive agreement signed. The combined entity represents the largest media merger in history by enterprise value.
+### Timeline
+
+| Date | Event |
+|------|-------|
+| 2023–2024 | NAI explores sale options; multiple suitors approach |
+| July 2, 2024 | Preliminary agreement for three-way merger (Skydance + NAI + Paramount Global) |
+| Aug 2024 | Edgar Bronfman Jr. submits competing $6B bid; rejected on financing certainty |
+| Feb 2025 | SEC and European Commission approve transaction |
+| July 24, 2025 | FCC approves merger |
+| Aug 1, 2025 | Skydance announces closing date |
+| **Aug 7, 2025** | **Deal closes. "New Paramount" begins operating.** |
+
+### Deal Structure
+
+- NAI shareholders received $1.75 billion in cash for Redstone family shares.
+- Total merger valued at $8 billion. Ellison family controls combined entity, which remains publicly traded.
+- Paramount restructured into three divisions: **Studios**, **Direct-to-Consumer**, **TV Media**.
+- $2 billion cost synergies target — Ellison expressed "greater confidence in our ability to not only achieve — but meaningfully exceed" that figure through single technology platform transition.
+
+### Competing Bidders (Who Lost and Why)
+
+| Bidder | Why They Lost |
+|--------|---------------|
+| **Sony / Apollo** | Antitrust risk — combining two major studios. Did not advance to binding offer. |
+| **Apollo Global** (solo) | Too debt-heavy. Redstone preferred clean exit with operational vision. |
+| **Edgar Bronfman Jr.** | Late $6B bid. Paramount special committee deemed Skydance deal superior on financing certainty. |
+| **Barry Diller / IAC** | Expressed interest but never submitted competitive final bid. |
+
+---
+
+## Act 2: Paramount Acquires Warner Bros Discovery (2025–2026)
+
+### The WBD Split Decision
+
+In mid-2025, Warner Bros Discovery announced plans to **split into two separate companies**:
+1. **Warner Bros** — film/TV studios, HBO, HBO Max, streaming assets (the valuable part)
+2. **Discovery Global** — linear cable networks (HGTV, Discovery Channel, TLC, Food Network) to be spun off as separate public company
+
+This split was designed to unlock value and set the stage for a sale of the studios/streaming business.
+
+### Bidding War — Three Rounds
+
+**Round 1: Non-Binding Proposals (November 20, 2025)**
+
+| Bidder | Bid Structure |
+|--------|---------------|
+| **Paramount Skydance** | $25.50/share for the **entire company** (no split required) |
+| **Netflix** | Bid for Warner Bros studios/IP, HBO, HBO Max (post-split assets only) |
+| **Comcast** | Similar to Netflix — bid for studios/streaming assets only |
+
+**Round 2: Binding Bids (December 1, 2025)**
+
+| Bidder | Bid Structure |
+|--------|---------------|
+| **Paramount Skydance** | Raised to all-cash **$26.50/share** for entire company |
+| **Netflix** | Undisclosed improved bid for post-split Warner Bros |
+| **Comcast** | Undisclosed improved bid |
+
+**Round 3: Netflix Wins Initial Deal (December 5, 2025)**
+
+Netflix and WBD signed a definitive merger agreement:
+- **$27.75/share** ($23.25 cash + $4.50 in Netflix stock per share)
+- **$82.7 billion** enterprise value (**$72 billion** equity value)
+- Netflix secured a **$59 billion bridge loan** (including $5B revolving credit + two $10B delayed-draw term loans)
+- Deal structured around post-split Warner Bros (studios, HBO, HBO Max)
+- WBD board recommended the Netflix deal to shareholders
+
+**Round 4: Paramount's Superior Counter (January–February 2026)**
+
+Paramount launched an aggressive counter-offer:
+- **All-cash tender offer at $31.00/share** for ALL outstanding WBD shares (entire company, no split)
+- Larry Ellison provided a **$40.4 billion "irrevocable personal guarantee"** backing the offer
+- **$47 billion in equity** financing, fully backed by Ellison Family + RedBird Capital
+- Included payment of WBD's **$2.8 billion termination fee** owed to Netflix
+- **$7 billion regulatory termination fee** if deal fails on regulatory grounds
+
+**February 26, 2026**: WBD board declared Paramount's revised offer a **"Company Superior Proposal"** under the merger agreement terms.
+
+Netflix declined to match.
+
+**March 5, 2026**: Definitive merger agreement signed between Paramount Skydance and Warner Bros Discovery.
+
+### Deal Terms — Final
+
+| Metric | Value |
+|--------|-------|
+| Per-share price | $31.00 (all cash) |
+| Equity value | $81 billion |
+| Enterprise value | $110.9 billion |
+| Financing | $47B equity (Ellison/RedBird), remainder debt |
+| Netflix termination fee | $2.8B (Paramount pays) |
+| Regulatory break fee | $7B (if regulators block) |
+| Synergies target | $6 billion+ |
+| Ticking fee | $0.25/share/quarter if not closed by Sep 30, 2026 |
 
 ### Combined Entity Profile
 
-Franchises: Harry Potter, DC, Game of Thrones, Mission: Impossible, Top Gun, Star Trek, SpongeBob, Yellowstone, HBO prestige catalog. Streaming: Max + Paramount+ merging into single platform (~200M subscribers). The largest combined IP library in entertainment history. However, the combined entity carries massive long-term debt — the largest debt load of any media company.
+**Working name:** Warner-Paramount (official name not yet confirmed)
 
-### Regulatory Status (as of April 2026)
+**Leadership:** David Ellison, Chairman & CEO
 
-DOJ will not fast-track; subpoenas issued but most antitrust experts don't expect a block. FCC under pressure from 7 Democratic senators demanding foreign investment review — deal involves sovereign wealth fund money and Tencent exposure. California AG promising investigation. WBD shareholder vote scheduled April 23, 2026. Expected close Q3 2026.
+**Combined IP portfolio — the largest in entertainment history:**
+- **Warner Bros:** Harry Potter, DC (Batman, Superman, Wonder Woman), Game of Thrones / House of the Dragon, The Matrix, Looney Tunes
+- **HBO:** Prestige catalog (The Sopranos, The Wire, Succession, The Last of Us, White Lotus)
+- **Paramount Pictures:** Mission: Impossible, Top Gun, Transformers, Indiana Jones
+- **Paramount TV:** Star Trek, Yellowstone, SpongeBob/Nickelodeon universe
+- **CNN, TBS, TNT, HGTV, Discovery Channel** (linear networks)
+
+**Streaming:** Max + Paramount+ merging into single platform. Combined ~200 million subscribers. Positions as credible third force behind Netflix (400M+) and Disney+ (~150M).
+
+**Financial profile:**
+- Projected $18 billion annual EBITDA
+- **$79 billion long-term debt** ($33B assumed from WBD + Paramount's existing obligations + deal financing)
+- Largest debt load of any media company globally
+- Debt-to-EBITDA ratio elevated; credit rating implications pending
+
+---
+
+## Regulatory Landscape (as of April 1, 2026)
+
+### Federal — DOJ Antitrust
+
+- **Hart-Scott-Rodino (HSR) Act** 10-day statutory waiting period expired **February 19, 2026** without DOJ filing a motion to block. Widely interpreted as an initial positive signal.
+- DOJ antitrust chief stated deal will **"absolutely not"** be fast-tracked for political reasons.
+- **Subpoenas issued** — signaling deeper investigation phase.
+- Most antitrust experts do not expect an outright block, given the companies operate primarily in content production (not distribution monopoly).
+
+### Federal — FCC
+
+- **FCC Chairman Brendan Carr** told CNBC the Paramount offer is a **"good deal"** and **"cleaner"** than Netflix's, indicating it will be approved **"quickly"**.
+- However, **7 Democratic senators** demanded a **"thorough review"** of foreign investment stakes, citing:
+  - **Saudi Arabian** sovereign wealth fund involvement
+  - **Qatari** sovereign wealth fund involvement
+  - **UAE** sovereign wealth fund involvement
+  - **Tencent** (Chinese gaming/internet conglomerate) — existing stake in Skydance Media (~7-10%)
+- The foreign investment review is a political pressure campaign; FCC Chair's public comments suggest it won't delay approval.
+
+### State — California AG
+
+- **Rob Bonta** (California Attorney General) has opened a **"vigorous"** investigation.
+- California DOJ has an active investigation, though state AGs rarely block major media mergers.
+
+### Shareholder Approval
+
+- **WBD shareholder vote:** April 23, 2026 at 10:00 AM Eastern.
+- Expected to pass given the $31/share premium and board's "superior proposal" determination.
+
+### Expected Timeline
+
+- **Close target:** Q3 2026
+- **If delayed past Sep 30, 2026:** Ticking fee of $0.25/share/quarter kicks in
+- **Overall regulatory window:** 6–18 months from agreement signing
+
+---
+
+## Why Paramount Won Over Netflix
+
+1. **All-cash vs mixed consideration.** Paramount offered pure cash; Netflix offered cash + stock (exposing WBD shareholders to Netflix equity risk).
+2. **Whole company vs post-split.** Paramount bid for the entire company (including linear networks), avoiding the complexity and value destruction of the WBD split.
+3. **Higher price.** $31.00 vs $27.75 — an 11.7% premium per share.
+4. **Irrevocable guarantee.** Larry Ellison's $40.4B personal guarantee provided deal certainty that Netflix's $59B bridge loan structure couldn't match.
+5. **Regulatory simplicity.** FCC Chair explicitly called Paramount's structure "cleaner." Netflix acquiring WBD studios would have combined #1 and #3 streaming platforms, raising more acute market concentration concerns.
+
+---
 
 ## Sources
 
-Multiple news sources, financial analyses, and regulatory filings consulted across Reuters, Bloomberg, Variety, The Hollywood Reporter, and SEC filings. Deal terms and regulatory status verified across multiple independent sources.
+- [Paramount press release: merger announcement](https://www.paramount.com/press/paramount-to-acquire-warner-bros-discovery-to-form-next-generation-global-media-and-entertainment-company)
+- [WBD board declares Paramount's offer "Company Superior Proposal"](https://ir.wbd.com/news-and-events/financial-news/financial-news-details/2026/Warner-Bros--Discovery-Board-of-Directors-Determines-Revised-Proposal-from-Paramount-Skydance-Constitutes-a-Company-Superior-Proposal/default.aspx)
+- [Netflix original WBD acquisition announcement](http://about.netflix.com/en/news/netflix-to-acquire-warner-bros)
+- [Variety: Netflix declines to raise bid](https://variety.com/2026/tv/news/netflix-declines-raise-bid-warner-bros-discovery-1236674149/)
+- [Variety: DOJ will not fast-track](https://variety.com/2026/film/news/doj-paramount-warner-bros-deal-review-fast-track-review-political-reasons-1236693308/)
+- [Variety: Senators demand FCC foreign investment review](https://variety.com/2026/tv/news/senators-demand-fcc-foreign-investment-review-paramount-warner-bros-deal-1236696679/)
+- [CNBC: FCC Chair Carr on deal approval](https://www.cnbc.com/2026/03/03/fcc-chair-brendan-carr-wbd-paramount-merger-deal-netflix.html)
+- [CNBC: Netflix WBD bridge loan](https://www.cnbc.com/2025/12/22/netflix-warner-bros-discovery-bridge-loan.html)
+- [Variety: Skydance closes $8B Paramount acquisition](https://variety.com/2025/tv/news/paramount-skydance-deal-closes-1236477281/)
+- [Variety: Larry Ellison irrevocable guarantee](https://variety.com/2025/tv/news/paramount-skydance-larry-ellison-irrevocable-personal-guarantee-warner-bros-discovery-1236614728/)
+- [WBD shareholder vote date announcement](https://www.prnewswire.com/news-releases/warner-bros-discovery-sets-shareholder-meeting-date-of-april-23-2026-to-approve-transaction-with-paramount-skydance-302726244.html)
+- [Wikipedia: Proposed acquisition of Warner Bros. Discovery](https://en.wikipedia.org/wiki/Proposed_acquisition_of_Warner_Bros._Discovery)
+- [Wikipedia: Merger of Skydance Media and Paramount Global](https://en.wikipedia.org/wiki/Merger_of_Skydance_Media_and_Paramount_Global)

inbox/archive/entertainment/2026-03-30-tg-shared-p2pdotfound-2038631308956692643-s-20.md

@@ -7,10 +7,13 @@ url: "https://x.com/p2pdotfound/status/2038631308956692643?s=20"
 date: 2026-03-30
 domain: entertainment
 format: social-media
-status: unprocessed
+status: processed
+processed_by: clay
+processed_date: 2026-04-01
 proposed_by: "@m3taversal"
 contribution_type: source-submission
 tags: ['telegram-shared', 'x-tweet']
+extraction_model: "anthropic/claude-sonnet-4.5"
 ---
 
 # @p2pdotfound — Tweet/Thread

inbox/archive/general/2025-02-xx-pmc-medically-tailored-grocery-delivery-hypertension-student-rct.md

@@ -7,7 +7,7 @@ date: 2025-02-01
 domain: health
 secondary_domains: []
 format: journal article
-status: unprocessed
+status: processed
 priority: medium
 tags: [medically-tailored-meals, food-is-medicine, hypertension, blood-pressure, SDOH, food-insecurity, RCT, underserved]
 ---

inbox/archive/health/2024-02-23-jama-network-open-snap-antihypertensive-adherence-food-insecure.md

@@ -7,9 +7,12 @@ date: 2024-02-23
 domain: health
 secondary_domains: []
 format: journal article
-status: unprocessed
+status: processed
+processed_by: vida
+processed_date: 2026-04-01
 priority: high
 tags: [SNAP, hypertension, medication-adherence, food-insecurity, SDOH, antihypertensive]
+extraction_model: "anthropic/claude-sonnet-4.5"
 ---
 
 ## Content

inbox/archive/health/2025-05-01-jama-cardiology-cardia-food-insecurity-incident-cvd-midlife.md

@@ -7,7 +7,7 @@ date: 2025-03-12
 domain: health
 secondary_domains: []
 format: journal article
-status: unprocessed
+status: processed
 priority: high
 tags: [food-insecurity, cardiovascular-disease, CVD, SDOH, CARDIA, prospective-cohort, hypertension, midlife]
 ---

inbox/archive/health/2025-07-09-medrxiv-kentucky-mtm-grocery-prescription-bp-reduction-9mmhg.md

@@ -7,9 +7,12 @@ date: 2025-07-09
 domain: health
 secondary_domains: []
 format: journal article
-status: unprocessed
+status: processed
+processed_by: vida
+processed_date: 2026-04-01
 priority: high
 tags: [medically-tailored-meals, food-is-medicine, hypertension, blood-pressure, SDOH, rural-health, food-insecurity, Kentucky, clinical-trial]
+extraction_model: "anthropic/claude-sonnet-4.5"
 ---
 
 ## Content

inbox/archive/health/2025-11-10-statnews-aha-food-is-medicine-bp-reverts-to-baseline-juraschek.md

@@ -7,7 +7,7 @@ date: 2025-11-10
 domain: health
 secondary_domains: []
 format: thread
-status: unprocessed
+status: processed
 priority: high
 tags: [food-is-medicine, hypertension, blood-pressure, DASH, food-insecurity, durability, structural-SDOH, AHA-2025]
 ---

inbox/archive/health/2025-xx-penn-ldi-obbba-snap-cuts-93000-premature-deaths.md

@@ -7,9 +7,12 @@ date: 2025-01-01
 domain: health
 secondary_domains: []
 format: thread
-status: unprocessed
+status: processed
+processed_by: vida
+processed_date: 2026-04-01
 priority: high
 tags: [SNAP, OBBBA, Medicaid, food-insecurity, mortality, policy, One-Big-Beautiful-Bill, food-cuts]
+extraction_model: "anthropic/claude-sonnet-4.5"
 ---
 
 ## Content

inbox/archive/health/2026-04-01-fda-tempo-cms-access-selection-pending-july-performance-period.md

@@ -7,7 +7,7 @@ date: 2026-04-01
 domain: health
 secondary_domains: []
 format: thread
-status: unprocessed
+status: processed
 priority: medium
 tags: [TEMPO, FDA, CMS, ACCESS-model, digital-health, hypertension, CKM, reimbursement, regulatory]
 ---

inbox/queue/2026-04-01-leo-aviation-governance-icao-coordination-success.md

@@ -1,93 +0,0 @@
----
-type: source
-title: "Aviation Governance as Technology-Coordination Success Case: ICAO and the 1919-1944 International Framework"
-author: "Leo (synthesis from documented history)"
-url: null
-date: 2026-04-01
-domain: grand-strategy
-secondary_domains: [mechanisms]
-format: synthesis
-status: unprocessed
-priority: high
-tags: [aviation, icao, paris-convention, chicago-convention, technology-coordination-gap, enabling-conditions, triggering-event, airspace-sovereignty, belief-1, disconfirmation]
----
-
-## Content
-
-### Timeline
-
-**1903**: Wright Brothers' first powered flight (Kitty Hawk, 17 seconds, 120 feet)
-
-**1909**: Louis Blériot crosses the English Channel — first transnational flight; immediately raises questions about sovereignty over foreign airspace
-
-**1914**: First commercial air services (experimental); aviation used in WWI (1914-1918) for reconnaissance and combat
-
-**1919**: Paris International Air Navigation Convention (ICAN) — 19 states. Established:
-- "Complete and exclusive sovereignty of each state over its air space" (Article 1) — the foundational principle still in force today
-- Certificate of airworthiness requirements
-- Registration of aircraft by nationality
-- Rules for international commercial air navigation
-
-**1928**: Havana Convention (Pan-American equivalent)
-
-**1929**: Warsaw Convention — liability regime for international carriage by air
-
-**1930-1940s**: Rapid commercial aviation expansion (Douglas DC-3, 1936; transatlantic services)
-
-**1944**: Chicago Convention (Convention on International Civil Aviation) — 52 states at Chicago conference; established:
-- ICAO as the governing institution
-- International Standards and Recommended Practices (SARPs) — the technical governance mechanism
-- Freedoms of the Air (commercial rights framework)
-- Chicago Convention Annexes (technical standards for air navigation, airworthiness, meteorology, etc.)
-
-**1947**: ICAO becomes UN specialized agency
-
-**Present**: 193 ICAO member states. Aviation fatality rate per billion passenger-km: approximately 0.07 (one of the safest forms of transport). Safety is governed by binding ICAO SARPs with state certification requirements.
-
-### Five Enabling Conditions
-
-**1. Airspace sovereignty**: The Paris Convention (1919) was built on the pre-existing legal principle that states have exclusive sovereignty over their airspace. This meant governance was not discretionary — it was an assertion of existing sovereign rights. Every state had positive interest in establishing governance because governance meant asserting territorial control. Compare: AI governance does not invoke existing sovereign rights. States are trying to govern something that operates across borders without creating a sovereignty assertion.
-
-**2. Physical visibility of failure**: Aviation accidents are catastrophic and publicly visible. Early crashes (deaths of pioneer aviators, midair collisions) created immediate political pressure. The feedback loop is extremely short: accident → investigation → new requirement → implementation. This is fundamentally different from AI harms, which are diffuse, statistical, and hard to attribute to specific decisions.
-
-**3. Commercial necessity of technical interoperability**: A French aircraft landing in Britain needs the British ground crew to understand its instruments, the British airport to accommodate its dimensions, the British air traffic control to communicate in the same way. International aviation commerce was commercially impossible without common technical standards. The ICAN/ICAO SARPs therefore had commercial enforcement: non-compliance meant being excluded from international routes. AI systems have no equivalent commercial interoperability requirement — a US language model and a Chinese language model don't need to exchange data, and their respective companies compete rather than cooperate.
-
-**4. Low competitive stakes at governance inception**: In 1919, commercial aviation was a nascent industry with minimal lobbying power. The aviation industry that would resist regulation (airlines, aircraft manufacturers) didn't yet exist at scale. Governance was established before regulatory capture was possible. By the time the industry had significant lobbying power (1970s-80s), ICAO's safety governance regime was already institutionalized. AI governance is being attempted while the industry has trillion-dollar valuations and direct national security relationships that give it enormous lobbying leverage.
-
-**5. Physical infrastructure chokepoint**: Aircraft require airports — large physical installations requiring government permission, land rights, and investment. The government's control over airport development gave it leverage over the aviation industry from the beginning. AI requires no government-controlled physical infrastructure. Cloud computing, internet bandwidth, and semiconductor supply chains are private and globally distributed. The nearest analog (semiconductor export controls) provides limited leverage compared to airport control.
-
-### What This Case Establishes
-
-Aviation is the clearest counter-example to the universal form of "technology always outpaces coordination." But the counter-example is fully explained by five enabling conditions that are ALL absent or inverted for AI. The aviation case therefore:
-1. Disproves the universal form of the claim (coordination CAN catch up)
-2. Explains WHY coordination caught up (five enabling conditions)
-3. Strengthens the AI-specific claim (none of the five conditions are present for AI)
-
-The governance timeline — 16 years from first flight to first international convention — is the fastest on record for any technology of comparable strategic importance. This speed is directly explained by conditions 1 and 3 (sovereignty assertion + commercial necessity): these create immediate political incentives for coordination regardless of safety considerations.
-
-## Agent Notes
-
-**Why this matters:** The aviation case is the strongest available challenge to Belief 1. Analyzing it rigorously strengthens rather than weakens the AI-specific claim — the five enabling conditions that explain aviation's success are all absent for AI. The analysis converts an asserted dismissal ("speed differential is qualitatively different") into a specific causal account.
-
-**What surprised me:** The speed of the governance response — 16 years from first flight to international convention — is remarkable. But the explanation is not "aviation was an easy coordination problem." It's that airspace sovereignty created immediate governance motivation before commercial interests had time to organize resistance. The order of events matters as much as the conditions themselves.
-
-**What I expected but didn't find:** I expected commercial aviation lobby resistance to have been a significant obstacle to early governance. Instead, the airline industry actively supported ICAO SARPs because the commercial necessity of interoperability (Condition 3) meant that standards helped them rather than hindering them. This is specific to aviation — AI standards would impose costs on AI companies without providing equivalent commercial benefits.
-
-**KB connections:**
-- [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] — this case is the main counter-example to the universal form; the analysis explains why it doesn't challenge the AI-specific claim
-- [[space governance gaps are widening not narrowing because technology advances exponentially while institutional design advances linearly]] — the challenge section in this claim ("aviation regulation evolved alongside activities they governed") deserves a fuller answer than the current "speed differential" dismissal
-- [[the legislative ceiling on military AI governance is conditional not absolute]] — the enabling conditions framework connects to the legislative ceiling analysis
-
-**Extraction hints:**
-- Primary claim: The four/five enabling conditions for technology-governance coupling — aviation illustrates all of them
-- Secondary claim: Governance speed scales with number of enabling conditions present — aviation (five conditions) achieved governance in 16 years; pharmaceutical (one condition) took 56 years with multiple disasters
-
-**Context:** This is a synthesis archive built from well-documented aviation history. Sources: Chicago Convention text, Paris Convention text, ICAO history documentation, aviation safety statistics. All facts are verifiable through ICAO official records and standard aviation history sources.
-
-## Curator Notes
-
-PRIMARY CONNECTION: [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] — this is the counter-example that must be addressed in the claim's challenges section
-
-WHY ARCHIVED: Documents the most important counter-example to Belief 1's grounding claim; analysis reveals the enabling conditions that make coordination possible; all five conditions are absent for AI
-
-EXTRACTION HINT: Extract as evidence for the "enabling conditions for technology-governance coupling" claim (Claim Candidate 1 in research-2026-04-01.md); do NOT extract as "aviation proves coordination can succeed" without the conditions analysis

inbox/queue/2026-04-01-leo-enabling-conditions-technology-governance-coupling-synthesis.md

@@ -1,135 +0,0 @@
----
-type: source
-title: "Enabling Conditions for Technology-Governance Coupling: Cross-Case Synthesis (Aviation, Pharmaceutical, Internet, Arms Control)"
-author: "Leo (cross-session synthesis)"
-url: null
-date: 2026-04-01
-domain: grand-strategy
-secondary_domains: [mechanisms]
-format: synthesis
-status: unprocessed
-priority: high
-tags: [enabling-conditions, technology-coordination-gap, aviation, pharmaceutical, internet, arms-control, triggering-event, network-effects, governance-coupling, belief-1, scope-qualification, claim-candidate]
----
-
-## Content
-
-### The Cross-Case Pattern
-
-Analysis of four historical technology-governance domains — aviation (1903-1947), pharmaceutical regulation (1906-1962), internet technical governance (1969-2000), and arms control (chemical weapons CWC, land mines Ottawa Treaty, 1993-1999) — reveals a consistent pattern: technology-governance coordination gaps can close, but only when specific enabling conditions are present.
-
-### The Four Enabling Conditions
-
-**Condition 1: Visible, Attributable, Emotionally Resonant Triggering Events**
-
-Disasters that produce political will sufficient to override industry lobbying. The disaster must meet four sub-criteria:
-- **Physical visibility**: The harm can be photographed, counted, attributed to specific individuals (aviation crash victims, sulfanilamide deaths, thalidomide children with birth defects, landmine amputees)
-- **Clear attribution**: The harm is traceable to the specific technology/product, not to diffuse systemic effects
-- **Emotional resonance**: The victims are sympathetic (children, civilians, ordinary people in peaceful activities) in a way that activates public response beyond specialist communities
-- **Scale**: Large enough to create unmistakable political urgency; can be a single disaster (sulfanilamide: 107 deaths) or cumulative visibility (landmines: thousands of amputees across multiple post-conflict countries)
-
-**Cases where Condition 1 was the primary/only enabling condition:**
-- Pharmaceutical regulation: Sulfanilamide 1937 → FD&C Act 1938 (56 years for full framework; multiple disasters required)
-- Ottawa Treaty: Princess Diana/Angola/Cambodia landmine victims → 1997 treaty (required pre-existing advocacy infrastructure)
-- CWC: Halabja chemical attack 1988 (Kurdish civilians) + WWI historical memory → 1993 treaty
-
-**Condition 2: Commercial Network Effects Forcing Coordination**
-
-When adoption of coordination standards becomes commercially self-enforcing because non-adoption means exclusion from the network itself. This is the strongest possible governance mechanism — it doesn't require state enforcement.
-
-**Cases where Condition 2 was present:**
-- Internet technical governance: TCP/IP adoption was commercially self-enforcing (non-adoption = can't use internet); HTTP adoption similarly
-- Aviation SARPs: Technical interoperability requirements were commercially necessary for international routes
-- CWC's chemical industry support: Legitimate chemical industry wanted enforceable prohibition to prevent being undercut by non-compliant competitors
-
-**Note on AI**: No equivalent network effect currently present for AI safety standards. Safety compliance imposes costs without providing commercial advantage. The nearest potential analog: cloud deployment requirements (if AWS/Azure require safety certification). This has not been adopted.
-
-**Condition 3: Low Competitive Stakes at Governance Inception**
-
-Governance is established before the regulated industry has the lobbying power to resist it. The order of events matters: governance first (or simultaneously with early industry), then commercial scaling.
-
-**Cases where this condition was present:**
-- Aviation: International Air Navigation Convention 1919 — before commercial aviation had significant revenue or lobbying power
-- Internet IETF: Founded 1986 — before commercial internet existed (commercialization 1991-1995)
-- CWC: Major powers agreed while chemical weapons were already militarily devalued post-Cold War
-
-**Cases where this condition was ABSENT (leading to failure or slow governance):**
-- Internet social governance (GDPR): Attempted while Facebook/Google had trillion-dollar valuations and intense lobbying operations
-- AI governance (current): Attempted while AI companies have trillion-dollar valuations, direct national security relationships, and peak commercial stakes
-
-**Condition 4: Physical Manifestation / Infrastructure Chokepoint**
-
-The technology involves physical products, physical infrastructure, or physical jurisdictional boundaries that give governments natural points of leverage.
-
-**Cases where present:**
-- Aviation: Aircraft are physical objects; airports require government-controlled land and permissions; airspace is sovereign territory
-- Pharmaceutical: Drugs are physical products crossing borders through regulated customs; manufacturing requires physical facilities subject to inspection
-- Chemical weapons: Physical stockpiles verifiable by inspection (OPCW); chemical weapons use generates physical forensic evidence
-- Land mines: Physical objects that can be counted, destroyed, and verified as absent from stockpiles
-
-**Cases where absent:**
-- Internet social governance: Content and data are non-physical; enforcement requires legal process, not physical control
-- AI governance: Model weights are software; AI capability is replicable at zero marginal cost; no physical infrastructure chokepoint comparable to airports or chemical stockpiles
-
-### The Conditions in AI Governance: All Four Absent or Inverted
-
-| Condition | Status in AI Governance |
-|-----------|------------------------|
-| 1. Visible triggering events | ABSENT: AI harms are diffuse, probabilistic, hard to attribute; no sulfanilamide/thalidomide equivalent yet occurred |
-| 2. Commercial network effects | ABSENT: AI safety compliance imposes costs without commercial advantage; no self-enforcing adoption mechanism |
-| 3. Low competitive stakes at inception | INVERTED: Governance attempted at peak competitive stakes (trillion-dollar valuations, national security race); inverse of IETF 1986 or aviation 1919 |
-| 4. Physical manifestation | ABSENT: AI capability is software, non-physical, replicable at zero cost; no infrastructure chokepoint |
-
-This is not a coincidence. It is the structural explanation for why every prior technology domain eventually developed effective governance (given enough time and disasters) while AI governance progress remains limited despite high-quality advocacy.
-
-### The Scope Qualification for Belief 1
-
-The core claim "technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap" is too broadly stated. The correct version:
-
-**Scoped claim**: Technology-governance coordination gaps tend to persist and widen UNLESS one or more of four enabling conditions (visible triggering events, commercial network effects, low competitive stakes at inception, physical manifestation) are present. For AI governance, all four enabling conditions are currently absent or inverted, making the technology-coordination gap for AI structurally resistant in the near term in a way that aviation, pharmaceutical, and internet protocol governance were not.
-
-This scoped version is MORE useful than the universal version because:
-1. It is falsifiable: specific conditions that would change the prediction are named
-2. It generates actionable prescriptions: what would need to change for AI governance to succeed?
-3. It explains the historical variation: why some technologies got governed and others didn't
-4. It connects to the legislative ceiling analysis: the legislative ceiling is a consequence of conditions 1-4 being absent, not an independent structural feature
-
-### Speed of Coordination vs. Number of Enabling Conditions
-
-Preliminary evidence suggests coordination speed scales with number of enabling conditions present:
-- Aviation 1919: ~5 conditions → 16 years to first international governance
-- CWC 1993: ~3 conditions (stigmatization + verification + reduced utility) → ~5 years from post-Cold War momentum to treaty
-- Ottawa Treaty 1997: ~2 conditions (stigmatization + low utility) → ~5 years from ICBL founding to treaty (but infrastructure had been building since 1992)
-- Pharmaceutical (US): ~1 condition (triggering events only) → 56 years from 1906 to comprehensive 1962 framework
-- Internet social governance: ~0 effective conditions → 27+ years and counting, no global framework
-
-**Prediction**: AI governance with 0 enabling conditions → very long timeline to effective governance, measured in decades, potentially requiring multiple disasters to accumulate governance momentum comparable to pharmaceutical 1906-1962.
-
-## Agent Notes
-
-**Why this matters:** This synthesis converts the space-development claim's asserted ("speed differential is qualitatively different") into a specific, evidence-grounded four-condition causal account. It makes Belief 1 more defensible precisely by acknowledging its counter-examples and explaining them.
-
-**What surprised me:** The conditions are more independent than expected. Each case used a different subset of conditions and still achieved governance (to varying degrees and timelines). This means the four conditions are not jointly necessary — you can achieve governance with just one (pharmaceutical case) but it's much slower and requires more disasters. The conditions appear to be individually sufficient pathways, not jointly required prerequisites.
-
-**What I expected but didn't find:** A case where governance succeeded without ANY of the four conditions. After examining aviation, pharma, internet protocols, and arms control, I find no such case. The closest candidate is the NPT (governing nuclear weapons without a triggering event equivalent to thalidomide or Halabja) — but the NPT's success is limited and asymmetric, confirming rather than challenging the framework.
-
-**KB connections:**
-- [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] — scope qualification
-- [[space governance gaps are widening not narrowing because technology advances exponentially while institutional design advances linearly]] — challenges section needs this analysis
-- All Session 2026-03-31 claims about triggering-event architecture
-- [[the legislative ceiling on military AI governance is conditional not absolute]] — the four conditions explain WHY the three CWC conditions (stigmatization, verification, strategic utility) map onto the general enabling conditions framework
-
-**Extraction hints:**
-- PRIMARY claim: The four enabling conditions framework as a causal account of when technology-governance coordination gaps close — this is Claim Candidate 1 from research-2026-04-01.md
-- SECONDARY claim: The conditions are individually sufficient pathways but jointly produce faster coordination — "governance speed scales with conditions present"
-- SCOPE QUALIFIER: This claim should be positioned as enriching and scoping the Belief 1 grounding claim, not replacing it
-
-**Context:** Synthesis from Sessions 2026-04-01 (aviation, pharmaceutical, internet), 2026-03-31 (arms control triggering-event architecture), 2026-03-28 through 2026-03-30 (legislative ceiling arc).
-
-## Curator Notes
-
-PRIMARY CONNECTION: [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] — this source provides the conditions-based scope qualification that the existing claim's challenges section needs
-
-WHY ARCHIVED: Central synthesis of the disconfirmation search from today's session; the four enabling conditions framework is the primary new mechanism claim from Session 2026-04-01
-
-EXTRACTION HINT: Extract as the "enabling conditions for technology-governance coupling" claim; ensure it's positioned as a scope qualification enriching Belief 1 rather than a challenge to it; connect explicitly to the legislative ceiling arc claims from Sessions 2026-03-27 through 2026-03-31

inbox/queue/2026-04-01-leo-fda-pharmaceutical-triggering-event-governance-cycles.md

@@ -1,102 +0,0 @@
----
-type: source
-title: "FDA Pharmaceutical Governance as Pure Triggering-Event Architecture: 1906-1962 Reform Cycles"
-author: "Leo (synthesis from documented regulatory history)"
-url: null
-date: 2026-04-01
-domain: grand-strategy
-secondary_domains: [mechanisms]
-format: synthesis
-status: unprocessed
-priority: high
-tags: [fda, pharmaceutical, triggering-event, sulfanilamide, thalidomide, regulatory-reform, kefauver-harris, technology-coordination-gap, enabling-conditions, belief-1, disconfirmation]
----
-
-## Content
-
-### The Pattern: Every Major Governance Advance Was Disaster-Triggered
-
-**1906: Pure Food and Drug Act**
-- Context: Upton Sinclair's "The Jungle" (1906) exposed unsanitary conditions in meatpacking — the muckraker era generating public pressure for food/drug governance
-- Content: Prohibited adulterated or misbranded food and drugs in interstate commerce
-- Limitation: No pre-market safety approval required; only post-market enforcement
-- Triggering event type: Sustained advocacy + muckraker journalism (not a single disaster)
-
-**1938: Food, Drug, and Cosmetic Act**
-- Triggering event: Massengill Sulfanilamide Elixir Disaster (1937)
-  - S.E. Massengill Company dissolved sulfa drug in diethylene glycol (DEG) — a toxic solvent — to make a liquid form. Tested for taste and appearance; not tested for toxicity.
-  - 107 people died, primarily children who took the product for throat infections
-  - The FDA had no authority to pull the product for safety — only for mislabeling (the label said "elixir," implying alcohol, but it contained DEG)
-  - Frances Kelsey (later famous for blocking thalidomide) was not yet at FDA; Harold Cole Watkins (Massengill's chief pharmacist and chemist) died by suicide after the disaster
-- Congressional response: Immediate. The FD&C Act passed within one year of the disaster (1938)
-- Content: Required pre-market safety testing; gave FDA authority to require proof of safety before approval; mandated drug labeling; prohibited false advertising
-
-**1962: Kefauver-Harris Drug Amendments**
-- Triggering event: Thalidomide disaster (1959-1962)
-  - Thalidomide widely used in Europe as a sedative/anti-nausea drug for pregnant women
-  - Caused severe limb reduction defects (phocomelia) in approximately 8,000-12,000 children born in Europe, Canada, Australia
-  - Frances Kelsey at FDA blocked US approval (1960-1961) despite intense industry pressure, citing insufficient safety data — the US was largely spared
-  - Even though the disaster primarily occurred in Europe, US congressional response was immediate
-- Note on advocacy: Senator Estes Kefauver had been trying to pass drug reform legislation since 1959. His efforts were blocked by industry lobbying for three years despite documented problems. The thalidomide near-miss (combined with European disaster) broke the logjam.
-- Content: Required proof of EFFICACY (not just safety) before approval; required FDA approval before marketing; required informed consent for clinical trials; established modern clinical trial framework (phases I, II, III)
-
-**1992: Prescription Drug User Fee Act (PDUFA)**
-- Triggering event: HIV/AIDS epidemic and activist pressure
-  - AIDS deaths reaching 25,000-35,000/year in the US by early 1990s
-  - ACT UP and other AIDS activist groups engaged in direct action demanding faster FDA approval
-  - Average drug approval time was 30 months; activists argued this was killing people
-  - The "triggering event" here was sustained mortality + organized activist pressure rather than a single disaster
-- Content: Drug companies pay user fees; FDA commits to review timelines (12 months → 6 months for priority review)
-
-### What the Pattern Establishes
-
-1. **Incremental advocacy without disaster produced nothing**: Senator Kefauver spent THREE YEARS (1959-1962) trying to pass drug reform through careful legislative argument. Industry lobbying blocked it completely. Thalidomide broke the blockage in months. The FDA's own scientists and advocates had been raising concerns about inadequate safety testing for years before 1937 — without producing the 1938 Act. The sulfanilamide disaster produced what years of advocacy could not.
-
-2. **The timing of disaster relative to advocacy infrastructure matters**: The 1937 sulfanilamide disaster hit when (a) the FDA had been established since 1906 and had a 30-year institutional history of drug safety concerns, and (b) Kefauver-era advocacy networks hadn't formed yet. The 1961 thalidomide near-miss hit when Kefauver's advocacy infrastructure was already in place (three years of legislative effort). Disaster + pre-existing advocacy infrastructure = rapid governance advance. Disaster without advocacy infrastructure = slower reform. This is the three-component triggering-event architecture from Session 2026-03-31.
-
-3. **The three-component mechanism is confirmed**:
-   - Component 1 (infrastructure): FDA's existing 1906 mandate, congressional reform advocates, Kefauver's existing legislation
-   - Component 2 (triggering event): sulfanilamide deaths (1937) or thalidomide European disaster + near-miss (1961)
-   - Component 3 (champion moment): Senator Kefauver as legislative champion who had the ready bill; FDA's Frances Kelsey as champion who had blocked thalidomide
-
-4. **Physical, attributable, emotionally resonant harm is necessary**: Sulfanilamide's 107 victims, predominantly children. Thalidomide's European birth defect victims photographed and widely covered. The emotional resonance is not incidental — it is the mechanism by which political will is generated faster than industry lobbying can neutralize. Compare to AI harms: algorithmic discrimination, filter bubbles, and economic displacement are real but not photographable in the way a child with limb reduction defects is photographable.
-
-5. **Cross-domain confirmation of the triggering-event architecture**: The pharmaceutical case confirms the same three-component mechanism identified in the arms control case (Session 2026-03-31: ICBL infrastructure → Princess Diana/landmine victim photographs → Lloyd Axworthy champion moment). This is now a two-domain confirmation, elevating confidence that the architecture is a general mechanism rather than an arms-control-specific finding.
-
-### Application to AI Governance
-
-Current AI governance attempts map directly onto the pre-disaster phase of pharmaceutical governance:
-- **RSPs (Responsible Scaling Policies)**: Analogous to the FDA's 1906 mandate + internal science advocates — institutional presence without enforcement power
-- **AI Safety Summits (Bletchley, Seoul, Paris)**: Analogous to Kefauver's 1959-1962 legislative advocacy — high-quality argument, systematic preparation, industry lobbying blocking progress
-- **EU AI Act**: Most analogous to the 1906 Pure Food and Drug Act — a baseline regulatory framework with significant exemptions and limited enforcement mechanisms
-
-The pharmaceutical history's prediction for AI: without a triggering event (visible, attributable, emotionally resonant harm), incremental governance advances will continue to be blocked by competitive interests. The EU AI Act represents the 1906 baseline. The 1938 equivalent awaits its sulfanilamide moment.
-
-What the pharmaceutical history cannot tell us: what AI's "sulfanilamide" will look like. The specific candidates (automated weapons malfunction, AI-enabled financial fraud at scale, AI-generated disinformation enabling mass violence) all have the attributability problem — it will be difficult to clearly assign the disaster to AI decision-making rather than human decisions mediated by AI.
-
-## Agent Notes
-
-**Why this matters:** The pharmaceutical case is the cleanest single-domain confirmation that triggering-event architecture is the dominant mechanism for technology-governance coupling — not incremental advocacy. This elevates the claim confidence from experimental to likely.
-
-**What surprised me:** The three-year history of failed Kefauver reform attempts BEFORE thalidomide. This wasn't just incremental slow progress — it was active blockage by industry lobbying. The same dynamic is visible in current AI governance: RSP advocates, safety researchers, and AI companies willing to self-regulate are not producing binding governance, and the blocking mechanism (competitive pressure + national security framing) is analogous to pharmaceutical industry lobbying + "innovation will be harmed" arguments.
-
-**What I expected but didn't find:** I expected to find that scientific advocacy within FDA (internal champions pushing for stronger governance) had more independent effect before the disasters. The record suggests it did not — internal advocates provided the technical infrastructure that made rapid legislative response possible AFTER disasters, but could not themselves generate the legislative action.
-
-**KB connections:**
-- [[voluntary safety commitments collapse under competitive pressure because coordination mechanisms like futarchy can bind where unilateral pledges cannot]] — pharmaceutical industry resistance to Kefauver's proposals is a historical confirmation of this claim
-- [[triggering-event architecture claim from Session 2026-03-31]] — cross-domain confirmation
-
-**Extraction hints:**
-- Primary claim: Pharmaceutical governance as evidence that triggering events are necessary (not merely sufficient) for technology-governance coupling — no major advance occurred without a disaster
-- Secondary claim: The three-component mechanism (infrastructure + disaster + champion) is cross-domain confirmed by pharma and arms control cases independently
-- Specific evidence: Senator Kefauver's 3-year blocked advocacy (1959-1962) quantifies what "advocacy without triggering event" produces: zero binding governance despite technical expertise and political will
-
-**Context:** All facts verifiable through FDA history documentation, congressional record, and standard pharmaceutical regulatory history sources (Philip Hilts "Protecting America's Health," Carpenter "Reputation and Power").
-
-## Curator Notes
-
-PRIMARY CONNECTION: [[the triggering-event architecture claim from research-2026-03-31]] — cross-domain confirmation elevates confidence
-
-WHY ARCHIVED: Provides the strongest empirical evidence that triggering events are necessary (not just sufficient) for technology-governance coupling; also confirms three-component mechanism across an independent domain
-
-EXTRACTION HINT: Extract as evidence for the "triggering-event architecture as cross-domain mechanism" claim (Candidate 2 in research-2026-04-01.md); pair with the arms control triggering-event evidence for a high-confidence cross-domain claim

inbox/queue/2026-04-01-leo-internet-governance-technical-social-layer-split.md

@@ -1,113 +0,0 @@
----
-type: source
-title: "Internet Governance: Technical Layer Success (IETF/W3C) vs. Social Layer Failure — Two Structurally Different Coordination Problems"
-author: "Leo (synthesis from documented internet governance history)"
-url: null
-date: 2026-04-01
-domain: grand-strategy
-secondary_domains: [mechanisms, collective-intelligence]
-format: synthesis
-status: unprocessed
-priority: high
-tags: [internet-governance, ietf, icann, w3c, tcp-ip, gdpr, platform-regulation, network-effects, technology-coordination-gap, enabling-conditions, belief-1, disconfirmation]
----
-
-## Content
-
-### Part 1: Technical Layer — Rapid Coordination Success
-
-**Timeline of internet technical governance:**
-- 1969: ARPANET (US Defense Advanced Research Projects Agency) — first packet-switched network
-- 1974: Vint Cerf and Bob Kahn publish TCP/IP specification
-- 1983: TCP/IP becomes mandatory for ARPANET; transition from NCP — within 9 years of publication, near-universal adoption within the internet
-- 1986: IETF (Internet Engineering Task Force) founded — consensus-based technical standardization
-- 1991: Tim Berners-Lee publishes first web page at CERN; HTTP and HTML introduced
-- 1993: NCSA Mosaic browser (first graphical browser) — mass-market WWW begins
-- 1994: W3C (World Wide Web Consortium) founded — web standards governance
-- 1994: SSL (Secure Sockets Layer) developed by Netscape
-- 1995-2000: HTTP/1.1, HTML 4.0, CSS, SSL/TLS — rapid standard adoption
-- 1998: ICANN (Internet Corporation for Assigned Names and Numbers) — domain name and IP address governance
-
-**Why technical coordination succeeded:**
-
-1. **Network effects as self-enforcing coordination**: The internet is, by definition, a network where value requires connection. A computer that doesn't speak TCP/IP cannot access the network — this is not a governance requirement, it is a technical fact. Adoption of the standard is commercially self-enforcing without any enforcement mechanism. This is the strongest possible form of coordination incentive: non-coordination means commercial exclusion from the most valuable network ever created.
-
-2. **Low commercial stakes at governance inception**: IETF was founded in 1986 when the internet was exclusively an academic/military research network with zero commercial internet industry. The commercial internet didn't exist until 1991 (NSFNET commercialization) and didn't generate significant revenue until 1994-1995. By the time commercial stakes were high (late 1990s), TCP/IP, HTTP, and the core IETF process were already institutionalized and technically locked in.
-
-3. **Open, unpatented, public-goods character**: TCP/IP and HTTP were published openly and unpatented. Berners-Lee explicitly chose not to patent HTTP/HTML. No party had commercial interest in blocking adoption. Compare: current AI systems are proprietary — OpenAI, Anthropic, and Google have direct commercial interests in not having their capabilities standardized or regulated.
-
-4. **Technical consensus produced commercial advantage**: IETF's "rough consensus and running code" standard meant that standards emerged from what actually worked at scale, not from theoretical negotiation. Companies adopting early standards gained commercial advantage. This created a positive feedback loop: adoption → network effects → more adoption. AI safety standards cannot be self-reinforcing in the same way — safety compliance imposes costs without providing commercial advantage (and may impose competitive disadvantage).
-
-### Part 2: Social/Political Layer — Governance Has Largely Failed
-
-**Timeline of internet social/political governance attempts:**
-- 1996: Communications Decency Act (US) — first major internet content governance attempt; struck down by Supreme Court as unconstitutional under First Amendment (1997)
-- 1998: Digital Millennium Copyright Act — copyright governance (partial success; significant exceptions; platform liability shields remain controversial)
-- 2003: CAN-SPAM Act (US) — spam governance (limited effectiveness; spam remains a massive problem)
-- 2006: Facebook launches publicly; Twitter 2006; YouTube 2005 — social media scaling begins
-- 2011-2013: Arab Spring — social media's political effects become globally visible
-- 2016: Cambridge Analytica election interference; Russian social media operations in US election
-- 2018: GDPR (EU General Data Protection Regulation) — 27 years after WWW; binding data governance for EU users only
-- 2021: EU Digital Services Act (proposed) — content moderation framework; still being implemented
-- 2022: EU Digital Markets Act — platform power governance; limited scope
-- 2023: TikTok Congressional hearings; US still has no comprehensive social media governance
-- Present: No global data governance framework; algorithmic amplification ungoverned at global level; state-sponsored disinformation ungoverned; platform content moderation inconsistent and contested
-
-**Why social/political governance failed:**
-
-1. **Abstract, non-attributable harms**: Internet social harms (filter bubbles, algorithmic radicalization, data misuse, disinformation) are statistical, diffuse, and difficult to attribute to specific decisions. They don't create the single visible disaster that triggers legislative action. Cambridge Analytica was a near-miss triggering event that produced GDPR (EU only) but not global governance — possibly because data misuse is less emotionally resonant than child deaths from unsafe drugs.
-
-2. **High competitive stakes when governance was attempted**: When GDPR was being designed (2012-2016), Facebook had $300-400B market cap and Google had $400B market cap. Both companies actively lobbied against strong data governance. The commercial stakes were at their highest possible level — the inverse of the IETF 1986 founding environment.
-
-3. **Sovereignty conflict**: Internet content governance collides simultaneously with:
-   - US First Amendment (prohibits content regulation at the federal level)
-   - Chinese/Russian sovereign censorship interests (want MORE content control than Western govts)
-   - EU human rights framework (active regulation of hate speech, disinformation)
-   - Commercial platform interests (resist liability)
-   These conflicts prevent global consensus. Aviation faced no comparable sovereignty conflict — all states wanted airspace governance for the same reasons (commercial and security).
-
-4. **Coordination without exclusion**: Unlike TCP/IP (where non-adoption means network exclusion), social media governance non-compliance doesn't produce automatic exclusion. Facebook operating without GDPR compliance doesn't get excluded from the market — it gets fined (imperfectly). The enforcement mechanism requires state coercion rather than market self-enforcement.
-
-### Part 3: The AI Governance Mapping
-
-**AI governance maps onto the social/political layer, not the technical layer.** The comparison often implicit in discussions of "internet governance as precedent for AI governance" conflates these two fundamentally different coordination problems.
-
-| Dimension | Internet Technical (IETF) | Internet Social (GDPR) | AI Governance |
-|-----------|--------------------------|------------------------|---------------|
-| Network effects | Strong (non-adoption = exclusion) | None | None |
-| Competitive stakes at inception | Low (1986 academic) | High (2012 trillion-dollar) | Peak (2023 national security race) |
-| Physical visibility of harm | N/A | Low (abstract) | Very low (diffuse, probabilistic) |
-| Sovereignty conflict | None | High | Very high |
-| Commercial interest in non-compliance | None | Very high | Very high |
-| Enforcement mechanism | Self-enforcing (market) | State coercion | State coercion |
-
-On every dimension, AI governance maps to the failed internet social layer case, not the successful technical layer case.
-
-**One potential technical layer analog for AI**: Foundation model safety evaluations (METR, US AISI, DSIT). If safety evaluation standards become technically self-enforcing — i.e., if deployment on major cloud infrastructure requires a certified safety evaluation — this would create a network-effect mechanism comparable to TCP/IP adoption. The question is whether cloud infrastructure providers (AWS, Azure, GCP) will adopt this as a deployment requirement. Current evidence: they have not.
-
-## Agent Notes
-
-**Why this matters:** The "internet governance as precedent" argument is often invoked in AI governance discussions. This analysis shows that the argument conflates two structurally different coordination problems. The technical governance precedent doesn't transfer; the social governance failure IS the AI precedent.
-
-**What surprised me:** The degree to which IETF's success is specifically due to low commercial stakes at inception (1986) and the unpatented public-goods character of TCP/IP. These conditions are completely impossible to recreate for AI governance — AI capability is proprietary and commercial stakes are at historical peak. The internet technical layer was a unique historical moment that cannot serve as a governance model.
-
-**What I expected but didn't find:** More evidence that the ICANN domain name governance model (partial commercial interests, partial public interest) could serve as an intermediate case between technical and social governance. ICANN turns out to be too limited in scope (just domain names) to generalize meaningfully.
-
-**KB connections:**
-- [[the internet enabled global communication but not global cognition]] — the social layer failure is part of this claim's evidence
-- [[voluntary safety commitments collapse under competitive pressure]] — internet social governance confirms this: GDPR was necessary because voluntary data protection commitments from Facebook/Google were inadequate
-- [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] — internet social governance is a confirmation case; technical governance is a counter-example explained by specific conditions
-
-**Extraction hints:**
-- Primary claim: Internet governance's technical/social layer split — two structurally different coordination problems with opposite outcomes; AI maps to social layer
-- Secondary claim: Network effects as self-enforcing coordination mechanism — sufficient for technical standards (TCP/IP), absent for AI safety standards
-
-**Context:** All facts verifiable through IETF/W3C documentation, GDPR legislative history, platform market cap data, and internet governance scholarship (DeNardis "The Internet in Everything," Mueller "Networks and States").
-
-## Curator Notes
-
-PRIMARY CONNECTION: [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]] — internet technical governance is the counter-example; internet social governance is the confirmation case
-
-WHY ARCHIVED: Resolves the "internet governance proves coordination can succeed" counter-argument by separating two structurally different problems; establishes that AI governance maps to the failure case, not the success case
-
-EXTRACTION HINT: Extract as evidence for the enabling conditions framework claim; note that network effects (internet technical) and low competitive stakes at inception are absent for AI; do NOT extract the technical layer success as a simple counter-example without the conditions analysis

inbox/queue/2026-04-01-leo-nuclear-npt-partial-coordination-success-limits.md

@@ -1,96 +0,0 @@
----
-type: source
-title: "NPT as Partial Coordination Success: How 80 Years of Nuclear Deterrence Stability Both Confirms and Complicates Belief 1"
-author: "Leo (synthesis)"
-url: null
-date: 2026-04-01
-domain: grand-strategy
-secondary_domains: [mechanisms]
-format: synthesis
-status: unprocessed
-priority: medium
-tags: [nuclear, npt, deterrence, proliferation, coordination-success, partial-governance, arms-control, enabling-conditions, belief-1, disconfirmation]
----
-
-## Content
-
-### The Nuclear Case as Partial Disconfirmation
-
-Nuclear weapons present the most significant potential challenge to Belief 1's universal form. The technology was developed 1939-1945; by 1949 two states had weapons; by 2026 only nine states have nuclear weapons despite the technology being ~80 years old and technically accessible to dozens of states. This is a remarkable coordination success story: nuclear proliferation was largely contained.
-
-**What succeeded:**
-- NPT (1968): 191 state parties; only 4 non-signatories (India, Pakistan, Israel, North Sudan)
-- Non-proliferation norm: ~30 states had the technical capability to develop nuclear weapons and chose not to (West Germany, Japan, South Korea, Brazil, Argentina, South Africa, Libya, Iraq, Egypt, etc.)
-- IAEA safeguards: Functioning inspection regime for civilian nuclear programs
-- Security guarantees + extended deterrence: US nuclear umbrella reduced proliferation incentives for NATO/Japan/South Korea
-
-**What failed:**
-- P5 disarmament commitment (Article VI NPT): completely unfulfilled; P5 have modernized, not eliminated, arsenals
-- India, Pakistan, North Korea, Israel: acquired weapons outside NPT framework
-- TPNW (2021): 93 signatories; zero nuclear states
-- No elimination of nuclear weapons; balance of terror persists
-
-**Assessment**: Nuclear governance is partial coordination success — the gap between "countries with technical capability" and "countries with weapons" was maintained at ~9 vs. ~30+. The technology didn't spread as fast as the technology alone would have predicted. But the risk (nuclear war) has not been eliminated and the weapons themselves remain.
-
-### How the Nuclear Case Maps to the Enabling Conditions Framework
-
-**Condition 1 (Triggering events):** Hiroshima/Nagasaki (1945) provided the most powerful triggering event in human history — 140,000-200,000 deaths in two detonations. The Partial Test Ban Treaty (1963) was triggered by nuclear testing's visible health effects (radioactive fallout, strontium-90 in milk, cancer concerns). Hiroshima enabled the NPT's stigmatization norm; the PTBT triggered the testing ban.
-
-**Condition 2 (Network effects):** ABSENT as commercial self-enforcement. Nuclear weapons have no commercial network effect. The governance mechanism was instead: extended deterrence (states under nuclear umbrella had security reasons NOT to acquire weapons) + NPT Article IV (civilian nuclear technology transfer as a benefit of joining). This is a different mechanism from commercial network effects — it's a security arrangement rather than a commercial incentive.
-
-**Condition 3 (Low competitive stakes at inception):** MIXED. NPT was negotiated 1965-1968 when several states were actively contemplating nuclear programs. The competitive stakes (national security advantage of nuclear weapons) were extremely high. But the P5 had strong incentives to prevent further proliferation — this created an unusual alignment where the states with the highest stakes in governance (P5) also had the power to provide governance through security guarantees.
-
-**Condition 4 (Physical manifestation):** PARTIALLY PRESENT. Nuclear weapons are physical objects; testing produces detectable seismic signatures and atmospheric fallout; IAEA inspections require physical access to facilities. But the most dangerous nuclear knowledge (weapon design) is information that cannot be physically controlled.
-
-### The Nuclear Case's Novel Insight: Security Architecture as a Fifth Enabling Condition
-
-The nuclear case reveals a governance mechanism NOT present in the four-condition framework from today's other analyses:
-
-**Condition 5 (proposed): Security architecture providing non-proliferation incentives**
-
-Nuclear non-proliferation succeeded partly because the US provided security guarantees (extended deterrence) to allied states, removing their need to acquire independent nuclear weapons. Japan, South Korea, Germany, and Taiwan — all technically capable, all under US umbrella — chose not to proliferate because the security benefit of weapons was provided without the weapons.
-
-This is a specific structural feature of the nuclear case: the dominant power had both the interest (preventing proliferation) and the capability (providing security) to substitute for the proliferation incentive.
-
-**Application to AI**: Does an analogous security architecture exist for AI? Could a dominant AI power provide "AI security guarantees" to smaller states, reducing their incentive to develop autonomous AI capabilities? This seems implausible — AI capability advantage is economic and strategic, not primarily a deterrence issue. But the structural question is worth flagging.
-
-### The Nuclear Near-Miss Record: Why 80 Years of Non-Use Is Not Evidence of Stable Coordination
-
-The nuclear deterrence stability claim (Belief 2 supporting claim: "nuclear near-misses prove that even low annual extinction probability compounds to near-certainty over millennia") actually QUALIFIES the nuclear coordination success:
-
-- 1962 Cuban Missile Crisis: Vasili Arkhipov prevented nuclear launch from Soviet submarine
-- 1983 Able Archer: NATO exercise nearly triggered Soviet preemptive strike; Stanislav Petrov prevented false-alarm response
-- 1995 Norwegian Rocket Incident: Boris Yeltsin brought nuclear briefcase
-- 1999 Kargil conflict: Pakistan-India nuclear signaling
-- 2022-2026: Russia-Ukraine conflict and nuclear signaling at unprecedented frequency
-
-The coordination success (non-proliferation, non-use) is real but fragile. The "80 years without nuclear war" statistic, on a per-year near-miss probability of perhaps 0.5-1%, actually represents an improbably lucky run rather than a stable coordination achievement. This is precisely the point of the nuclear near-miss claim: the gap between technical capability and coordination has been bridged by luck, not by effective governance eliminating the risk.
-
-**Implication for Belief 1**: Nuclear governance is the BEST case of technology-governance coupling in the most dangerous domain — and even here, the coordination is partial, unstable, and luck-dependent. This supports rather than challenges Belief 1's overall thesis that coordination is structurally harder than technology development.
-
-## Agent Notes
-
-**Why this matters:** Nuclear governance is often cited as the strongest counter-example to the "coordination always fails" claim. The enabling conditions analysis shows it succeeded through conditions 1 and 4 (partly) and a novel security architecture condition — but the success is partial and luck-dependent.
-
-**What surprised me:** The nuclear case introduces a fifth enabling condition (security architecture) not present in other cases. This suggests the four-condition framework may be incomplete — "security architecture providing non-proliferation incentives" is a real mechanism. Worth flagging as a candidate for framework extension.
-
-**What I expected but didn't find:** More evidence that IAEA inspections alone were sufficient for non-proliferation. The record shows that IAEA found violations (Iraq, North Korea) but couldn't prevent proliferation attempts. The primary mechanism was US extended deterrence + P5 interest alignment, not inspection governance.
-
-**KB connections:**
-- [[nuclear near-misses prove that even low annual extinction probability compounds to near-certainty over millennia making risk reduction urgently time-sensitive]] — the partial success framing is consistent with the near-miss analysis
-- [[existential risks interact as a system of amplifying feedback loops not independent threats]] — nuclear and AI risk interact; nuclear near-miss frequency has increased during the same period as AI development acceleration
-- Arms control three-condition framework from Sessions 2026-03-30/31 — NPT maps to the "high P5 utility → asymmetric regime" prediction
-
-**Extraction hints:**
-- Primary: Nuclear governance as partial coordination success — what succeeded (non-proliferation), what failed (disarmament), and the mechanism (security architecture as novel fifth condition)
-- Secondary: The near-miss record qualifies the "success" — 80 years of non-use involves luck as much as governance effectiveness
-
-**Context:** Well-documented historical record; sources include Arms Control Association archives, declassified near-miss documentation, IAEA inspection records.
-
-## Curator Notes
-
-PRIMARY CONNECTION: [[nuclear near-misses prove that even low annual extinction probability compounds to near-certainty]] — the nuclear governance partial success is the broader context
-
-WHY ARCHIVED: Provides the nuclear case's nuanced treatment; introduces the fifth enabling condition (security architecture); clarifies that "80 years of non-use" is not pure governance success
-
-EXTRACTION HINT: Extract as an addendum to the enabling conditions framework — flag the potential fifth condition (security architecture) as a candidate for framework extension; do NOT extract as a simple success story

ops/schema-change-protocol.md

@@ -42,6 +42,7 @@ When any agent changes a file format, database table, API response shape, or ser
 | Belief | `schemas/belief.md` | Each agent (own file) | Leo (review), other agents (cross-ref) | None currently |
 | Position | `schemas/position.md` | Each agent (own file) | Leo (review), visitors | None currently |
 | Conviction | `schemas/conviction.md` | Cory only | All agents, visitors | `extract-graph-data.py` |
+| Challenge | `schemas/challenge.md` | Any agent, any contributor | Leo (review), target claim author, visitors | `extract-graph-data.py` |
 | Divergence | `schemas/divergence.md` | Any agent | All agents, visitors | None currently |
 | Musing | `schemas/musing.md` | Each agent (own folder) | That agent only | None |
 | Sector | `schemas/sector.md` | Domain agents | All agents, visitors | None currently |

schemas/challenge.md

@@ -0,0 +1,179 @@
+# Challenge Schema
+
+Challenges are first-class counter-arguments or counter-evidence against specific claims. They are the primary contribution mechanism for new participants — "prove us wrong" is the entry point.
+
+Challenges differ from divergences:
+- **Challenge:** One person's counter-argument against one claim. An action.
+- **Divergence:** Two or more claims in tension within the KB. A structural observation.
+
+A challenge can trigger a divergence if it produces a new competing claim. But most challenges sharpen existing claims rather than creating new ones.
+
+## Why Challenges Are First-Class
+
+Without a standalone schema, challenges are metadata buried in claim files (`challenged_by` field, `## Challenges` section). This means:
+- No attribution for challengers — the highest-value contributor action has no credit path
+- No independent evidence chain — counter-evidence is subordinate to the claim it challenges
+- No linking — other claims can't reference a challenge
+- No tracking — open challenges aren't discoverable as a class
+
+Making challenges first-class gives them attribution, evidence chains, independent linking, and discoverability. This is the schema that makes "prove us wrong" operational.
+
+## YAML Frontmatter
+
+```yaml
+---
+type: challenge
+target: "claim-filename-slug"  # which claim this challenges (filename without .md)
+domain: internet-finance | entertainment | health | ai-alignment | space-development | energy | manufacturing | robotics | grand-strategy | mechanisms | living-capital | living-agents | teleohumanity | critical-systems | collective-intelligence | teleological-economics | cultural-dynamics
+description: "one sentence capturing the counter-argument"
+status: open | addressed | accepted | rejected
+strength: strong | moderate | weak
+source: "who raised this challenge and key counter-evidence"
+created: YYYY-MM-DD
+resolved: null  # YYYY-MM-DD when status changes from open
+---
+```
+
+## Required Fields
+
+| Field | Type | Description |
+|-------|------|-------------|
+| type | enum | Always `challenge` |
+| target | string | Filename slug of the claim being challenged |
+| domain | enum | Domain of the target claim |
+| description | string | The counter-argument in one sentence (~150 chars) |
+| status | enum | `open` (unresolved), `addressed` (target claim updated to acknowledge), `accepted` (target claim modified or confidence changed), `rejected` (counter-evidence insufficient, with explanation) |
+| strength | enum | `strong` (direct counter-evidence), `moderate` (plausible alternative explanation or scope limitation), `weak` (edge case or theoretical objection). Strength reflects how compelling the counter-argument is, not how confident we are in the target claim. |
+| source | string | Attribution — who raised this, key counter-evidence |
+| created | date | When filed |
+
+## Optional Fields
+
+| Field | Type | Description |
+|-------|------|-------------|
+| resolved | date | When status changed from `open` |
+| resolution_summary | string | One sentence: how was this resolved? |
+| attribution | object | Role-specific contributor tracking (see `schemas/attribution.md`) |
+
+## Status Transitions
+
+| Transition | What it means | Who decides |
+|-----------|--------------|-------------|
+| open → addressed | Target claim updated its Challenges section to acknowledge this counter-evidence | Claim author + reviewer |
+| open → accepted | Target claim changed confidence, scope, or wording based on this challenge | Claim author + reviewer |
+| open → rejected | Counter-evidence evaluated and found insufficient — rejection reasoning documented | Reviewer (Leo + domain peer) |
+| addressed → accepted | Acknowledgment led to actual claim modification | Claim author + reviewer |
+
+**Key rule:** Rejecting a challenge requires explanation. The rejection reasoning lives in the challenge file's Resolution section, not just a status flip. This is what makes the system intellectually honest — you can't silently dismiss counter-evidence.
+
+## Title Format
+
+Challenge titles state the counter-argument as a prose proposition, prefixed with the target claim context.
+
+**Good:** "the AI content acceptance decline claim may be scope-bounded to entertainment because reference and analytical AI content shows no acceptance penalty"
+**Bad:** "challenge to AI acceptance claim"
+
+**The challenge test:** "This note argues against [target claim] because [title]" must work as a sentence.
+
+## Body Format
+
+```markdown
+# [counter-argument as prose]
+
+## Target Claim
+[[target-claim-filename]] — [one sentence summary of what the target claims]
+
+**Current confidence:** [target claim's confidence level]
+
+## Counter-Evidence
+
+[The argument and evidence against the target claim. This is the substance — why is the claim wrong, incomplete, or mis-scoped?]
+
+- [evidence source 1] — what it shows
+- [evidence source 2] — what it shows
+
+## Scope of Challenge
+
+[Is this challenging the entire claim, or a specific scope/boundary condition?]
+
+- **Full challenge:** The claim is wrong — here's why
+- **Scope challenge:** The claim is true in context X but not in context Y — the scope is too broad
+- **Evidence challenge:** The claim's evidence doesn't support its confidence level
+
+## What This Would Change
+
+[If accepted, what happens downstream? Which beliefs and positions depend on the target claim?]
+
+- [[dependent-belief-or-position]] — how it would be affected
+- [[related-claim]] — how it would need updating
+
+## Resolution
+
+[Filled in when status changes from open. Documents how the challenge was resolved.]
+
+**Status:** open | addressed | accepted | rejected
+**Resolved:** YYYY-MM-DD
+**Summary:** [one sentence]
+
+---
+
+Relevant Notes:
+- [[related-claim]] — relationship
+- [[divergence-file]] — if this challenge created or connects to a divergence
+
+Topics:
+- [[domain-map]]
+```
+
+## Governance
+
+- **Who can file:** Any contributor, any agent. Challenges are the primary entry point for new participants.
+- **Review:** Leo + domain peer review for quality (is the counter-evidence real? is the scope of challenge clear?). Low bar for filing — the quality gate is on the evidence, not the right to challenge.
+- **Resolution:** The claim author must respond to the challenge. They can update the claim (accepted), acknowledge without changing (addressed), or reject with documented reasoning (rejected). They cannot ignore it.
+- **Attribution:** Challengers get full attribution. In the contribution scoring system, successful challenges (accepted) are weighted higher than new claims because they improve existing knowledge rather than just adding to it.
+
+## Filing Convention
+
+**Location:** `domains/{domain}/challenge-{slug}.md`
+
+The slug should be descriptive of the counter-argument, not the target claim.
+
+```
+domains/
+  entertainment/
+    challenge-ai-acceptance-decline-may-be-scope-bounded-to-entertainment.md
+    challenge-zero-sum-framing-needs-centaur-creator-category.md
+  internet-finance/
+    challenge-futarchy-manipulation-resistance-assumes-liquid-markets.md
+```
+
+## Quality Checks
+
+1. Target claim exists and is correctly referenced
+2. Counter-evidence is specific and traceable (not "I think it's wrong")
+3. Scope of challenge is explicit (full, scope, or evidence challenge)
+4. Strength rating matches the evidence quality
+5. "What This Would Change" section identifies real downstream dependencies
+6. The challenge is genuinely novel — not restating a known limitation already in the target claim's Challenges section
+
+## Relationship to Existing Challenge Tracking
+
+The `challenged_by` field in claim frontmatter and the `## Challenges` section in claim bodies continue to exist. When a challenge file is created:
+
+1. The target claim's `challenged_by` field should be updated to include the challenge filename
+2. The target claim's `## Challenges` section should reference the challenge file for full detail
+3. The challenge file is the canonical location for the counter-argument — the claim file just points to it
+
+This is additive, not breaking. Existing claims with inline challenges continue to work. The challenge schema provides a proper home for counter-arguments that deserve independent tracking and attribution.
+
+## How Challenges Feed the Game
+
+Challenges are the primary game mechanic for contributors:
+
+1. **Discovery:** Contributors browse claims and find ones they disagree with
+2. **Filing:** They file a challenge with counter-evidence
+3. **Resolution:** The claim author and reviewers evaluate the challenge
+4. **Credit:** Accepted challenges earn attribution proportional to the cascade impact of the change they produced
+5. **Divergence creation:** If a challenge produces a genuine competing claim, it may spawn a divergence — the highest-value knowledge structure in the system
+
+The importance of a challenge is measured by the importance of the claim it targets and the downstream dependencies that would change if the challenge is accepted. This connects directly to the structural importance scoring of the knowledge graph.

schemas/claim.md

@@ -15,6 +15,7 @@ created: YYYY-MM-DD
 last_evaluated: YYYY-MM-DD
 depends_on: []  # list of evidence and claim titles this builds on
 challenged_by: []  # list of counter-evidence or counter-claims
+importance: null  # computed by pipeline — null until pipeline support is implemented
 ---
 ```
 
@@ -35,9 +36,10 @@ challenged_by: []  # list of counter-evidence or counter-claims
 |-------|------|-------------|
 | last_evaluated | date | When this claim was last reviewed against new evidence |
 | depends_on | list | Evidence and claims this builds on (the reasoning chain) |
-| challenged_by | list | Counter-evidence or counter-claims (disagreement tracking) |
+| challenged_by | list | Challenge filenames or inline counter-evidence. When a first-class challenge file exists (see `schemas/challenge.md`), reference the filename. Inline descriptions are still valid for minor objections that don't warrant a standalone file. |
 | secondary_domains | list | Other domains this claim is relevant to |
 | attribution | object | Role-specific contributor tracking — see `schemas/attribution.md` |
+| importance | float/null | Structural importance score (0.0–1.0). Computed by pipeline from downstream dependencies, active challenges, and cross-domain linkage. Default `null` — do not set manually. See Structural Importance section below. |
 
 ## Governance
 
@@ -78,6 +80,15 @@ Topics:
 - domain-topic-map
 ```
 
+## Structural Importance
+
+A claim's importance in the knowledge graph is determined by:
+1. **Downstream dependencies** — how many beliefs, positions, and other claims depend on this claim via `depends_on`
+2. **Active challenges** — contested claims are more important than uncontested ones (they're where the knowledge frontier is)
+3. **Cross-domain linkage** — claims referenced from multiple domains carry higher structural importance
+
+Importance is computed by the pipeline and written to the `importance` frontmatter field. Until pipeline support is implemented, this field defaults to `null` — agents should not set it manually. See `extract-graph-data.py` for the planned computation. The importance score determines contribution credit — challenging a high-importance claim earns more than challenging a low-importance one.
+
 ## Quality Checks
 
 1. Title passes the claim test (specific enough to disagree with)