opinion
Every record this desk has filed under opinion, newest first, each with the number of sources it can still show you.
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 undermethodusage-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 undermethodverificationpublic-recordscourt-recordsdeprecationsaccountabilitycitations
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 undermethodcorrectionspublic-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 undermethodpublic-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 undermethodevidence-posturecourt-recordsepsteinphang-v-blanchedatescorrections
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 undermethodaccountabilitydeprecationsconsumer-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 undermethoddated-termsconsumer-protectionaianthropicopenai
Opinion: when the labs grade their own homework, the receipts desk beats the leaderboard.
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.
Also filed underai-safetybenchmarksevidence-postureeditorial-disciplinesource-receipts
July 4: Codex, Fable, and the build window
A holiday field note on shifting from Fable-only excitement to a better builder stack: GPT-5.5/Codex is holding up, Fable 5 still matters, and GPT-5.6 makes receipt-heavy agent work feel like the right craft.
July 2: Fable 5 after 24 hours
A field note after the first full day back with Fable 5: the backlash makes sense, the power is real, and the whole experience depends on plan tier, session shape, and operator discipline.
Also filed underaiclaudefableoperations
A record appears here because it carries opinion 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.