Architecture
How the engine is structured and why the parts are arranged the way they are.
The full picture: ingest, prosecution, synthesis, and the verdict gate. What runs, in what order, and what the engine refuses to decide on its own.
Why premature agreement is the failure mode, not the win condition. The reward function that makes beliefs fight instead of consolidate.
Why no interface ever shows one user another user's verdict. The isolation guarantee, how it is enforced, and the freedom-to-operate basis behind it.
How your beliefs are mapped, linked, and surfaced. The shared visualization layer and how it is separated from the inference engine beneath it.
The Brigade
Fourteen agents, one synthesizer, one auditor. What each does and what each refuses to do.
The specialist roster: roles, attack postures, steelman obligations, and the defer protocol when prosecution reaches its epistemic limit.
Presents the surviving beliefs. Draws no conclusion. Why synth-creep, the tendency to usurp the verdict, is the highest-severity failure mode.
Holds no position, attacks no belief, audits the other fourteen. The steel gate, herd check, fairness loop, and the aporia declaration. Why he is not optional.
The engine never rules. rule() is called only by a user action. If you extend the engine and this stops being true, the architecture has broken. The aporia rate is protected for the same reason: Socrates admitting "I don't know" is a feature, not a failure to suppress.
Ground Truth
How ratified beliefs become ground truth, and what that word actually means.
The Pass is the engagement loop; Calibration is the outcome loop. They run on separate tracks. A ratified belief that later fails evidence is re-plated, never overruled retroactively.
The survival score. How beliefs are scored against disagreement. Why there is no separate survival() function.
When a kept belief meets counter-evidence, it is submitted again, not overruled. The cadence is evidence-triggered and stakes-scaled. How to configure the re-plate threshold.
Mise & Epistemic Kind
The tagger that reads each belief before prosecution begins.
Mise assigns each belief a kind: FACT, PREDICTION, VALUE, or PREFERENCE. The brigade attacks the first two and surfaces contradictions in the latter two. Values are never refuted.
How to manually correct a Mise classification, and when the distinction between PREDICTION and VALUE changes the prosecution's approach entirely.
The Pass
The verdict interface. Three actions, no fourth option.
The only three things you can do with a belief that survives prosecution. What each action writes to the ground truth store and how behavior becomes the signal.
How prosecution findings are surfaced: the ticket layout, the Clarity Index reading, and the synthesizer's presentation. Reading a run without losing the thread.
Socrates, Agent 15
The auditor of the auditors. His rules, his limits, and why there is no Agent 16.
Steel gate, herd check, fairness, and aporia. The four things he checks. What each catches, and what "I don't know" looks like in a run output.
Dropping Socrates ships a forensic instrument aimed at a person with no oversight. The moral architecture of the system and the regress that halts in him.
Verifying that Socrates catches strawmen in production, not just in prompts. The test harness, what it checks, and how to extend it.
Integration Guide
Connecting your second brain to the engine. Obsidian, Roam, Notion, Logseq, and the raw ingest API.
What the engine accepts: atomic note format, required fields, belief extraction heuristics, and what to do when a note contains more than one claim.
Select notes, tag as beliefs, and submit to a Colosseum run directly from your vault. Installation and configuration.
Block-reference export, graph-aware belief extraction, and the page-property conventions the engine looks for.
For custom integrations. Authentication, endpoints, rate limits, and response formats.
Security & Privacy
What is stored, for how long, and what the engine can never share with another user.
Beliefs, runs, verdicts, and ground truth records. What is persisted and what is ephemeral. Retention periods and deletion mechanics.
The unanimous firewall in technical terms. How assert_solitary() is enforced, what raises, and what can never degrade silently.