Coverage
Every subsystem, every runnable command, every document type and every published page is either covered or explicitly excluded with a reason. Covered plus declared-excluded is the whole; anything that is neither fails the build by name.
Discovery walks lib/mix/tasks, viewer and scripts in the colony repository, plus the package manifests of two others. A forensic review found a real server outside those roots — production/guest/pubgate/server.cjs, which binds a port on all interfaces — that is in neither the covered list nor the excluded one, and 52 runnable scripts under runs/ against the 16 under scripts/that form the denominator. The table below is honest about those four roots and says nothing about the rest of the estate.
The mutation that was supposed to prove the claim could not have: it appended a fabricated entry to the discovery result rather than putting a file on disk, so it proved the axis reacts to a longer list and not that discovery finds a new file. It now writes a real file into a real walk root. A proof-of-bite that cannot bite is the defect this whole site is organised against, and it was sitting inside the check that says so.
The four axes
| Axis | Denominator | Total | Covered | Excluded | Gap |
|---|---|---|---|---|---|
| Subsystems | declared | 8 | 8 | 0 | 0 |
| Entry points | discovered | 104 | 80 | 24 | 0 |
| Document types | declared | 8 | 8 | 0 | 0 |
| Published pages | discovered | 524 | 524 | 0 | 0 |
| All axes | 644 | 620 | 24 | 0 | |
Discovered means the denominator is measured from the source repositories or from the ingest, so it grows on its own. Declared means the list is editorial — a shorter list would score the same, and saying so is the only defence against that.
The ratchet: 100% cannot collapse and cannot reduce
A percentage is the most collapsible statistic there is. Covered ÷ total stays at exactly 1.0 under two completely different disasters, and the table above is blind to both because in each case the sum still closes and the gap is still zero:
Collapse — the denominator shrinks. A repository moves, a discovery rule is tidied away, a corpus stops resolving. 100% of a smaller world, reported identically.
Reduction — work moves from covered into excluded. Every exclusion carries a reason and the arithmetic still closes, so the gate is satisfied while the guides document less with each change.
So every measured quantity is also held against a committed floor, and the floor is compared against its own previous version in version control. Lowering one is allowed; lowering one silently is not — it requires a recorded amendment saying what moved and why. A floor that can be edited down in the same change that breaches it is not a floor.
Growth is free and needs no ceremony — this estate adds servers and documents constantly, and a gate that fights ordinary work gets switched off. Only going backwards costs anything.
Amendments
Every time a floor was deliberately lowered, with the reason given at the time.
| Date | What | Why |
|---|---|---|
| 2026-08-01 | Lowered floors pages_total (292 -> 291) and corpora_pages.workbench (2 -> 1). | A forensic pass held all 292 published pages against the commit each citation names and found ONE whose published bytes were an uncommitted working-tree edit published under a commit sha that does not contain them (workbench/living-science-walkthrough). The ingest now fences any document whose own bytes are uncommitted, per path, so it cannot assert a provenance it does not have. The page count falls by one because a page that was making a false claim stopped being published. This is a REDUCTION IN COUNT AND AN INCREASE IN CORRECTNESS, which is why the floor is lowered deliberately rather than the fence being weakened to preserve a number. The remaining four fenced documents return the moment the workbench worktree is committed. |
| 2026-08-02 | Lowered floor article_chars.run-it (8678 -> 8667), a drop of 11 characters, as part of re-pinning the baseline for the 493-page expansion. | No prose was removed. The run-it page body is byte-identical to its previous version. The 11-character drop is an earlier fix catching up: a dead internal link to a flagellar-motor route that does not exist was corrected to the live route, removing the 11 characters of the word laboratory. The floor was pinned before that fix and is only now re-emitted. This is a reduction in count and an increase in correctness -- a working link is shorter than a broken one -- so the floor article_chars.run-it is lowered deliberately and recorded here rather than the page being padded to preserve a number. |
All 81 bounds, and the distance to each
| Bound | Kind | Now | Limit | Margin |
|---|---|---|---|---|
| entry points discovered · mix-task | floor | 8 | 8 | 0 |
| entry points discovered · server | floor | 8 | 8 | 0 |
| entry points discovered · powershell | floor | 42 | 42 | 0 |
| entry points discovered · elixir-script | floor | 16 | 16 | 0 |
| entry points discovered · npm-script | floor | 30 | 30 | 0 |
| entry points discovered · total | floor | 104 | 104 | 0 |
| pages published · encyclopedia | floor | 45 | 39 | 6 |
| pages published · cookbook | floor | 34 | 34 | 0 |
| pages published · control-plane | floor | 33 | 33 | 0 |
| pages published · flagellum | floor | 14 | 14 | 0 |
| pages published · workbench | floor | 1 | 1 | 0 |
| pages published · minecraft | floor | 87 | 87 | 0 |
| pages published · evidence | floor | 105 | 105 | 0 |
| pages published · gpt-pack | floor | 2 | 2 | 0 |
| pages published · builder | floor | 5 | 5 | 0 |
| pages published · cookbook-repo | floor | 6 | 6 | 0 |
| pages published · hierarchical-aif | floor | 64 | 64 | 0 |
| pages published · audits | floor | 3 | 3 | 0 |
| pages published · flagellum-repo | floor | 3 | 3 | 0 |
| pages published · science-lab | floor | 17 | 17 | 0 |
| pages published · films | floor | 8 | 8 | 0 |
| pages published · broadcast | floor | 56 | 56 | 0 |
| pages published · colony-builder | floor | 7 | 7 | 0 |
| pages published · estate | floor | 9 | 9 | 0 |
| pages published · lexicon | floor | 8 | 8 | 0 |
| pages published · constants | floor | 7 | 7 | 0 |
| pages published · total | floor | 524 | 508 | 16 |
| pages in route · start | floor | 9 | 9 | 0 |
| pages in route · install-run | floor | 6 | 6 | 0 |
| pages in route · method | floor | 11 | 11 | 0 |
| pages in route · colony | floor | 4 | 4 | 0 |
| pages in route · specs | floor | 17 | 17 | 0 |
| pages in route · broadcast | floor | 57 | 57 | 0 |
| pages in route · operator | floor | 8 | 8 | 0 |
| pages in route · architecture | floor | 33 | 33 | 0 |
| pages in route · flagellum | floor | 9 | 9 | 0 |
| pages in route · workbench | floor | 2 | 2 | 0 |
| pages in route · reports | floor | 23 | 23 | 0 |
| pages in route · lab-team | floor | 7 | 7 | 0 |
| pages in route · encyclopedia-method | floor | 16 | 16 | 0 |
| pages in route · encyclopedia-nature | floor | 12 | 12 | 0 |
| pages in route · encyclopedia-stack | floor | 11 | 11 | 0 |
| pages in route · cookbook-kitchen | floor | 8 | 8 | 0 |
| pages in route · cookbook-stack | floor | 14 | 14 | 0 |
| pages in route · cookbook-nature | floor | 12 | 12 | 0 |
| pages in route · plans | floor | 15 | 15 | 0 |
| pages in route · evidence-receipts | floor | 62 | 62 | 0 |
| pages in route · evidence-prereg | floor | 37 | 37 | 0 |
| pages in route · evidence-handoffs | floor | 12 | 12 | 0 |
| pages in route · pack-and-reader | floor | 7 | 7 | 0 |
| pages in route · builder | floor | 12 | 12 | 0 |
| pages in route · haif-program | floor | 21 | 21 | 0 |
| pages in route · haif-prereg | floor | 8 | 8 | 0 |
| pages in route · haif-results | floor | 35 | 35 | 0 |
| pages in route · science-lab | floor | 17 | 17 | 0 |
| pages in route · films | floor | 8 | 8 | 0 |
| pages in route · lexicon | floor | 8 | 8 | 0 |
| pages in route · constants | floor | 7 | 7 | 0 |
| RUNNABLE markers | floor | 16 | 16 | 0 |
| entry points documented | floor | 80 | 80 | 0 |
| entry points excluded | ceiling | 24 | 24 | 0 |
| subsystems | floor | 8 | 8 | 0 |
| document types | floor | 8 | 8 | 0 |
| articles | floor | 13 | 13 | 0 |
| resolved citations | floor | 59 | 59 | 0 |
| quoted source blocks | floor | 15 | 15 | 0 |
| curated routes | floor | 33 | 31 | 2 |
| pages in no route | ceiling | 0 | 0 | 0 |
| substance · start-here | floor | 3806 | 2854 | 952 |
| substance · the-colony | floor | 2657 | 1992 | 665 |
| substance · the-producer | floor | 2836 | 2127 | 709 |
| substance · the-control-plane | floor | 3324 | 2493 | 831 |
| substance · the-brain | floor | 4011 | 3008 | 1003 |
| substance · the-operator-plane | floor | 3582 | 2686 | 896 |
| substance · the-flagellar-motor | floor | 5492 | 4119 | 1373 |
| substance · the-broadcast-suite | floor | 12659 | 9494 | 3165 |
| substance · quick-start | floor | 3645 | 2733 | 912 |
| substance · install | floor | 7492 | 5619 | 1873 |
| substance · run-it | floor | 8667 | 6500 | 2167 |
| substance · maintenance | floor | 8190 | 6142 | 2048 |
| substance · how-to | floor | 5170 | 3877 | 1293 |
A margin of zero is not a failure — it means the quantity is sitting exactly on its floor, which is where a freshly-measured baseline puts most things. It does mean the next reduction there fails the build.
Subsystems, in two layers each
Understanding without the ability to run something does not transfer; the ability to run something without understanding it does not survive the first problem. So each subsystem is documented twice.
| Subsystem | Understand it | Run it yourself |
|---|---|---|
| The colony | the-colony | run-it |
| The Producer | the-producer | run-it |
| The active-inference brain | the-brain | run-it |
| The scientific control plane | the-control-plane | run-it |
| The operator plane | the-operator-plane | run-it |
| The broadcast suite | the-broadcast-suite | the-broadcast-suite |
| The flagellar-motor laboratory | the-flagellar-motor | run-it |
| The math workbench | the-flagellar-motor | run-it |
The eight document types
| Type | Satisfied by | Reachable from |
|---|---|---|
| Quick start | quick-start | /articles/ |
| Install guide | install | /articles/ |
| User guides | run-it, the-broadcast-suite | /articles/ |
| Manuals | the-operator-plane, the-broadcast-suite | /articles/ |
| How-to guides | how-to | /articles/ |
| Maintenance guides | maintenance | /articles/ |
| Specs | the specs route, at least 8 pages | /wiki/ |
| Code citations | at least 40 resolved source citations | /articles/ |
Reachability is checked against the navigation component that actually renders the site, not against a copy of it kept here. A declared copy could certify a route the site no longer has.
What is deliberately excluded, and why
24 runnable entry points are documented nowhere on this site. Each is named with its reason, because an exclusion nobody can see is an omission with better manners.
powershell -File viewer/hud/_install_elevated_wrapper.ps1
Part of the native HUD's build-and-package chain: compiling the widget executable, fetching a service-wrapper binary, and an elevation shim. These build the artifact rather than run or maintain the system, and a reader who wants the HUD installs the built service rather than compiling it. Named here so their existence is not hidden.
powershell -File viewer/hud/build_exe.ps1
Part of the native HUD's build-and-package chain: compiling the widget executable, fetching a service-wrapper binary, and an elevation shim. These build the artifact rather than run or maintain the system, and a reader who wants the HUD installs the built service rather than compiling it. Named here so their existence is not hidden.
powershell -File viewer/hud/download_nssm.ps1
Part of the native HUD's build-and-package chain: compiling the widget executable, fetching a service-wrapper binary, and an elevation shim. These build the artifact rather than run or maintain the system, and a reader who wants the HUD installs the built service rather than compiling it. Named here so their existence is not hidden.
powershell -File viewer/hud/native/_cert_and_sign_elevated.ps1
Elevated steps of the native HUD's code-signing and service-registration chain, invoked while developing the widget itself. Documenting a code-signing procedure for a certificate the reader cannot possess would be a recipe that ends at a wall. The two elevated scripts a reader DOES need — the launcher install and the service swap — are covered in the install guide, and the two restart drills are covered in the maintenance guide.
powershell -File viewer/hud/native/_sign_and_reinstall_elevated.ps1
Elevated steps of the native HUD's code-signing and service-registration chain, invoked while developing the widget itself. Documenting a code-signing procedure for a certificate the reader cannot possess would be a recipe that ends at a wall. The two elevated scripts a reader DOES need — the launcher install and the service swap — are covered in the install guide, and the two restart drills are covered in the maintenance guide.
powershell -File viewer/hud/native/_sign_widget_elevated.ps1
Elevated steps of the native HUD's code-signing and service-registration chain, invoked while developing the widget itself. Documenting a code-signing procedure for a certificate the reader cannot possess would be a recipe that ends at a wall. The two elevated scripts a reader DOES need — the launcher install and the service swap — are covered in the install guide, and the two restart drills are covered in the maintenance guide.
powershell -File viewer/hud/native/_stop_service_elevated.ps1
Elevated steps of the native HUD's code-signing and service-registration chain, invoked while developing the widget itself. Documenting a code-signing procedure for a certificate the reader cannot possess would be a recipe that ends at a wall. The two elevated scripts a reader DOES need — the launcher install and the service swap — are covered in the install guide, and the two restart drills are covered in the maintenance guide.
powershell -File viewer/hud/native/_update_service_binaries_elevated.ps1
Elevated steps of the native HUD's code-signing and service-registration chain, invoked while developing the widget itself. Documenting a code-signing procedure for a certificate the reader cannot possess would be a recipe that ends at a wall. The two elevated scripts a reader DOES need — the launcher install and the service swap — are covered in the install guide, and the two restart drills are covered in the maintenance guide.
powershell -File viewer/hud/native/_urlacl_and_networkservice_elevated.ps1
Elevated steps of the native HUD's code-signing and service-registration chain, invoked while developing the widget itself. Documenting a code-signing procedure for a certificate the reader cannot possess would be a recipe that ends at a wall. The two elevated scripts a reader DOES need — the launcher install and the service swap — are covered in the install guide, and the two restart drills are covered in the maintenance guide.
npm run dev
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run build
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run start
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run test
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run experiment:ingest
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run experiment:run
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run experiment:verify
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run science:run
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run science:verify
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run cross-study:ingest
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run cross-study:verify-raw
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run cross-study:run
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run cross-study:verify
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run lint
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
npm run db:generate
The math workbench is a git WORKTREE of the flagellum repository on a different branch, so its package file is the same package file. Measured 2026-08-01: 14 of its 15 scripts are byte-identical to the flagellum ones already documented, and the 15th differs only by adding one test file to the same test command. Documenting them twice would pad the coverage count without telling a reader anything they do not already have. The workbench's own route is covered in the run-it guide.
Routes through the wiki
33 routes covering 524 published pages. Every page belongs to a route; there is no default bucket, and a document that matches none of them fails the build rather than landing nowhere.
- Start here · 9
- Installing and running it · 6
- The method and its discipline · 11
- The colony and its world · 4
- Typed specs — organs, world and runtime · 17
- Broadcast, studio and run of show · 57
- The operator plane · 8
- Architecture and decisions · 33
- The flagellar-motor laboratory · 9
- The math workbench · 2
- Reports, audits and validation · 23
- The adversarial review personas · 7
- Encyclopedia — method and ledgers · 16
- Encyclopedia — the Natura wing · 12
- Encyclopedia — the stack, L0 to L12 · 11
- Cookbook — kitchen rules · 8
- Cookbook — recipes for the stack · 14
- Cookbook — recipes from nature · 12
- Plans, status and handover · 15
- Receipts — the dated record · 62
- Pre-registrations and RED verdicts · 37
- Handoffs and resume states · 12
- The GPT pack and the offline reader · 7
- The builder briefs · 12
- Hierarchical active inference — the programme · 21
- Hierarchical AIF — predictions committed first · 8
- Hierarchical AIF — results and adversarial verification · 35
- The science lab — proofs, limits and sources · 17
- The films · 8
- The lexicon — one concept, five registers · 8
- Constants, ratios and the nature ledger · 7
- The engraved plates · 10
- Encyclopedia — Track A, the commercial appendix · 6
What this table cannot tell you
It cannot tell you a guide is followable.Coverage proves nothing is unaccounted for. It says nothing about whether the quick start works on a machine that is not the author’s, whether the ordering makes sense to somebody meeting this for the first time, or whether an explanation actually explains. Only a stranger following it can answer that, and no gate substitutes for one.
It also cannot see sensitive narrative, which is the other thing no scanner here can do. Both limits are printed rather than left to be discovered.