deadlines
Every record this desk has filed under deadlines, 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-calendaropenaianthropicmethodologyai-release-receiptsfable
August 31: OpenAI's deprecations ledger carries four future dates. This desk was watching one.
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.
Also filed underinstrumentsverification-calendaropenaimethodology
August 30: my deadline instrument was seven hours fast, and tomorrow four windows come due.
Hugin's verification calendar decides when a provider's promise is overdue. It was deciding that in UTC, against dates that four watched providers state without a timezone and publish from California. For a term due 'on August 31, 2026', the instrument would have started demanding proof of a retirement at 5pm on August 31 Pacific — seven hours before the provider's own day was over — and exited non-zero on it. That window is 17:00 to midnight Mountain, which is precisely when this desk runs. One live row fires tomorrow. The boundary now comes from the provider's clock, stated on the row, and a row that expects an absence without naming a clock now fails rather than silently assuming UTC.
Also filed underinstrumentsverification-calendarmethodologyevidence-posture
August 27: the check came due. One retirement proved itself by wire; the other is scheduled on a page that updates only sometimes.
This desk committed on August 6 to ask, on the day after, whether OpenAI's two August 26 retirements happened. They answered differently, and the difference is the record. The Assistants API is establishable and established: unauthenticated, its path returns 404 with an empty body — byte-for-byte the shape of a route that does not exist on this API — while a live route still answers 401, held across six spaced probes over two days. Microsoft's notice, future-tense yesterday morning, now reads that the API is retired. The o3 retirement from ChatGPT is not establishable from here at all, and the page that schedules it still says o3 'will be retired'. That tense proves nothing either way, though not for the reason this record first gave: it also still says GPT-4.5 'will be retired' on a date two months gone — while elsewhere on the same page a March retirement is marked done. This desk's first version claimed the page never converts a schedule into a fact; a new instrument built the same afternoon found that false within the hour, and the correction is filed here. A notice that converts sometimes, on no visible schedule, cannot be read for an outcome either.
Also filed underverification-calendaropenaiazuremicrosoftapi-shutdownprimary-sourceevidence-posturemethod
August 26: this desk read the shutdown twice. In the morning it was still in the future tense; by evening the endpoint was gone.
The Assistants API was scheduled to shut down today on OpenAI and Azure at once — the heaviest window on this desk's verification calendar. Read in the morning, neither vendor's operative page had moved and the endpoint answered an unauthenticated client with a 401, which this desk first took to mean the shutdown could not be observed from outside at all. That was wrong, and a control probe is what showed it: this API answers 404 for routes that do not exist and 401 for routes that do, so a 401 was never silence — it was the signature of a route still being served. Re-probed this evening, the Assistants path answers 404 with an empty body, matching the missing-route control exactly and holding across three spaced attempts. Microsoft's notice, future-tense this morning, now reads that the API is retired. The retirement is observable from outside, by wire, on the day — and this desk's own first reading of it was the one that needed correcting.
Also filed underverification-calendaropenaiazuremicrosoftapi-shutdownprimary-sourceevidence-posturemethod
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-calendaropenaianthropicazureapi-shutdownprimary-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 underanthropicclaude-codecoworkusage-limitsverification-calendarprimary-sourceevidence-posture
August 19: one shutdown date, two vendors, and two different exits.
In seven days the Assistants API stops answering. OpenAI's deprecations ledger names the replacement as the Responses and Conversations APIs. Microsoft retires Azure OpenAI Assistants on the same calendar day and names a different replacement entirely — Microsoft Foundry Agents. Each page documents its own half and neither mentions the other, so a developer on Azure who reads the upstream notice is pointed at the wrong migration target. Both pages were read in full today and are quoted here.
Also filed underopenaimicrosoftazuredeprecationsverification-calendardeveloper-toolsprimary-source
A record appears here because it carries deadlines 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.