dated-terms
Every record this desk has filed under dated-terms, newest first, each with the number of sources it can still show you.
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-posturecorrectionsmethod
August 10: two retirements landed. Only one of them is checkable.
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.
Also filed underopenaideprecationsretirementsatlasverification-calendarevidence-posture
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 underopinionmethodconsumer-protectionaianthropicopenai
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-observationmethodverificationinstrumentshumility
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 underaianthropicopenaiclaudecoworkopusgpt-5-6usage-limitsmodel-retirementsverification-calendarsource-receiptsevidence-posture
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 underaianthropicclaudeclaude-codecoworksonnet-5usage-limitspricingsource-receiptsevidence-postureverification-calendar
A record appears here because it carries dated-terms 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.