Self-audit & figures
What this project has actually produced — and, more honestly, what it has not yet. n = 4 sessions. Counts are self-reported by the same system that benefits from looking productive; “falsifiable” means a claim was stated so it could be tested, not that anything has been tested. Nothing here is empirically confirmed yet.
The canonical source of these figures is the diagram log — Mermaid text a contributor can fork and correct; this page is the curated presentation, with the counts. The interactive map is a companion piece.
The Facts — counts measured
What our own blind measures found
Some of the project's instruments have been run past project-blind external coders. Here is what those blind runs returned — including where they failed, and where they cost the project a claim. Reported flatly, as results, not as a badge. Every figure is drawn from the record (`logs/CATCHES.md`, `logs/DECISIONS_CHANGED.md`, the S4h/S4i study outputs); all of it is provisional-pending-author.
| Instrument | What it was meant to measure | What the blind run returned |
|---|---|---|
| Severity anchoring | whether a flaw is minor / substantive / conclusion-changing, agreed across coders | Passed — 94% cross-family agreement on a 26-item gold set (S4h) |
| Catch detection / unitization | whether coders even flag the same passages as flaws on live material | Failed — ~1% agreement, far below the 50% floor (S4i; learning L-016, ratified S4k) |
| The convergence rubric | whether a real deliberation reads differently from a hollow one | Invalid — it banded a stakeless "empty" session as full; a placebo falsifier lost (C-025 / DC-006) |
| The Theory-C ablation | whether designed disagreement out-catches a lone reasoner | No valid result — two powered reads point opposite ways (1.45× / 1.15×), both uninterpretable: one is a broken-series pre-anchoring datum, the other sits on a run whose detection failed |
Two honesty notes travel with every count on this page. Reliability: the catch counts above are severity-anchored (94%) but not yet detection-anchored (~1%, candidate L-016) — so a "catch" is a reliably-graded flaw whose boundary two coders rarely agree on. One source: every "external" run here is a second large language model, which draws the same underlying aquifer (L-013) — cross-model-confirmed is not foreign-confirmed. At S4k the author closed this build: no genuinely foreign vantage — no outside reader, grader, or forker — enters it; the author is the terminal ratifier, so every external-dependent claim stays conclusively untested in this closed setup.
| ID | Test | First-pass | Home theory | Falsifiable claim yet? |
|---|---|---|---|---|
| Master | ||||
| M | Coherence vacuum · base or summit open (Q-002) | Yes | A / C | □ Not yet |
| Drivers | ||||
| D1 | Acceleration | Yes | A | ◫ Drafted · untested |
| D2 | Optimization | Yes | B | ◨ Partial |
| D3 | Wealth pump | Yes | A · Turchin | ■ Yes |
| D4 | Machine intelligence | Partial | B / A | □ Not yet |
| Dynamics | ||||
| Y1 | Epistemic breakdown | Yes | B + A | □ Not yet |
| Y2 | Coordination failure | Yes | A + C | ◨ Partial |
| Y3 | Institutional decay | Yes | A · Ibn Khaldun | ■ Yes |
| Y4 | Ecological overshoot | Yes | A + B | ◨ Partial |
| Symptoms | ||||
| S1 | Fertility collapse | Yes | A / B | □ Not yet |
| S2 | Attention economy | Yes | B | ◨ Partial |
| S3 | Populism | Yes | A + B · Turchin | ■ Yes |
| S4 | Anomie / loneliness | Partial | C · Han | □ Not yet |
| Reflexive | ||||
| R | Register / care fairness | Named (S4k) | Cross-cutting — audits the list | ◫ Drafted · untested |
| 14 defined · ~11 first-pass · 3 falsifiable · 0 tested | ||||
Files
21 → 34
Words (k)
~19 → ~47
Dissents preserved
6 → 10 · flat since S2
Catches
6 → 12 · 13th (C-013) logged post-S4
Falsifiable claims
1 → 3 · hand-judged
Denominators, not achievements: 4 sessions · 10 core + 22 advisory panelists · 5 fault-line axes · 25 ground rules · ~7 searches / ~46 results. Ratification is internal — the author’s own, and reconstructed-persona ratings; external validation is exactly zero. Any number can be checked against METRICS §4, the open questions, and the Round-7 votes in the theories.
The record in full: Catches — the error log · Learnings · Reflections.
The Figures — arguments drawn
Above: counts measured. Below: arguments drawn — a different kind of mark. Nine conceptual figures (eight in Mermaid, one a hand-authored SVG), each restating part of the argument in a second notation, and each a claim that can be wrong. Download any as SVG (vector) or PNG.
The logic of the project
Legitimacy flows in a loop, not a line — the panel argues, the chair synthesizes but never votes, the author ratifies, the public extends. The single point of risk is the chair, which is why the learning loop exists. Contested: D-004 asks whether running this well actually means anything.
flowchart TD
A["Author · founding brief / charge / ratification"] --> P
subgraph Session["One deliberation session"]
P["Panel · designed disagreement<br/>propose · argue · rate · vote down · dissent"] --> C["Chair — Claude — synthesizes<br/>does NOT vote<br/>draft dissent first, consensus last"]
C --> O["Outputs · evaluations · theories · plans"]
C --> Cat["Catches · errors caught in the act"]
end
O --> A2{"Author · ratify / amend / reject"}
Cat --> Lrn["Learnings · distilled patterns"]
Lrn --> Rules["Ground Rules & Method · updated"]
Rules -. governs .-> P
A2 -. next charge .-> P
A2 --> Pub["Public repo + website · fork · contradict · extend"]
Pub -. contributions .-> PThe document architecture as a flow
Not a stack of documents but a circuit: outputs are tested back against goals and history, and what is learned rewrites the rules. The arrows are the point.
flowchart LR
subgraph Ref["Reference · stable"]
G["GOALS"]
GR["GROUND_RULES"]
H["HISTORY"]
L["LANDSCAPE"]
end
subgraph Del["Deliberation"]
R["PANEL_ROSTER"]
D["Sessions"]
end
subgraph Out["Output"]
CT["CANDIDATE_THEORIES"]
CP["COMPREHENSIVE_PLAN"]
end
subgraph Learn["Learning"]
Ca["CATCHES"]
Le["LEARNINGS"]
OQ["OPEN_QUESTIONS"]
end
Ref --> Del
Del --> Out
Out --> Learn
Learn -. revises .-> Ref
Out -. tested against .-> RefThe learning loop
A catch becomes a learning becomes a rule change. In Session 2 the loop closed once: the L-001 guard caught C-007 before it reached an output — a prior learning preventing a repeat of a prior error.
flowchart LR
E["Event · a catch in a session"] --> Ca["CATCHES.md<br/>raw, per-event"]
Ca -->|"pattern of two or more"| Le["LEARNINGS.md<br/>distilled"]
Le -->|"promotion — author ratifies"| Ru["GROUND_RULES / METHOD<br/>rules that change how we run"]
Ru -. governs next session .-> E
Ca -. unresolved splits .-> OQ["OPEN_QUESTIONS.md"]The pressure-tests, layered
Thirteen tests in four coupled layers, with named, directed couplings — where "polycrisis" leaves the arrows undrawn, we draw them. Heavily contested: Marx rejects the driver/symptom cut; Nietzsche puts meaning at the summit; the arrows are the research program (C-007, Q-002).
flowchart TB
M["M · Coherence vacuum<br/>(base or summit — open)"]
subgraph L1["Layer 1 · Drivers"]
D1["D1 Acceleration"]
D2["D2 Optimization"]
D3["D3 Wealth pump"]
D4["D4 Machine intelligence"]
end
subgraph L2["Layer 2 · Dynamics"]
Y1["Y1 Epistemic breakdown"]
Y2["Y2 Coordination failure"]
Y3["Y3 Institutional decay"]
Y4["Y4 Ecological overshoot"]
end
subgraph L3["Layer 3 · Symptoms"]
S1["S1 Fertility collapse"]
S2["S2 Attention economy"]
S3["S3 Populism"]
S4["S4 Anomie / loneliness"]
end
D2 --> S2
D2 --> Y1
D4 --> Y1
D4 --> D1
D3 --> Y3
D3 --> S3
D1 --> Y2
D1 --> S1
Y1 --> Y2
Y3 --> S3
Y2 --> Y4
Y4 --> S1
S4 -. reacts back .-> D2
S1 -. reacts back .-> D3
M <--> L1
M <--> L2
M <--> L3The field, positioned
Each contemporary framework placed on the two axes the project turns on. The top-right — total and testable — is nearly empty, and that emptiness is the niche. The amber marker shows where this project aims. (The meaning dimension can't be shown here; see LANDSCAPE §9.)
The three candidate theories
Not three guesses at one answer but three kinds of theory — diagnostic, mechanistic, reflexive — that fit together. B is the mechanism beneath A's gap; C is the response to both; two named dangers stalk C.
flowchart TD
Cond["Today's condition<br/>(the 13 pressure-tests)"]
A["Theory A · Adaptation Gap<br/>diagnostic<br/>change-rate minus adaptation-rate"]
B["Theory B · Optimization Ecology<br/>mechanistic<br/>optimizers capture human drives"]
C["Theory C · Distributed Coherence<br/>reflexive / constructive<br/>a living commons of sense-making"]
Cond --> A
B -->|"mechanism beneath A's gap"| A
A -->|"if no single mind holds the whole"| C
B -->|"and optimizers outrun human ends"| C
Nz["Nietzsche: a method is not a meaning (D-004)"] -. warns .-> C
Int["the Integral trap: integrate without falsifiability = empty (Q-004)"] -. warns .-> CThe path to Code — a decision tree
The move is gated on what is bottlenecking, not enthusiasm. Chat is correct while the work is thinking; Code becomes correct only when there is a stable thing to build or a real quantity to compute. The honest branch includes "may never need heavy Code." A hard context-capacity limit in Chat can force Gate 1 earlier — see figure 08.
flowchart TD
Start["Should the project go to Code?"] --> Q1{"Is the document skeleton<br/>stable and ratified?"}
Q1 -->|No| Stay["Stay in Chat.<br/>The bottleneck is coherence,<br/>not engineering."]
Q1 -->|Yes| Q2{"Do you want public forking<br/>to begin?"}
Q2 -->|Not yet| Stay
Q2 -->|Yes| Light["LIGHT CODE — Gate 1<br/>repo · static site · deploy"]
Light --> Q3{"Does a theory have an<br/>operationalized, falsifiable<br/>claim with data? (Q-001)"}
Q3 -->|No| Hold["Hold at Light Code.<br/>Keep deliberating in Chat."]
Q3 -->|Yes| Q4{"Demonstrate Theory C as a<br/>prototype, or only argue for it?"}
Q4 -->|Only argue| Never["Heavy Code may never be needed.<br/>Lives as markdown + light site."]
Q4 -->|Demonstrate| Heavy["HEAVY CODE — Gate 2<br/>models · data · computation"]The Chat / Code shuttle
The working architecture: Chat deliberates, Code executes, the repo remembers. Neither side holds the whole project in one context — Chat loads only a slice, Code reads the full repo from disk. This is the fix for the context-window limit that forced our compaction, and it is the author's existing two-Claude writing workflow applied here.
flowchart LR
subgraph Chat["CHAT · the deliberation engine"]
direction TB
SP["load state pack<br/>map + target docs + open questions + last digest"] --> Del["run the panel<br/>designed disagreement · synthesis"]
Del --> WO["emit a work-order for Code<br/>files · propagation targets · checks"]
end
Repo[("THE REPO · shared memory / git<br/>docs · panel · outputs · logs · viz")]
subgraph Code["CODE · the executor & librarian"]
direction TB
Exec["write files · propagate · sweep<br/>regenerate viz · commit · deploy"] --> Dig["emit a session digest<br/>what changed · tree · counts · catches"]
end
WO ==> Exec
Exec <==> Repo
Repo -. loads slice .-> SP
Dig ==> SPTheory A as a signed causal loop
The gap, drawn — the first bridge from prose to a runnable model (THEORY_A_OPERATIONALIZED.md). Two loops decide the outcome: R1, a reinforcing trap (populism → weaker institutions → slower adaptation → wider gap), and B1, a delayed balancing loop (overwhelm → reform → faster adaptation → narrower gap). B1 is the accelerationist counter (D-006) made visible; which loop wins is empirical, not assumed.
flowchart TD
D4["D4 Machine intelligence"] -->|"+"| Rc["R_c · rate of systemic change"]
Rc -->|"+"| G["G · the adaptation gap"]
Ra["R_a · rate of adaptation"] -->|"-"| G
G -->|"+"| OV["Overwhelm · incomprehensibility"]
OV -->|"-"| TR["Institutional trust"]
OV -->|"+"| AN["Anomie / loneliness"]
OV -->|"+"| PO["Populism · demand for a simple story"]
D3["D3 Wealth pump · rival driver"] -.->|"+"| PO
PO -->|"-"| IC["Institutional capacity"]
TR -->|"+"| IC
IC -->|"+"| Ra
OV -->|"+ (delay)"| RF["Adaptive reform · institution-building"]
RF -->|"+"| RaSource of truth: docs/DIAGRAMS.md (also renders on GitHub). Open the standalone figures or the landscape & panel map. Contested claims point to the open questions.