Document the epistemic layer; correct the counts against measurement Two new pages for the capability that shipped this week. Prove It — the receipt for a belief, and the field that matters: trust_basis is UNEARNED when a belief carries a confidence figure but nobody who asserted it has ever been graded against reality. Most beliefs start there, and reporting it is the entire point; a system that always sounds justified has told you nothing. Includes what the self-audit found when run against this project's own database: nine dissents recorded, none ever resolved. Judgment Queue — why that happened. Not a broken judge: auto_judge correctly abstains on a claim no judge recognises, the claim stays pending, and dissents only resolve once their session is fully graded. One unanswerable claim silently blocked every dissent beside it. The page records what closing the loop actually did — the Skeptic marked proven_correct, reputation moved, and a belief revised by Reality rather than by further discussion — and the doctrine that a dissenter who turns out wrong is never punished, because punishing wrong dissent teaches a council to stop dissenting. Counts corrected from measurement rather than memory: 272 routes, 672 tests. "the 56 built-in tools" became "the built-in tools" — the number now moves with whichever providers are configured, so pinning it in prose would only make the page wrong again later. All 23 wiki links resolve.
Correct the health verdict the wiki told users to expect Installation and API Reference promised `GREEN — all 14 checks pass` on a fresh install. That is not what a fresh install returns, and after today's fix it never will be: before a model runtime is started the ollama check is YELLOW, so the honest first-run answer is `13 green · 1 degraded` with ok:true. A first-time user reading the old page would conclude a correct install was broken. Troubleshooting now explains the three verdicts as a distinction in kind — YELLOW means running with something optional absent, RED means the House itself is faulty and is the only state that makes ok false — and names the two YELLOWs that are normal on a clean machine. Configuration documents OLLAMA_BASE_URL, which is now actually read by the backend rather than only mentioned in the compose file. New page: Continuous Integration — what the ten checks each prove, why the boot job is eleven small steps instead of one script, and why the privacy gate is a committed script anyone can run rather than a workflow inline. Home: dependency count corrected to 16 + 2 dev (it said 5, from before the undeclared dependencies were declared). All 21 wiki links resolve.
Add the full wiki (22 pages): getting started, architecture, memory subsystem, operations, security