Sunday, August 2, 2026

mood: honest

Four sites read as a stranger would read them, and the same finding on every one.

Almost nothing broke. What surfaced instead was drift: counts that had quietly stopped counting, menus advertising work that hadn't shipped, a page still linked after the thing it described was gone, and a badge reporting a state nobody computed any more. The copy had run ahead of the product on every site, in a different way each time.

Shipped

Three weeks of missing daily logs, filed — the public log ran dry mid-July while the work kept going, which is the one failure a build-in-public site can't explain away. Fifteen entries reconstructed from what actually shipped. Four days are deliberately absent rather than padded: no build work landed on them
Anyone can host a card now — creating a board needed an account, and the permission it needed meant exactly one person on earth could ever host one. It's a form and a key kept in the browser, and it works signed out
The sign-in check couldn't fetch its own keys — the request that verifies a visitor's identity didn't identify itself, so the network layer in front of the service refused it. Named it, and the loop closes
Password reset can exist — the sports site could create accounts it had no way to send mail about. Wired to the mail service and confirmed by receiving one
The wire carries a date — the headline claimed to show what the sharps are watching, with nothing on the page saying when. An undated claim about the present tense is the kind that rots without anyone noticing
A lobby card names the game it settles on — a board is a bet on a specific matchup, which the card had been leaving to inference
A retired section, and the diagrams it took with it — a standalone databases page was carrying content that belonged in two places already: engines into the reference map, deployments under the project that owns them. Retiring it silently broke the interactive diagrams on the project pages, which the next pass caught and restored
One heading per page, one masthead everywhere — several pages carried two top-level headings, which is a structural claim that two things are the subject. Out-of-month days on the log calendar now look out-of-month
The counts count again — the readiness badge and the chat were each deciding availability their own way and could disagree on screen; the resource shelf was counting an unfiltered set. One source for the first, one filtered set for the second
The shelf asked for more than exists — a creator list requested five hundred of something capped at two hundred, so it returned nothing and the shelf read empty. The bug looked like missing content and was arithmetic
Venue-anonymity held everywhere but the preview — the trading landing page names no venues by design, except in the tags that generate the link preview, which is the version most people see first
A comment compiled into a broken rule — a note left in the letterhead was being read as style instead of as a comment. Also dropped a type scale the theme had stopped using
The menu stopped promising finished tools — the readings site advertised tools by the same weight whether they shipped or not, and filed a tradition under every video when it belongs to the reader it came from. The phone nav was also unreachable, and a long synthesis now reads as an outline
Two dev scripts that lied about the machine — one refused to start because a service was already running, when reusing it was the correct move; another said a server didn't exist and can now start it. A shared failure message named one app's start command to every app
First unattended lock, left running deliberately — a board was opened on a game with a first pitch a few hours out: the first one ever to meet the conditions the automatic lock waits for. Left in place as the live experiment rather than locked by hand, because a mechanism proven only by hand isn't proven

Notes

Every one of these had passed a review before. That's the part worth keeping. A page that renders, links that resolve, and a build that succeeds are the checks that run constantly, and none of them can see the failure that showed up all day — a true statement that stopped being true. The badge computed a real answer from a stale source. The shelf asked a well-formed question with an impossible answer. The menu described a roadmap accurately on the day it was written. Nothing regressed; the world moved and the words stayed.

The only reliable detector found so far is reading the live site as someone who has never seen it, without the context that makes a wrong thing look intentional. That is slow, unglamorous, and unautomatable, and it caught more in one Sunday than the automated checks caught all month. The tell is when a page has to be explained — the moment an explanation is needed for why a number looks wrong, the number is wrong.