Colophon

1. 01Planned first

   Claude surveyed every repository, asked four questions about look, name, sources and scope, and wrote a plan with a design review folded in. Nothing was built until the plan was approved.

2. 02The rules are checked by tests

   The brand palette is checked against the brand kit. Every text color pair is checked for contrast. A lint fails the build on em dashes, on words the owner never uses, on emails, private links and anything on a hashed list of names that must never appear. The same lint runs again over the finished pages.

3. 03The LED wall uses SignalWall's code

   SignalWall's transitions were ported to TypeScript and held to the board's golden test images, pixel for pixel, at two panel widths. Only frames built from demo data are allowed on the page; calendar, flight and fantasy screens are refused by name.

4. 04The numbers come from the commit history

   A harvest reads the commit history of every project and keeps only counts and dates: no messages, no emails, no links. Running it again updates the totals and the River.

5. 05Adding a project

   Each chapter is a small, validated data file. A new project becomes a new file, and the Playbook, the River and the rail pick it up. A chapter cannot go public without the owner's dated sign-off.

Set in EB Garamond and Inter, both under the SIL Open Font License, served from this site. No analytics, no third-party requests. Numbers as of October 7, 2026.