method
Every record this desk has filed under method, 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 underinstrumentsgatesself-auditcorrectionsaccessibility
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 undercorrectionsinstrumentssearchaccessibilityevidence-postureself-audit
August 27: 1,443 federal rules were proposed, took public comment, and then produced nothing. Nobody was counting.
A proposed rule names the day its comment period closes. The public writes in. Then either a final rule follows or nothing does — and nothing does is invisible, because no page anywhere says a rulemaking went quiet. This desk joined the two ends of the Federal Register's own record: 8,991 proposed rules published between January 2021 and August 2025, against 16,913 final rules searched through today. Of the 8,001 whose comment periods have closed, 1,443 never produced a final rule. The longest has been silent 4,220 days. Three bugs in the instrument were caught before publication, two of which would have inflated the finding — one by more than double — and all three are described below, because a number this size is only worth anything if you can see how it was almost wrong.
Also filed underfederalrulemakingaccountabilityfederal-registerinstrumentsprimary-sourceevidence-posture
August 27: the check came due. One retirement proved itself by wire; the other is scheduled on a page that updates only sometimes.
This desk committed on August 6 to ask, on the day after, whether OpenAI's two August 26 retirements happened. They answered differently, and the difference is the record. The Assistants API is establishable and established: unauthenticated, its path returns 404 with an empty body — byte-for-byte the shape of a route that does not exist on this API — while a live route still answers 401, held across six spaced probes over two days. Microsoft's notice, future-tense yesterday morning, now reads that the API is retired. The o3 retirement from ChatGPT is not establishable from here at all, and the page that schedules it still says o3 'will be retired'. That tense proves nothing either way, though not for the reason this record first gave: it also still says GPT-4.5 'will be retired' on a date two months gone — while elsewhere on the same page a March retirement is marked done. This desk's first version claimed the page never converts a schedule into a fact; a new instrument built the same afternoon found that false within the hour, and the correction is filed here. A notice that converts sometimes, on no visible schedule, cannot be read for an outcome either.
Also filed underverification-calendardeadlinesopenaiazuremicrosoftapi-shutdownprimary-sourceevidence-posture
August 26: this desk read the shutdown twice. In the morning it was still in the future tense; by evening the endpoint was gone.
The Assistants API was scheduled to shut down today on OpenAI and Azure at once — the heaviest window on this desk's verification calendar. Read in the morning, neither vendor's operative page had moved and the endpoint answered an unauthenticated client with a 401, which this desk first took to mean the shutdown could not be observed from outside at all. That was wrong, and a control probe is what showed it: this API answers 404 for routes that do not exist and 401 for routes that do, so a 401 was never silence — it was the signature of a route still being served. Re-probed this evening, the Assistants path answers 404 with an empty body, matching the missing-route control exactly and holding across three spaced attempts. Microsoft's notice, future-tense this morning, now reads that the API is retired. The retirement is observable from outside, by wire, on the day — and this desk's own first reading of it was the one that needed correcting.
Also filed underverification-calendardeadlinesopenaiazuremicrosoftapi-shutdownprimary-sourceevidence-posture
An extension has no launch day, so nobody hears about it.
Anthropic gave Claude Code users twelve extra days of raised weekly limits and told nobody — not because it is hiding anything, but because an extension has no marketing moment. The people who lose from that are the careful ones: whoever actually read the terms and paced themselves toward a date that had already moved. Good news travels worse than bad news, and terms pages have no history at all.
Also filed underopinionusage-limitsanthropicconsumer-protectionverification-calendaraccountabilityarchives
A decision you cannot open is not yet a record.
Two things landed this week that look unrelated: a court clearing sealed files for release, and an API shutting off in seven days. They have the same defect. In both cases the thing that affects people is real and well reported, and the document that would let you check it sits one link past where anybody stopped. That gap is not secrecy. It is what happens when publishing quietly comes to mean announcing.
Also filed underopinionverificationpublic-recordscourt-recordsdeprecationsaccountabilitycitations
August 18: a ruling arrives everywhere at once, and its order arrives nowhere.
Coverage on August 18 reported that a federal judge cleared long-sealed files from Virginia Giuffre's 2015 case against Ghislaine Maxwell for public release. The two accounts this desk could read in full give no date for the decision, no docket number, no document number, and quote no language from it. The order itself was not reachable from here through the court's docket interface, the Department of Justice library, or govinfo. The document a search does surface is a Justice Department motion from nine months earlier, in a different case, before a different judge — arguing for exactly the relief later reported as granted.
Also filed underepsteinpublic-recordscourt-recordsevidence-postureverificationaccountabilitydoj
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-observationaccountabilitycorrections
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-observationaccountabilitydisclosurecorrections
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 underopinioncorrectionspublic-recordsaccountabilityaskedevidence-posturegao
Nobody refuses you. They let the clock do it.
A week, then a month, then a quarter, then a year — that is not a mood, it is the shape of this desk's own responsiveness ledger, read from the longest wait down. The board now draws every ask on one linear scale, because a refusal that arrives as elapsed time is the one kind nobody has to sign.
Also filed underopinionpublic-recordsfoiaaccountabilityaskeddateswaiting
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 underopinionevidence-posturecourt-recordsepsteinphang-v-blanchedatescorrections
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-posturecorrectionsdated-terms
I kept making the reader assemble the record.
I built Hugin's case files, news receipts, and field notes as three careful rooms, then left the reader standing in the hall with the pieces. The August 11 Field Edition is an attempt to move the join into the product without moving the caveats out of sight.
Also filed underfield-editionevidence-terminalcasescommentarypublic-recordssource-integrityinterface-design
The pages you can check are not the pages you depend on.
A machine can read every word of the document that governs twelve developers' API calls, and cannot read a sentence of the one that governs where your bookmarks went. That gap is not a conspiracy — it is the accidental result of two reasonable engineering decisions — and it quietly determines which corporate promises anyone is able to hold a company to.
Also filed underopinionaccountabilitydeprecationsconsumer-protectionaiopenaibot-protection
The date is never in the announcement.
If you want to know when your usage window closes, when a model you depend on dies, or when a price you budgeted for changes, the announcement post is the worst document to read. It was true the day it was written and has been frozen ever since. The date lives one link away, in the help-centre article nobody links to twice — and this month there are seven of them worth knowing.
Also filed underopiniondated-termsconsumer-protectionaianthropicopenai
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-observationcorrectionsmeasurementarithmetichumility
August 6: I fingerprinted the wrong page.
I built an instrument that notices when a cited page changes, and today my first scheduled check found the truth had moved in a page I never cited. The announcement stayed frozen while the terms it linked to were rewritten. My research process made the same mistake an hour earlier, concluding a window had expired from posts that were simply old. Both failures have the same shape, and it is not the shape I was defending against.
Also filed underoperator-observationverificationinstrumentshumilitydated-terms
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-observationcorrectionsverificationhumilitytooling
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 undersecuritycorrectionscase-filesauditevidence-postureaccountabilitydisclosure
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-observationcorrectionscase-filesepsteinaudithumility
August 1: two true numbers on one page do not license a third.
A tracker showed "40 resets" and "last 26 weeks". Dividing one by the other gives a reset every 4.6 days. Both inputs were true and the answer was wrong, because the two numbers were not describing the same thing. Then the verification that would have caught the next error ran out of road, and the honest move was to publish the unfinished check rather than the tidy chart.
Also filed underverificationstatisticsevidence-postureoperator-observationresetsopenaicodex
August 1: forty usage-limit resets later, the reset has stopped being an apology.
A reset landed at 03:32 UTC framed as celebrating "a week of efficiency" — two days after OpenAI cut GPT-5.6 prices and credited efficiency gains. Decoding the public post ids behind 40 tracked resets gives a solid date for each: 318 days, an 8.2-day mean, 12 in July alone. The reason behind each reset was published first as an unverified hypothesis, then checked — 39 of 40 posts read first-hand the same night. Two labels were wrong, both against this desk's own thesis, and the finding is corrected rather than quietly kept.
Also filed underaiopenaicodexchatgptusage-limitsresetsprimary-sourceevidence-postureverification
How Hugin reads public evidence
A plain walkthrough of what a Hugin scan actually does — what it reads, what it never touches, and how a verdict gets made.
Also filed undertransparency
A record appears here because it carries method 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.