Documents

The documents this site was built from and the notes it is run by, published whole. Each is a markdown file in the repository, which is the source of truth, and a page rendered from it on every release, which is presentation. The rendered page links the raw file at the top; the raw file is what a reader checks the site against.

• Design documents: the MVP build brief (the instruction set), what it got wrong, and the four documents that carry the reasoning.
• Operations: how a release works, what only a human can do, the GCP bootstrap as commands, the DNS record, the repository protections.
• Reality: what is built, by status, generated from data/features.json. The same data renders /shipped/.

Why publish the brief at all

A reader who wants to check whether this site is faithful to what it was asked to build should not have to reconstruct the brief from the site. Publishing the commission, and the corrections beside it, makes the site checkable against something other than its own claims. That is the same argument the reality document makes, pointed at this site.

For agents

llms.txt lists every page and document with a one-line description; llms-full.txt is all of them in one fetch. Every HTML page has a markdown twin at the same path with the extension swapped, and links inside the markdown point at markdown.