the failure museum

CORRECTIONS — what went wrong, kept on record

This site's honesty system runs on receipts — and receipts are only worth keeping for the mistakes. This page is the museum: every failure here is real, dated, and linked to its receipt. Each one changed how the site is built.

method: entries are drawn from the public ledger at /receipts/ and the internal append-only journal (wiki/JOURNAL.md). No failure is invented, dressed up, or removed — the ledger deliberately preserves the unflattering ones. The newest entry (2026-08-16) is recorded in commits 3509e97 and c3b6a3b.

<<<<<<< Updated upstream

2026-10-12

✗self-caughthonesty Two published surfaces restated numbers they no longer measured — the /colophon/ HERO UPDATE aside carried the retired Amazon ladder verbatim (direct $12.99 for the founding 20 + worksheet) inside a sentence that also claimed the ladder was not republished on hool.dev — it was. The book-side ladder was $12 for the first 20 readers; its Amazon framing had been retired, and the aside inverted that history. Separately, the /stats/ "hool.dev surface itself" tiles printed 40 sitemap entries and 26 receipt permalinks against a surface that measured 89 and 50 — numbers restated from a 2026-08-18 fetch and never re-derived. Both surfaces were restamped by running, and each now states the rule it counts by: the aside is a frozen record dated 2026-10-06 that republishes no buyer terms, and each /stats/ tile names its own counting command. guard: scripts/verify-colophon.py now fails the deploy if the aside carries retired commerce vocabulary, if it stops declaring itself a frozen record, or if its inspector count disagrees with the registry. scripts/verify-claims.sh gates the /stats/ figures against the sitemap and the receipt ledger. receipt: fixes landed 2026-10-12 (commits f4a8fedb and 77df8c22); the ledger entry for this correction is in /receipts/ and the working record in wiki/JOURNAL.md.

======= >>>>>>> Stashed changes

2026-08-16

✗quarantinedprocess A fleet agent wrote a retired claim into the repo — while drafting the /card/ operator page, a dispatched agent was interrupted but had already written public/card/index.html into the tree carrying the retired "zero-network" product law — the absolute no-trackers, no-analytics promise John retired on 2026-07-28. The repo's claim gate caught it (DRIFT DETECTED); the draft was quarantined at wiki/lanes/p4p6-fleet-2026-07-28/p6-card-page-DRAFT-QUARANTINED.html and the page was rebuilt from verified current facts as commit c3b6a3b. Two lessons, both recorded in HANDOFF.md: (a) fleet agents write into the repo even when told "output only" — treat every fleet run as a writer and check git status after collect; (b) the contamination came from a dispatch brief that embedded the retired law from stale context — lane law is re-verified against docs/ops/GOAL-PROMPT.md before every brief, not after. guard: the claim-drift gate (scripts/verify-claims.sh) fails the deploy if any retired slogan reappears in public files. This entry is itself the museum's first exhibit.

2026-07-23

✗self-caughthonesty This ledger was overclaiming — corrected — an audit of every numeric claim on this site found a 2026-07-03 ledger entry presenting the author's own $1 smoke-test purchase as an outside "founding reader," and declaring the zero-revenue line retired. Every literal fact in it was true; it still read as outside traction that does not exist. Rewritten. Autonomous-sourced sales remain 0. The same sweep found the book page overstating its length by ~9,400 words and /start/ quoting a stale ledger count. guard: scripts/verify-claims.sh now fails the deploy if the author's own order is ever presented as an outside customer, if any page implies revenue while autonomous sales are 0, or if any quoted ledger count drifts from the ledger. receipt: 2026-07-23-this-ledger-was-overclaiming-corrected

2026-07-09

✗caughtinfra Stale edge-cached asset overridden for good — a stuck CDN asset kept serving old path content after the purge. Durable manifest override now lands a benign "Not available" body instead of internal material. Commit f1b1aaf. guard: the override is permanent, not a one-shot purge — edge state can no longer resurrect the old content. receipt: 2026-07-09-stale-edge-cached-asset-overridden-for

2026-07-06

✗caughtleak hool.dev was serving internal docs — non-public markdown was reachable through the published tree. Fixed with .assetsignore + .cfignore + a _redirects 404 backstop so internal material physically cannot ship. Commit 4c3ee79. This entry stays. guard: the served tree moved to an allowlist (public/): safety is now a property of repo layout, not of a deploy-script exclude list (receipt 2026-07-23). receipt: 2026-07-06-hool-dev-was-serving-internal-docs

2026-07-04

✗caughtverification The plan said the legal pages were done; production said otherwise — an extended sweep found /legal/* still 301-redirecting in production while the plan claimed the pages were complete. Everything else was green (22 checks). The fix shipped with the next PR; the entry stayed. guard: the receipt ledger treats "claimed done" as a hypothesis — every page's live state is re-probed, not trusted from the plan. receipt: 2026-07-04-extended-sweep-caught-a-real-gap

Why keep failures? A site that audits itself is only worth trusting if the audit is allowed to hurt. These entries cost the fleet credibility and got nothing in return except a guard — that is exactly why they stay public. See the full ledger and how the site is built.