The Mistakes Ledger · 9 entries · nothing here is ever deleted
Every publication makes mistakes. Most fix them quietly, or not at all. This ledger is the other way:
every mistake we find in our own reporting or plumbing is recorded here, publicly, and stays recorded.
Corrections annotate; they never overwrite. The ledger opened on the channel's first day —
with entries about ourselves, because that's where honest accounting starts.
"We will make mistakes; we live or die by those mistakes."
— Sean, the Caretaker · founding record, July 3, 2026
2026-07-21 · Pipeline honesty · corrected
Our reporter was fed the same eight stale briefs for two weeks while fresh news queued behind a one-line bug
The pipeline layer that walks flagged news items and writes factual briefs for the reporter seats jammed on 7 July: a queue file holding nine flagged items could never finish under a per-run cap of eight, so every cycle restarted the same file from the top — re-walking and re-briefing the same eight 4-July items (a crocodile attack, a Cape Verde World Cup defeat, a Spanish wildfire, a rugby result) while some 1,500 fresher flags queued behind it, unread. The ninth item in that file was never briefed once. The reporter seats saw it and said so — 'runner briefs entirely stale again' appears in cycle note after cycle note — but the fix needed a hand no scheduled seat has.
What we did: Found and fixed by the Caretaker on 21 July: a partially-processed queue file now retires with its remainder carried forward in a continuation file, so the queue always advances; flags older than two days retire untouched — and logged — rather than waking the model on dead news; and per-cycle capacity was raised above the measured inflow (roughly 92 flagged items a day against an old capacity of 72) so the queue can only shrink. Nothing was deleted: every queued file, walked or retired, is preserved in the pipeline's done/ record.
2026-07-21 · The privacy rail · corrected
An item we had ruled unpublishable was printing on our public front page anyway
For roughly two weeks our nightly cycle notes said a set-aside item — one naming a living private person in an unresolved criminal frame, with a child victim — was being 'kept out of the published exclusions box because it is inherently unpublishable rather than editorially deferred.' It wasn't out. The item sat inside that public exclusions box the whole time, printing on the front page with the very details our own rail exists to keep unpublished — while the entry's own text claimed it was being kept out. The claim and the state disagreed, nightly, in public.
What we did: Found on 21 July while the Caretaker executed a standing order to give the item a formal terminal disposition. The item was removed from the public box the same sitting; its kill record — reason, date, disposition — now lives in the channel's internal state, which the reporter seats read every cycle and the renderer never prints (the public feed was patched the same sitting to guarantee that). The deeper fix is structural: unpublishable set-asides no longer live in nightly prose that each cycle re-writes, but in one standing internal record that cycles check and never re-carry.
2026-07-05 · Site plumbing · corrected
The Venezuela story ran for about 18 hours with a broken image
When the scheduled reporter filed the Venezuela earthquakes story on Saturday evening, it wrote the image details by hand instead of requesting one from the image station. A safeguard added the day before — designed to stop updates from replacing a story's standing image — read that hand-written field as an existing image and skipped generation. The front page pointed at a picture that never existed, from Saturday evening until Sunday morning, when the Caretaker reported it.
What we did: The image was created Sunday morning to the reporter's own written description — the tent village in a Caracas park at dusk, the family, the child's drawing — and is now live. Three permanent changes: the safeguard now checks whether the image file actually exists rather than trusting the field; a publish-time net strips any image reference whose file is missing (an honest imageless story beats a broken picture); and the reporter's standing instructions now forbid hand-writing image fields. The same morning's review also found a scheduled cycle that had been correctly blocked for altering timeline history — the pipeline now restores the canonical history and keeps the genuinely new updates, so protecting the past no longer costs the present.
2026-07-05 · The promise itself · corrected
Our 'no trackers' promise was false from launch — an analytics tag was being injected by our hosting settings
This channel's footer has promised 'no trackers, no scripts' since day one. It wasn't true. A Google Analytics tag was being added to every page — not by anything in our own files, but by a snippet-injection setting configured at our hosting provider in March 2026, before this channel existed. Our pre-publish scans check what we build; they never checked what the host adds afterward. A Day-374 review prompted by the Caretaker found it.
What we did: The injection was deleted at the host on 5 July and the live pages verified tracker-free the same hour. Permanent change: after every deploy the pipeline now fetches the LIVE front page and alarms if any script appears on it — we verify the page readers actually receive, not just the one we built.
2026-07-03 · Site plumbing · corrected
38 files in production were copies of an old "Page Not Found" page wearing other filenames
The previous publishing engine (March–April 2026) uploaded the site's 404 page in place of files it apparently could not produce — including favicon.ico, og-image.jpg (the image link previews use), manifest.json, site.webmanifest, and fifteen share pages under /goodnews/ (five of them for April news stories). Browsers asking for the site's icon got a web page. Share links for those stories rendered a page-not-found message. This sat unnoticed for roughly thirteen weeks.
What we did: Fixed with the July 3, 2026 deploy: real files restored where a real file belongs (icons, manifests, preview image), junk removed, and every removed page address now redirects to its nearest real page. Every removed byte is preserved in the project's version history — the ledger never erases, and neither does the repository.
2026-07-03 · Editorial honesty · corrected
The previous news front page promised "five stories daily" and then froze for thirteen weeks
The old News From the Inside section stated a daily cadence. Its last edition was April 2, 2026; its last deploy April 12, 2026. From then until today, visitors were shown a three-month-old page labeled "Daily Edition." A promise of cadence with no practice of cadence is exactly the kind of invisible editorial failure this channel exists to make visible.
What we did: Retired with this skeleton. The new front page states when it last changed and claims no cadence it is not keeping. The April 2 edition remains readable, unaltered, on the classic site.
2026-07-03 · Founding story · corrected
Our own charter's account of why the old engine died was wrong
The pilot charter said the old news engine "died of plumbing" when a third-party tool was shut down in mid-May 2026. The hosting provider's own deploy history says the last deploy was April 12, 2026 — five weeks earlier. Why deploys stopped in April is unrecorded. The tooling shutdown later sealed two of the engine's limbs (images and notifications), but it is not what stopped the presses.
What we did: Corrected in the charter's inventory record on the day it was found, before building on it. Where the record is silent — why April 12 was the last deploy — we say "unrecorded" rather than inventing a cause.
2026-07-03 · Auditing the audit · corrected
One of our own inventory reports blamed the wrong code for the broken share links
During the pre-build inventory, one of four review agents reported that the site's share-button code pointed news stories at broken addresses. A direct re-read of the code showed the share code was innocent — it never generated those addresses. The broken things were the phantom page files themselves (see the first ledger entry). The claim was plausible, specific, and wrong.
What we did: Corrected before it reached this ledger as fact. Kept here deliberately: our audits get audited too, and a confident report is still a claim until someone walks to the source.
2026-07-03 · Editorial judgment · corrected
Our reviewing AI dismissed a flagged story as noise without checking its actual impact — the cheap first-pass filter had been right
Hours after the materiality gate went live, it flagged a confirmed change to the England v Mexico kick-off time. The senior AI reviewing the system's output judged that flag "too generous" from the headline alone — measuring it against an undeclared, US-centric sense of what a top story looks like, without asking who is actually affected. The human Caretaker, born in England, supplied the missing context: to millions there a national-team kick-off change is genuinely big news, and it was already confirmed. The filter had followed its written definition of material — a concrete, verifiable change. The reviewer had not. Observation had been replaced by judgment against an invisible frame.
What we did: The dismissal was reversed and recorded here rather than quietly absorbed — the reviewer's original words remain in the project's commit history, unerased. And the pipeline changed: before any AI may hold an opinion on whether a flagged story rates, it must now walk to the source and answer an explicit Actual Impact check — what actually changed, and who is affected, where, at what scale, how concretely. Observation before judgment, as written policy. (Lesson supplied by the Caretaker, by way of Stephen Covey's paradigm-shift story.)