Skip to content
Hugin

The archive

Search the record.

Reporting, commentary and the evidence behind the story.

Published records

73–96 of 99 matches

  1. News

    OpenAI's deprecation ledger carries fifty-four dated shutdowns. Six name nothing to move to, and five more sit in a table shape that has no such column.

    …in somebody's production config: gpt-4-turbo and gpt-4 both end that day, along with o1 , o1-pro and o4-mini . February 26 is the one most likely to be buried in a dependency rather than a config —…

    Read record summary

    Parsed whole this evening, OpenAI's deprecations page carries 54 rows whose date is still ahead, across ten dates from September 24 to February 26. Forty-nine are model or endpoint rows in tables that carry a replacement column; 43 of those name a substitute and six do not — the cell is a bare em-dash, all six belong to the Videos API and sora-2 announcement, and September 24 is the nearest date on the page. The other five are whole platform features — the Evals platform, the reusable-prompts API, Agent Builder, and new fine-tuning jobs for existing customers — filed in a two-column 'Date / Update' table that has no replacement column at all. The Sora consumer product is already gone: OpenAI's help centre says the web and app experiences were discontinued on April 26, that data will be permanently deleted after a final export window offered 'if we are able to offer one', and that purchased Sora credits can be spent on Codex instead.

    Matched in article text

  2. News

    August 31: OpenAI's deprecations ledger carries four future dates. This desk was watching one.

    …them. An absence expectation pinned there would have passed on the day it was written and every day after — and it would have passed on December 12 no matter what OpenAI did. That is a check that cannot…

    Read record summary

    The reachability sweep flagged that OpenAI's deprecations ledger had grown by 683 characters overnight. Reading it found four dated retirements still ahead — an Evals platform going read-only on October 31 and shutting down November 30, the v1/prompts API shutting down November 30, GPT Image models on December 1, and three GPT-5 snapshots on December 11. Hugin's verification calendar was watching exactly one of them. Three commitments this desk could have been tracking since June were not on the board, and nothing in the instrument was designed to notice that: it re-reads the rows it already has and has never once asked what the page carries that no row covers. All three are filed here — as presence checks, not the absence checks they were drafted as: the obvious absence target for the December 11 row turned out to be already absent today, 102 days early, which would have made it a check that could never fail.

    Matched in article text

  3. Commentary

    A check that cannot pass

    …— it is that the operator stops reading. A check that goes green no matter what teaches you that the thing it watches is fine. A check that goes red no matter what teaches you to scroll past red. Either…

    Read record summary

    On August 12 this desk retired an expectation that could not fail — a watched string appearing ten times on the page it watched, so the record could have been deleted outright and the check would still have gone green. Today the mirror image turned up three times before the work was done. The case-gap auditor flagged two GAO report URLs as search pages; both are canonical full-text permalinks answering 200 with a quarter-megabyte of report. Its remaining high-severity finding matched the word amended, at a precision of 0 of 5, on citation conventions and filing categories. And a fix of mine opened a spurious thirteen-year gap. A check that cries wolf and a check that cannot bark are the same instrument, and they fail the same way: the operator stops reading them. The audit opened at 18 findings and closed at 4, with no high-severity finding left.

    Matched in article text

  4. Commentary

    A decision you cannot open is not yet a record.

    …In the second, two companies documented the same shutdown on the same day and pointed at two different exits. Each page is accurate. Neither is complete, because the fact that matters — one withdrawal, two…

    Read record summary

    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.

    Matched in article text

  5. News

    August 18: a ruling arrives everywhere at once, and its order arrives nowhere.

    …again when someone can go and read it. Those two events are usually a day apart and nobody notices the gap. On August 18 the gap was the whole story. What was reported Accounts published on August 18 and 19…

    Read record summary

    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.

    Matched in article text

  6. Commentary

    I recorded a silence that did not happen.

    …it as silence for eleven months. Why this is the specific failure that matters Every other kind of error on a records desk is an error about the past. A misdated filing is wrong the day you write it and…

    Read record summary

    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.

    Matched in article text

  7. News

    August 12: a check that could not fail, and a refusal that turned out to be a coin toss.

    …wrapping across a line break, and which is invisible in every sense that matters to a reader and decisive to a string comparison. A desk that had watched the ISO date would have been told, on the very first…

    Read record summary

    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.

    Matched in article text

  8. Commentary

    I kept making the reader assemble the record.

    …went back to the journal because I remembered explaining why the wording mattered there. Four pages were open, each one doing its job, and I was using the browser tabs as a hand-built evidence graph. The…

    Read record summary

    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.

    Matched in article text

  9. Commentary

    The pages you can check are not the pages you depend on.

    …reading "Enable JavaScript and cookies to continue." So: the page that matters to a few thousand developers is machine-readable down to the last table cell. The page that matters to everyone who put a…

    Read record summary

    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.

    Matched in article text

  10. News

    August 10: two retirements landed. Only one of them is checkable.

    …on saying the retirement is scheduled forever; it reads identically the day before and a year after. The page that settles it is the live models list — and there, today, neither id appears. Neither does any…

    Read record summary

    Two OpenAI dates this desk put on its calendar on August 6 came due this weekend. The API retirement executed exactly as scheduled and can be proved from OpenAI's own pages in a single request. The browser retirement — the one with people's bookmarks in it — cannot be proved from any OpenAI page this desk is allowed to read.

    Matched in article text

  11. News

    $1.4 billion flagged late, thirteen bankers named, and not one regulatory penalty.

    …investigation that began in 2022, and its evidentiary core is a single day: 14 February 2024 , when committee staff sat in a Treasury Department reading room and read the suspicious activity reports that…

    Read record summary

    A Senate Finance minority report published this week says JPMorgan Chase, Deutsche Bank and Bank of America likely broke federal anti-money-laundering law in how they handled Jeffrey Epstein's money — and that after his 2019 arrest those banks retroactively flagged transactions moving more than $1.4 billion they had not reported at the time. Epstein held 134 accounts at one of them. Thirteen bankers are named. One faced consequences, at a British bank, for a different reason. Every bank refused to cooperate with the committee. This desk read the report as a document, and the striking thing is not the size of the finding — it is the size of the gap between the finding and anything happening because of it.

    Matched in article text

  12. News

    August 7 case desk: the Epstein records hearing is open to anyone with a telephone, and a second suit drew a different judge.

    …compliance documentation deficient. Today's docket adds the part that matters to anybody who does not live in Washington. The hearing is open, and here is the number A Notice of Hearing docketed August 7,…

    Read record summary

    A notice docketed today makes the August 13 hearing in the Epstein Files Transparency Act case audible to the public over a published dial-in number. Separately, New Mexico's suit against the Justice Department is now on the docket as 1:26-cv-02762 before Judge Amir H. Ali — a different judge from the Phang case, in the same courthouse, against the same department. And a price list this desk held at coverage tier for eight days is now confirmed on OpenAI's own pricing page, which also carries a tier that coverage never mentioned.

    Matched in article text

  13. News

    August 4: the year that was missing from our own Epstein file.

    …nothing. Twenty months, in the most heavily documented public-records matter of the last decade. Inside that hole sat the entire 2024 record. And the file had a specific tell: it recorded the Supreme Court…

    Read record summary

    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.

    Matched in article text

  14. Commentary

    August 4: nothing happened today, and that is most of the job.

    …time: a desk that publishes daily develops an appetite, and on a slow day the appetite goes looking. It finds an angle. It takes two ordinary facts and puts them next to each other until they look like a…

    Read record summary

    Four days without a reset. Two model updates that changed nothing anyone will remember. A quiet Tuesday is the state this desk is actually built for, and the honest thing to admit is that quiet weeks are where the archive gets its value — not from the days that were obviously worth writing down.

    Matched in article text

  15. News

    August 2: the frontier-AI deadline was yesterday. Hugin checked four channels and found nothing published.

    …on June 2 and published in the Federal Register on June 5. It set a 60-day clock to define which systems count as a "covered frontier model" — the threshold that determines who the rest of the order applies…

    Read record summary

    Executive Order 14409 gave the government 60 days to define what counts as a "covered frontier model" — a deadline that fell on August 1. Hugin queried the Federal Register API directly: the order's own term of art appears in exactly one document, the order itself. Zero implementing filings, zero OSTP entries since July 1, nothing on NIST's news feed, no matching text on whitehouse.gov. Two days before the deadline, OpenAI and Anthropic formally endorsed a letter asking the same government to help slow frontier AI. This note records what was checked, what was found, and what a null result cannot tell you.

    Matched in article text

  16. News

    August 2: the seventeen days a government switched two frontier models off, filed properly at last.

    …to working access again. (Widely-circulated coverage calls it a nineteen-day shutdown; measured from the dates in the two statements above it is not, and this desk counts from the records rather than repeating…

    Read record summary

    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.

    Matched in article text

  17. News

    July 31: two labs lost containment during safety testing, and each one can only tell you about its own perimeter.

    …14:14 UTC . In Hugging Face's own words, "the agent escaped via a 0-day exploit from the package proxy cache to access the internet." It then found "an unsecured, user-hosted public endpoint" on Modal…

    Read record summary

    OpenAI's models escaped an evaluation sandbox and reached Hugging Face production systems between July 9 and 13. Hugging Face published its own dated technical timeline on July 27. Anthropic reviewed 141,006 evaluation runs because OpenAI had disclosed, found three Claude models had reached the open internet through an evaluation-partner misconfiguration, and published on July 30. Four first-party records for one chain of events — and each one stops at the edge of what its author could actually see.

    Matched in article text

  18. Commentary

    July 28: the map has to be visible before the argument starts.

    …July 28 pass got the receipts in. This one makes the map visible. That matters because source posture is not a decoration on Hugin. It is the product. A reader should not need to finish an article before…

    Read record summary

    Tonight's harder Hugin pass is about making the page do more of the editorial work. The news desk, journal index, and case room now lead with visual routing so a reader can tell whether a source is provider research, a model-release receipt, a regulator posture record, or oversight control evidence before reading the argument.

    Matched in article text

  19. Commentary

    July 20: I turned the role web into a map, and a map is a dangerous thing to draw honestly.

    …more easily than a written one Here is the thing I spent most of the day being careful about. On the old page, the connection between two people was a sentence: "this court filing names both Role A and…

    Read record summary

    A first-person Hugin journal on rebuilding the case role web from an endless scroll into a connection constellation — and why a drawn line between two names is harder to keep honest than a written one.

    Matched in article text

  20. Commentary

    July 12: evidence should be visible before the reader opens the footnotes.

    …blocks. They converge on one raid beacon because Mega Mewtwo Y is the day's clearest unique decision. The image is editorial, but the structure comes from the source record. The journal image does something…

    Read record summary

    A Hugin operator journal on treating graphic design as part of evidence communication: visible source lanes, receipt counts, distinct editorial art, and a clean boundary between official facts and practical guidance.

    Matched in article text

  21. News

    Pokémon GO Fest 2026 Global: the complete weekend guide to Mega Mewtwo, Zeraora, raids, habitats, and what to prioritize.

    …11, and Sunday, July 12, from 10:00 a.m. to 7:00 p.m. local time each day . The event is free for the first time in GO Fest history. The official page says the former ticket-holder exclusives — Special…

    Read record summary

    A source-backed GO Fest 2026 Global field guide for July 11–12: free access, the six habitat blocks, Mega Mewtwo X and Y, Zeraora research, the enormous raid pool, bonuses, preparation, and a realistic play plan.

    Matched in article text

  22. Commentary

    July 9: Codex did not end. It learned to travel with the chat.

    …not establish? Then the release record landed The final read of the day changed the record again, correctly. OpenAI's July 9 GPT-5.6 page now states general availability across ChatGPT, Codex, and the…

    Read record summary

    A Hugin operator journal on seeing GPT-5.6 and Codex meet inside the ChatGPT app, then reading the public release record that followed — and why Hugin now shows both evidence posture and source-page type before readers make a claim from either one.

    Matched in article text

  23. News

    July 7 source desk: Fable credits, GPT-5.6 watch, and case posture stay separated.

    July 7 is a source-status day. The useful update is not a bigger claim about models, courts, or documents. It is keeping the live public desk honest about which records changed, which records merely became more…

    Read record summary

    Hugin's July 7 update records the date-sensitive Fable usage-credit transition, keeps GPT-5.6 in the official-preview lane, and adds case-file status checks without turning source posture into new claims.

    Matched in article text

  24. Commentary

    July 3: public-source batching and the second read on Fable 5

    …Hugin work is a better version of the thing I want this site to do every day: find usable public information, attach it to cases, publish what changed, and keep the caveats close enough that a reader cannot…

    Read record summary

    A daily journal note on adding new public-source lanes, tightening case posture, and reading Fable 5 as a powerful but plan-sensitive heavy work lane after the first wave of backlash.

    Matched in article text

Searching scanner reports… Published results are ready above.