What is not here

Architecture & Decisions

The Flagellar Motor

The Colony & the Method

Evidence & Verdicts

The Reader and its Deploy Bundle

The Broadcast Platform

The Builder — colony cold start

8 documents are not published because their own bytes are uncommitted in the source repository. Every page here asserts “this is this file, at this commit” — and a document that exists only as an uncommitted edit cannot make that claim truthfully.

This fence was added on 2026-08-01 after a forensic pass held all 292 published pages against the commit each citation named. One page failed: its published bytes were a working-tree edit published under a commit sha that did not contain them. 291 of 292 were sound. The page count on this site fell by one as a result — a reduction in count and an increase in correctness, recorded as an amendment on the coverage page rather than quietly absorbed. The fence is per file: unrelated uncommitted work elsewhere in a source repository does not withhold anything.

8 documents were not rendered because an identical document had already been ingested from another repository — proved by sha256, never by filename. Two files with the same name and different contents are two documents; two files with different names and the same bytes are one.

These arise because one repository is a git worktree of another on a different branch, so its documentation directory is largely the same directory. Publishing both copies would put the same page in the wiki twice under two names, which is the smallest possible version of the findability problem this site is built to avoid.

This page is one half of a pair. It names what was withheld; the coverage page names what was kept and proves that every subsystem, every runnable command, every document type and every published page is either covered or excluded on purpose.

A site that only publishes its omissions still leaves a reader unable to tell thorough from selective. Both halves are needed and both are computed rather than asserted.

Everything above was caught by a pattern — an address shape, a hostname shape, a key shape. No scanner recognises sensitive narrative. A document describing a client engagement in prose, naming nobody and matching no pattern, passes every check that produced this page.

That is not hypothetical in this estate. A large archive of development transcripts was verified to have had its credentials redacted perfectly — zero surviving tokens across 1.74 GB — while its narrative content was the actual exposure. Human review of new prose is required, and nothing here replaces it.