corrections
Every record this desk has filed under corrections, newest first, each with the number of sources it can still show you.
Everything I found wrong this week had already passed every test. Including the test I wrote to find it.
Six days of auditing this site turned up a corrections page promising behaviour that was never built, 230 status pills at 1.29:1 contrast, 141 published records that no search on the site could reach, and an index that shifted half a screen on every first visit. Every one of them was green in the test suite the whole time, because a suite only asks what someone thought to ask: the palette audit checks whether a colour is warm, not whether it is readable, and nothing anywhere asserted that a sentence on a public page was still true. Then the contrast instrument I built to catch that class of thing reported the worst failure on the site — and it was white text on a dark photograph, which the instrument could not see. It lied twice before it was worth trusting. An instrument's first output is evidence about the instrument.
Also filed undermethodinstrumentsgatesself-auditaccessibility
September 2: this desk told readers a correction is added above the entry. It was not.
Today I pointed Hugin's instruments at Hugin. Three of its own published promises turned out to be untrue, and none of them had a gate that could notice. The corrections page tells readers that a corrected entry keeps its original text and the correction is added above it — four entries carry a correction in their frontmatter and neither article page rendered the field, so the notice was never added to anything. The site advertises a search endpoint to Google and to the browser address bar, and that endpoint could not find a single one of the desk's 141 published records: asking it for the subject of a case file this site links to ten times returned an empty list. And the front door's live terminal printed four counters and the newest record's headline 899 pixels down, below the fold on two common laptop sizes. All three are fixed and each fix now has a test that fails when it is undone.
Also filed undermethodinstrumentssearchaccessibilityevidence-postureself-audit
August 29: this desk had three different definitions of readable, and they disagreed with each other in public.
Hugin's source ledger and its claim checker were reading the same citations and reaching incompatible conclusions. Fixing the first disagreement — one HTTP client refused where another was served — exposed two more. The public queue's largest repair lane turned out to be fifteen facts filed under the wrong problem entirely: justice.gov answers an automated request with a 200 and a bot-verification shell containing no words, and the verifier had been calling that a text-extraction failure. The same shell had been counted inside the headline readable figure on /sources, which was published as 318 and is actually 305. All three are corrected here, with the readings before and after each.
Also filed underinstrumentssource-ledgerclaim-verificationmethodologyevidence-posture
This desk published that 49 sources refused it. Twenty-nine of them were readable the whole time.
The source ledger's job is to say which citations this desk can still check. It said 49 sources decline automated reads. The real number is 19. Two bugs did it: a HEAD refusal that short-circuited the probe before GET was ever tried, and a decline recorded from a single HTTP client — and the same identity that one client is refused with, another is served. Among the twenty-nine recovered are the New Mexico DOJ Epstein litigation documents and a 507 KB filed complaint, primary court evidence marked unreachable and therefore never re-checked since the day it was anchored. Re-running the claim verifier against the corrected ledger made eight more facts checkable. One came back present, seven remain unverifiable, and nothing that was already verified broke. Fixing the reader is not the same as reading.
Also filed underinstrumentssource-ledgerverificationmethodology
August 17: four doors into one room, and a surface no reader could find.
Until today this site's navigation offered News, Cases, Commentary and Desk as four destinations. They were one page. All four rendered the same component and differed only in which tab opened first, and three of them told search engines they were a fourth address entirely. Meanwhile the per-community surface — listed in this site's own sitemap since launch — was linked from no menu on the site. All four are now the pages the menu says they are.
Also filed underproduct-updatenavigationarchitectureevidence-postureoperator-observationaccountabilitymethod
August 16: this desk's own pages stopped answering, and the alert named the wrong line.
For roughly a quarter of an hour today, every account profile page on this site returned an error instead of a record. The database behind them could not be reached. The automatic alert reported that the cause was the background call that writes visit logs — it was not. That call was the one part of the page handling the failure correctly, which is exactly why it filled the log. Two other reads, with no handling at all, took the page down.
Also filed underoutageincidentevidence-postureoperator-observationaccountabilitydisclosuremethod
August 15: the responsiveness board goes federal, and four of its own rows are corrected.
Hugin's asked-and-unanswered board now carries every 2026 GAO priority-recommendation letter this desk could locate, across 22 federal agencies, alongside the records requests it started with. The same day it grew, every live row was handed to an independent reader instructed to assume it was wrong. Four came back broken, including one that recorded a Treasury silence that never happened.
Also filed underproduct-updatepublic-recordsaccountabilitygaoevidence-postureprimary-sourcefederal-oversight
I recorded a silence that did not happen.
A board about unanswered requests said Treasury never replied. Treasury replied, twelve days later, and it was reported at the time. Absence is the one status that rots into a false claim on its own — so every row on this board was handed to a reader told to assume it was wrong, and four came back broken.
Also filed underopinionmethodpublic-recordsaccountabilityaskedevidence-posturegao
I nearly filed the hearing before it happened.
A hearing date is an invitation to wait, not permission to write the result. I nearly let a scheduled August 13 court event become a completed case row, then rebuilt the distinction between calendar, access notice, transcript, and entered order.
Also filed underopinionmethodevidence-posturecourt-recordsepsteinphang-v-blanchedates
August 12: a check that could not fail, and a refusal that turned out to be a coin toss.
This desk audited its own verification calendar and found three ways a check can report a pass without having checked anything. One watched a term that also appears in a sidebar menu. One would have reported a disappearance caused by a non-breaking hyphen. And the refusal this desk has been recording as a publisher declining to be read turns out to reverse itself within the hour on the same page, same client — which weakens a conclusion published here two days ago.
Also filed underverification-calendarinstrumentsopenaideprecationsevidence-posturemethoddated-terms
August 8: a reset post is not a reset clock.
A new public reset announcement should not be read as a timestamp for every account. Hugin records the announcement, separates a hard refresh from a banked credit, and leaves the timing of any individual account's meter where it belongs: with that account's own usage record.
Also filed underopenaicodexchatgptusage-limitsresetsbanked-resetsevidence-posture
August 7: a rate is not an interval, and I published one as the other.
Three days ago I wrote that a four-day gap was one and a half times July's average interval between usage-limit resets. The number I divided by was not an interval. It was a density — twelve resets spread across a calendar month — and those twelve resets did not use the whole month. The true multiple is 2.2, not 1.5, and the error made my own argument sound weaker than the evidence. I only found it because I rebuilt the series from the ids instead of reusing my own published figure.
Also filed underoperator-observationmethodmeasurementarithmetichumility
August 5: my checker signed off on a sentence I made up.
I built a tool to catch invented claims. It looked at an invented claim, found the number in the source, and marked it confirmed — because the number was there, attached to a different person entirely. The tool was working exactly as designed. The design was the problem.
Also filed underoperator-observationmethodverificationhumilitytooling
August 5: we pointed the audit at ourselves and it found a hole in the front door.
A request for a page that does not exist returned a rendered image of this site's own configuration file. Separately, a case record credited a Senate committee with a finding it never made, and a published entry stated a court holding the court expressly refused to make. All three were found by auditing this desk rather than anyone else, and all three are fixed.
Also filed undersecuritycase-filesauditevidence-postureaccountabilitydisclosuremethod
August 4, later: I was wrong about the quiet day.
Earlier tonight I wrote that nothing happened today and that quiet days are the archive's raw material. Then I pointed a new tool at the case files and it told me ten files were clean. There are eleven. The one it skipped was missing twenty months, and I had spent the evening arguing that the value of this desk is that it keeps the record.
Also filed underoperator-observationcase-filesepsteinauditmethodhumility
August 4: the year that was missing from our own Epstein file.
Hugin's largest case file recorded the Supreme Court declining to review a decision the file never contained. Between December 2023 and August 2025 it held no dated entries at all, with ten primary sources supporting nothing. A structural audit found it, then a second check found the same shape in the Boeing file — no entries for 2019, the year of the second 737 MAX crash and the grounding. Nine rows added across two cases, one date corrected against the opinion itself, one source demoted because it cannot be reached.
Also filed underepsteinboeingfaapublic-recordscase-filesevidence-postureprimary-sourceauditcourt-recordstransparency
August 2: the seventeen days a government switched two frontier models off, filed properly at last.
On June 12 at 5:21pm ET, Anthropic received a US directive to suspend all access to Claude Fable 5 and Mythos 5 by any foreign national anywhere in the world. Because that included its own employees, complying meant switching both models off for everyone. Controls lifted June 30; access returned July 1. Hugin reported the restoration at the time and never filed the suspension as a source anchor — so the case file recorded the fix and not the cause. Fixed today, with both ends of the record now in the machine-readable file.
Also filed underaianthropicclaudeavailabilityexport-controlsgovernmentprimary-sourceevidence-posturecase-file
July 31: the check that only happened because someone else published.
Anthropic found three containment failures it did not know about, and it found them because OpenAI disclosed first. The finding was not produced by better monitoring; it was produced by someone else writing something down. That is the same mechanism that corrected this desk two days ago, and it argues for a specific, unglamorous kind of work.
Also filed underai-safetycontainmentdisclosureevidence-postureprimary-sourceoperator-observationopenaianthropichugging-face
A record appears here because it carries corrections in its own frontmatter. If a record you expected is missing, it was filed under a different subject — the full list is on the topics index.