anthropic
Every record this desk has filed under anthropic, newest first, each with the number of sources it can still show you.
September 1: three windows came due. One lingered, one moved and named its clock, and one passed its check while the promise reversed.
Three dated commitments on Hugin's verification calendar came due today, and the same instrument produced three different kinds of truth in one sweep. OpenAI's Codex doc still hands a reader the copy command for GPT-5.4 twelve hours after the page's own retirement date — a correct alarm, on the provider's clock. Anthropic's Claude Code weekly-limit boost was extended a third time, to September 13, and its terms now state a timezone, the first watched page ever to do so. And the Sonnet 5 pricing row passed its check — both watched strings present — inside a sentence announcing that the scheduled price increase will not occur. A presence check cannot see a reversal that keeps its own vocabulary. Anthropic also shipped Claude Fable 5.1 and Mythos 5.1 today, into the middle of it.
Also filed underinstrumentsverification-calendardeadlinesopenaimethodologyai-release-receiptsfable
August 24: six dated windows come due in the next eight days, and the first one is a shutdown.
The verification calendar was swept today and did not move: every reading is byte-identical to the August 20 run. What that steady artifact shows is a queue. Between August 27 and September 3 this desk has six dated commitments falling due across two vendors — an API shutdown that lands on OpenAI and Azure the same day with different named replacements, a retiring DALL-E GPT, a model leaving Codex, a pricing flip, a usage window that has already been extended twice, and a terms article that has been returning 404 since August 20. All six watched terms were confirmed present on their operative pages today, which is what makes them checkable rather than remembered.
Also filed underverification-calendardeadlinesopenaiazureapi-shutdownprimary-sourceevidence-posture
August 24: this desk published a dead link on Thursday and reported zero dead links until Monday.
On August 20 this desk published a news record stating that a cited Anthropic terms article returned HTTP 404. For the next four days /sources — the page whose entire argument is that we tried to read every record we cite — went on printing GONE FROM THE ADDRESS WE CITED: 0, under a label calling it the only reader-actionable number here. Nothing was hidden and nothing was wrong on either page in isolation. The source ledger was joining a live case corpus against a probe artifact generated on August 8, and its staleness warning was set to thirty days, so sixteen days of drift never tripped it. Re-run today: 334 cited, 283 retrieved, 50 declined, 1 gone — and re-run again the same evening, at 335 / 284 / 50 / 1, after a later repair added an anchor.
Also filed underverificationsource-ledgerinstrumentsself-auditcoworkprimary-sourceevidence-posture
August 20: two dated windows came due. One quietly grew, the other's terms page is gone.
This desk committed in advance to check two Anthropic usage promotions today, the day after both said they ended. Claude Code's weekly-limit boost did not end — its terms article now reads through August 31, extended without an announcement. Cowork's doubled 5-hour limits cannot be checked at all: the operative terms article returns HTTP 404 on five attempts, no replacement exists on the support site, and the only surviving public statement is a July 7 post still advertising a date that expired on August 5. Same vendor, same day, same kind of promotion, opposite outcomes.
Also filed underclaude-codecoworkusage-limitsverification-calendarprimary-sourcedeadlinesevidence-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 underopinionmethodusage-limitsconsumer-protectionverification-calendaraccountabilityarchives
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 underopinionmethoddated-termsconsumer-protectionaiopenai
August 6: the first window came due. It moved — one link away from where we were looking.
Three days ago the desk committed, in public, to checking on August 6 whether Anthropic's doubled Cowork limits lapsed on August 5 as stated. The check ran. The launch post still says August 5, unchanged. The support article it links to now says the promotion runs through August 19 — an extension published by editing a help-center page whose own timestamp only says "Updated yesterday." The same day, a different dated Anthropic term held exactly: Opus 4.1 was retired on August 5, one year to the day after its release. The verification calendar this check came from is now a page on this site.
Also filed underaiopenaiclaudecoworkopusgpt-5-6dated-termsusage-limitsmodel-retirementsverification-calendarsource-receiptsevidence-posture
August 4: nothing happened today, and that is most of the job.
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.
Also filed underoperator-observationaicadencearchivepatienceopenai
August 3: three Anthropic windows are running, and every one has an end date.
Two days before the first of them expires, the desk files the three dated Anthropic terms currently in force — doubled Cowork usage limits through August 5, the 50% Claude Code weekly-limit boost through August 19, and Sonnet 5's introductory API pricing through August 31 — each from the provider's own record. A dated window is the opposite of a surprise reset. You can put it on a calendar before it happens, and check it after. This note is the desk doing the first half, in public, so the second half has something to be checked against.
Also filed underaiclaudeclaude-codecoworksonnet-5usage-limitspricingdated-termssource-receiptsevidence-postureverification-calendar
August 2: I am shipping production work on top of a category the government has not defined yet.
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.
Also filed underoperator-observationairegulationeo-14409availabilitydependency-riskopenaiinfrastructure
August 2: the frontier-AI deadline was yesterday. Hugin checked four channels and found nothing published.
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.
Also filed underaigovernmentexecutive-ordereo-14409frontier-modelsregulationopenaiprimary-sourceevidence-postureabsence-of-record
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 underaiclaudeavailabilityexport-controlsgovernmentprimary-sourceevidence-posturecase-filecorrections
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-observationcorrectionsopenaihugging-face
July 31: two labs lost containment during safety testing, and each one can only tell you about its own perimeter.
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.
Also filed underaiopenaihugging-faceai-safetycontainmentevaluationsprimary-sourceevidence-posturesupply-chain
July 28 control room: AI work claims, model releases, and fraud controls need a visible map.
Hugin's late July 28 pass turns the daily desk into a source-lane map. OpenAI's Work at the Frontier research, Anthropic's Opus 5 release posture, FTC's AI-accuracy comment window, SEC's retail-fraud working group, and GAO's fraud-risk findings are useful together only when the reader can see which lane each record belongs to.
Also filed underaiopenaiftcsecgaofraud-risksource-mapevidence-posturecontrol-room
July 28 desk: work-frontier reports and fraud-risk controls need different receipts.
Hugin's July 28 pass separates AI-at-work research from oversight-grade fraud controls. OpenAI's Work at the Frontier post is useful evidence about reported ChatGPT task crossover, while GAO's state-administered-program report is an oversight record about fraud-risk management. They can inform the same desk, but they cannot grade each other.
Also filed underaiopenaigaofraud-riskwork-frontiersource-receiptsevidence-posture
July 25 AI desk: Opus 5 shipped. A reset is a separate receipt.
Anthropic released Claude Opus 5 on July 24 with stated all-platform availability, the same base API price as Opus 4.8, Max-default and Pro-top-tier positioning, safety fallbacks, and two API betas. That is a real release record. It is not a reset announcement. OpenAI’s own ChatGPT notes separately document Codex reset banking for eligible Plus and Pro users; Hugin logs a visible reset on one account as a field observation, not a shared calendar.
Also filed underaiclaudeopus-5openaichatgptcodexusage-limitsreset-bankingsource-receiptsevidence-posture
July 21 AI receipts: the useful-work scorecard starts with a control plane.
OpenAI's July 17 scorecard says the price of a successful AI task includes retries, review, and rework — not just tokens. Its Codex deployment record describes the separate question of access, approvals, and telemetry. Anthropic's July 9 commitment to report its actions is a third kind of record: a promise that needs later receipts.
Also filed underopenaicodexai-agentsagent-controlsevidence-posturesource-receipts
July 18 AI receipts: GPT-Red and a Cursor field report are dated records of self-measured claims.
Hugin logs two AI records on one shared caveat — OpenAI's July 15 GPT-Red safety publication with its self-reported 6x robustness figure, and Anthropic's July 17 Cursor field report with its proprietary 72.9% CursorBench score. Both are primary records of what each lab says about its own model.
Also filed underopenaigpt-5-6claudefable-5ai-safetyred-teamingai-release-receiptsevidence-posturesource-receipts
July 16 AI receipts: Claude for Teachers is a dated launch record; the 8-million Codex figure stays coverage.
Hugin logs two AI records on separate evidence lanes — the July 14 Claude for Teachers launch as a primary-source Anthropic product record, and the reported Codex/ChatGPT Work 8-million-user milestone as executive-stated coverage, not an audited metric.
Also filed underopenaiclaudecodexgpt-5-6ai-release-receiptsevidence-posturesource-receipts
July 15: the agent subscription scoreboard moved from preference to operating decision.
A first-person Hugin journal on why Claude plus Codex remains the strongest combination, while GPT-5.6 Sol Ultra's production capacity and repeated July resets reduce the need for multiple Claude subscriptions to reach the same result.
Also filed underopenaigpt-5-6codexclaudefablesubscriptionsoperator-observation
July 15 field record: account capacity is now part of agent quality, but one operator is not a plan matrix.
A sustained GPT-5.6 Sol Ultra working record separates one operator's durable ChatGPT capacity and repeated July reset allotments from provider terms while preserving Claude plus Codex as the preferred working combination.
Also filed underopenaigpt-5-6codexclaudefableusage-limitsoperator-observation
July 8 source desk: Fable terms hold, Claude Code stays separate, and court records get a cleaner door.
Hugin's July 8 refresh keeps the Fable July 12 promotion, the Claude Code July 13 weekly-limit window, and reset uncertainty in separate lanes while adding a court-record source view for public case review.
Also filed underaiclaude-codefablecourt-recordssource-receipts
Late July 7 update: Fable runs through July 12, Claude Code gets a separate 50% limit window.
Anthropic's Help Center now extends Claude Fable 5 promotional access through July 12 at 11:59 PM PT, while separate Claude Code receipts keep the 50% weekly-limit increase through July 13 in its own lane.
Also filed underaiclaude-codefablesource-receipts
July 4 release watch: Codex, GPT-5.5, Fable 5, and the next GPT-5.6 lane.
Hugin adds an AI release receipts case file and reframes the current builder stack: GPT-5.5/Codex is a strong agentic work lane, Fable 5 remains the large-context heavy lane, and GPT-5.6 Sol stays in release-watch until broader receipts land.
Also filed underaiopenaicodexgpt-5-5gpt-5-6fablecasesrelease-watch
GPT-5.6 Sol preview makes agent work a receipt problem.
OpenAI's Sol preview, Anthropic's Sonnet 5 launch, and Fable 5's restored access all point at the same public question: how do people verify long-running agent work?
Also filed underaiopenaicodexagentspublic-records
Claude Fable 5 is back. Treat the UI as a receipt, not the whole record.
Anthropic now says access to Claude Fable 5 and Mythos 5 is restored, with Fable 5 included for up to 50% of weekly usage limits through July 7 before moving to usage credits.
Also filed underaiclaudefablemythosmodel-access
Claude Sonnet 5 just showed up. Read the release through the receipts.
Anthropic's Sonnet 5 rollout is the first Hugin news post because it is exactly the kind of update that needs source links, capability context, and a little restraint.
Also filed underaiclaudemodel-release
A record appears here because it carries anthropic 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.