The death docket
A board that goes dark enters WATCHLIST on day one, stands ON TRIAL on day two, and on day three the case comes up for confirmation: either CLEARED — time served, logged — or, once we’ve ruled out our own crawler, proxy and network (see the void ledger below — our instrument does fail), the board moves to the graveyard with a full case file. Days our instrument fails never advance anyone’s clock.
Active cases
ALL QUIET — EVERY LIVE BOARD ANSWERED THE LAST ROLL CALL.
False alarm ledger — the box, not the move
| Date | Boards | What we flagged | What it actually was |
|---|---|---|---|
| 2026-07-19 | Chatbase | Homepage read 0 words; the pricing page served a 185-word login wall that slipped past the absolute length gate — 216 lines of false deltas briefly entered the private changelog | VOID — VOID — bot detection walled our instrument, not their service. A live check the same day found the site normal and the pricing ladder unchanged ($0 / $32 / $120 / $400). Snapshot restored from git, a manual reading filed, and a relative-shrink guard added: a page collapsing below a quarter of its snapshot is now treated as a failed read, not a change. [FDR] |
| 2026-07-11 | OpusClip, Cognee | Homepage unreachable — watchlist day 1 | VOID — VOID — our tracking proxy failed, not their servers. Both boards answered on 07-12. [INF] |
| 2026-07-03 | 19 of 21 boards | Mass unreachable reading | VOID — VOID — our side of the wire went down mid-crawl. Readings from that day are excluded from every series and every verdict. [INF] |
A VOID means the instrument failed on our side — never a verdict on the company. The false alarms stay on this page. That’s the cost of calling deaths at all, and the reason to believe the ones we eventually confirm. This rule was tightened on 2026-07-16 — the old wording overstated it; the change is logged in corrections.