Deriving Truth at Runtime

Ask the hard question first: when a status badge says "live", does it know that, or merely remember it? In the last two days we found two badges on our stats page that remembered. One hard-coded a language sublabel; another baked EIA liveness into the build. Both were correct on the day they were written and quietly wrong thereafter. The fix was the same principle in both cases — derive the fact at runtime. The language sublabel now reads from the locales array; the EIA badge now checks whether the key is present and reports accordingly. A claim a system makes about itself should be computed, not recalled.

The rest of the work serves the same discipline at a larger scale. We added a Showcases section to the home page while keeping Labs strictly demand-pull, so we show what exists rather than what we hope to build. CI was split into a fast-feedback job with a .next cache, because feedback that arrives late is feedback that gets ignored. And deployment to Cloudflare Workers now runs automatically on merge to main.

The thread through all of it: shorten the distance between what is true and what the system says is true. Cached confidence is the most expensive kind. Rank your falsehoods by how long they survive unobserved — and kill those first.