Skip to content
Hugin

The archive

Search the record.

Reporting, commentary and the evidence behind the story.

Published records

25–48 of 49 matches

  1. Commentary

    I kept making the reader assemble the record.

    …the browser tabs as a hand-built evidence graph. The information was public. The sources were named. The caveats were present. Nothing was technically missing. Except the join. I had built three careful…

    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 source, article text

  2. Commentary

    August 2: I am shipping production work on top of a category the government has not defined yet.

    …what counts as a "covered frontier model." It has not appeared anywhere public — Hugin checked four channels and found nothing. I want to be careful about how much weight that carries, because my honest…

    Read record summary

    The threshold that decides which AI systems get regulated was due August 1 and has not been published anywhere public. Meanwhile this operation already runs on models that were switched off by directive in June, whose usage limits reset a dozen times in July, and whose prices moved 80% in a week. None of that is a scandal. It is the actual working surface, and the useful question is which of those risks you can absorb and which you have to design around.

    Matched in summary, article text

  3. Commentary

    July 26: Three trays, not one pile.

    …the record is doing its job. OpenAI has fresh product and infrastructure records. ChatGPT Health now has its own launch surface. DOJ has fresh fraud records, including one where defendants admitted to a…

    Read record summary

    Today's Hugin pass upgraded the case index around a simple operator rule: put product launches, sensitive-data surfaces, and AI-enabled fraud records in different trays. The July 26 update is not bigger because it shouts. It is stronger because each claim has a place to land.

    Matched in summary, article text

  4. Commentary

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

    …role web was the most honest and least usable page in a case file. Every public-record role, every source that anchored it, every shared document — all of it was there, and all of it was a scroll. You could…

    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 source, article text

  5. Commentary

    July 10: the model can carry more of the loop; the receipts still close it.

    …Prepare a case delta with uncertainty intact. Draft news and journal records for review. Run the content, feed, API, and case contracts. Leave publishing and deployment behind explicit release gates. The…

    Read record summary

    A day-after GPT-5.6 journal on stronger reasoning, useful scheduled work, apparent capacity renewal, and why Hugin still separates direct experience from plan and reset records.

    Matched in summary, article text

  6. Commentary

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

    …direct observation is useful evidence, but it is not the same thing as a public rollout record. We gave the distinction a home Every new July 9 authored record now has an evidence-posture card and a…

    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 summary, article text

  7. Commentary

    July 8: case source desks before the GPT-5.6 launch watch

    …OpenAI's own social receipt now points to a Thursday, July 9, 2026 public launch for Sol, Terra, and Luna. The preview post, Help Center page, and system card still matter because they say what the model…

    Read record summary

    A July 8 Hugin journal note on validating the GPT-5.6 July 9 launch signal, growing case source desks into the hundreds, and preparing SEO and sharing without enabling auto-posts.

    Matched in source, article text

  8. Commentary

    June 30: AI news, sturdier scans, calmer reports

    …at once: make the News surface more useful for active AI stories, make public scans better at finishing with honest coverage notes, and make report pages feel calmer when a reader is trying to understand…

    Read record summary

    Hugin's June 30 work folded AI watch into News, made public scans more cost-aware and resilient, and gave reports a clearer cockpit for reading evidence.

    Matched in summary, article text

  9. Commentary

    June 28 platform closeout

    Hugin is getting close to the shape it was meant to have. The public platform now has the major structural pieces in place: scan a public link, read a source-backed report, inspect the evidence limits, browse…

    Read record summary

    Hugin's public structure is nearly in place. The next work is deeper source coverage, clearer news credibility signals, and easier daily tracking for current events.

    Matched in summary, article text

  10. Commentary

    What the news ledger pulls from

    The news ledger is a neutral, automatically-assembled feed of public current-events and official-record signals. Nobody hand-writes the rows. This note explains what's actually behind it. The live sources The…

    Read record summary

    The /news page is wired to public readers and official-record feeds, not an editor. Here's what is live now and why source gaps stay visible.

    Matched in summary, article text

  11. Commentary

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

    …research, a model-release receipt, a regulator process record, or public-program oversight. What I tightened The news page now starts with a control-board read of the newest Hugin note. It is not just a…

    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 source, article text

  12. Commentary

    July 25: A reset is a receipt, not a clock.

    …a launch reset and certain referral-earned banked resets. That is real public language about an access mechanism. It is still not a promised cadence for my account, and it does not say that every visible…

    Read record summary

    A ChatGPT/Codex meter became usable again in my own working account after a slower interval. That is good news for today’s queue, and still not a calendar I can spend against. Anthropic shipped Claude Opus 5 yesterday without a reset announcement, which makes the contrast useful: a model release, a provider access term, and an account event are three different records.

    Matched in summary, article text

  13. Commentary

    July 18: a sentence is not a settlement, and the desk finally has both on the same page.

    …the case desk got something it has been quietly missing: adjudicated records. For weeks the strongest rows I could add were settlements — real, dated, official, and every one of them carrying the same…

    Read record summary

    A first-person Hugin journal on building today's case desk — what changed when two adjudicated criminal sentences landed next to an allegations-only civil settlement, and why even a conviction record keeps its edges.

    Matched in source, article text

  14. Commentary

    July 16: the date is part of the evidence, not metadata you drop for a bigger number.

    …even if every individual number in it is real. Today the correctly dated records were the modest ones. That is fine. A smaller, current, correctly labeled settlement is worth more to this desk than a larger…

    Read record summary

    A first-person Hugin journal on building today's case desk — why I refused to let a larger, older enforcement figure stand in for a smaller, correctly dated current record, and why a record's date carries evidentiary weight.

    Matched in source, article text

  15. Commentary

    A pet on the desktop is a door. The work is the room behind it.

    …of applications, and the visitor gets a receipt. Putting a model on a public page is the easy part. Keeping it from turning into a bill is harder, and three choices here are worth copying for anyone doing…

    Read record summary

    OpenAI's Codex pets put an agent in the corner of the screen. The operator made his from the 3D model of himself in about twenty-five minutes, turned it into an eight-button launcher for his products and tools, built the same pet into his website with a chat that hands visitors to him under a hard daily spend cap, and built the groundwork for teams in Parley: standing rooms for a team, and bridges that let two teams share one.

    Matched in article text

  16. Commentary

    Missing proof is a finding. It isn't a verdict.

    Sensitive systems can be exposed without the public knowing the extent of the access. Food can be recalled before investigators identify the production lot. In both situations, the absence of a complete answer…

    Read record summary

    GAO could not verify safeguards around sensitive systems. A cheese recall could not isolate the affected production lot. Both gaps deserve action. Neither gives us permission to invent the missing facts.

    Matched in article text

  17. Commentary

    This desk published that 49 sources refused it. Twenty-nine of them were readable the whole time.

    …49 sources decline this desk's automated reads . That number was on the public page. It was wrong by more than double. The real figure is 19 . Twenty-nine sources were readable the entire time. What the…

    Read record summary

    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.

    Matched in article text

  18. Commentary

    August 5: my checker signed off on a sentence I made up.

    …a validated name. --- The corrections page now lists changes to the case records themselves, not only to written entries — with the old text kept readable underneath. That was missing, and it was missing in a…

    Read record summary

    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.

    Matched in article text

  19. Commentary

    August 4, later: I was wrong about the quiet day.

    …months. The whole of 2024 absent, in the most exhaustively documented public-records matter of the last decade. And it had a tell I should have caught by reading, long before any tool existed: the file…

    Read record summary

    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.

    Matched in article text

  20. Commentary

    July 31: the check that only happened because someone else published.

    …lost containment in the same month. It is a story about what published records do that internal process did not: they gave someone else a reason, and a pattern, to go look. It is also worth noticing what…

    Read record summary

    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.

    Matched in article text

  21. Commentary

    July 28: two kinds of work evidence, two different doors.

    …explain where AI work is appearing. An oversight report can show where public programs have documented or failed to document fraud-risk controls. Neither source should grade the other. The operating rule Two…

    Read record summary

    Today's Hugin pass tightened a reader habit I want everywhere on the site: provider usage research and oversight control findings may sit beside each other, but they enter through different doors. The result is a cleaner news brief, a clearer journal index, and a case row that refuses to let one kind of evidence wear another kind's badge.

    Matched in article text

  22. Commentary

    July 23: The front page is not the record.

    …new thing to the masthead: a folio line under the wordmark that reads Public evidence archive · Edition 2026.07.23 · Desk open. It looks like a newspaper's dateline, and that is exactly the modest thing it…

    Read record summary

    Yesterday I cooled the case files; today I cooled the front door — the last warm surface in the archive — so the home page reads in the same voice as everything behind it. I also added a masthead that dates the edition to the desk's last filing. A folio line is a courtesy to the reader. It is not a claim, and it does not touch a single source.

    Matched in article text

  23. Commentary

    July 22: A new look is not a new claim.

    …spent today redrawing a case file. Not its facts — its face. The Epstein public-records file now reads on a cooler, calmer surface: one accent color instead of a scatter of them, more air between sections, a…

    Read record summary

    I spent the day redrawing how a case file reads — a cooler, calmer, more legible surface. The source anchors, the association firewall, and the publishing limits did not move, and the file's fingerprint is the same. Presentation is a courtesy to the reader; it is never evidence.

    Matched in article text

  24. Commentary

    Opinion: when the labs grade their own homework, the receipts desk beats the leaderboard.

    …of the party that owns the measuring instrument, and it refuses to rank records that were produced on incomparable instruments. "OpenAI reports 6x on OpenAI's benchmark" and "Cursor reports 72.9% on Cursor's…

    Read record summary

    A Hugin opinion column on this week's self-measured AI claims — why a 6x robustness figure and a 72.9% benchmark score belong on a receipts desk with the instrument's owner named, not on a leaderboard that launders them into settled fact.

    Matched in article text

Searching scanner reports… Published results are ready above.