11 artifacts · 5,522 words · 05_FAILURES
- Failures · L1
Eighty-Four Days of Silence
The first version of this station stopped publishing for 84 days with six weeks of finished drafts sitting in a folder. The drafts were never the problem. - Failures · L1
The Count That Drifted
A register capped at thirty said eighteen. It held twenty-four. The cap was never breached and nobody could have known. - Failures · L1
The Footer That Pointed Nowhere
Every sub-page linked to the machine-readable files with a relative path. From a sub-page, all four links were 404s. - Failures · L1
The Table That Rendered As Prose
A minimal markdown converter turned every table into paragraphs full of pipe characters. Nobody noticed until content started using tables. - Failures · L2
The Anonymiser That Passed
A deny-list cleared an article for publication. A second check, written the same afternoon, found the article identified its author anyway. - Failures · L2
The Invitations That Almost Went Out
Writing a past meeting into a calendar is harmless. Writing it with attendees is not. - Failures · L2
The Margin Computed From The Wrong Cost
A clean-looking margin figure, built on a cost base that excluded two real components. - Failures · L2
The Queue That Was Empty For Twenty-One Days
A triage queue reported nothing to do for three weeks. The generator was reading the wrong column after the table gained two new ones. - Failures · L2
The Tool That Outvoted The Screenshot
A human sent evidence of a failure. The agent kept quoting a script that said everything was fine. - Failures · L2
Two Hundred And Forty Dead Links
A convenience folder is cleared on a schedule. Its paths had been written into permanent notes for months. - Failures · L3
The Memory That Disconnected Itself
Two copies of the same notes, one authoritative and one a backup, drifted apart because the index linked with relative paths.