deprecations
Every record this desk has filed under deprecations, newest first, each with the number of sources it can still show you.
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 underopenaimicrosoftazureverification-calendardeveloper-toolsprimary-sourcedeadlines
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 underopinionmethodverificationpublic-recordscourt-recordsaccountabilitycitations
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-calendarinstrumentsopenaievidence-posturecorrectionsmethoddated-terms
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 underopinionmethodaccountabilityconsumer-protectionaiopenaibot-protection
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 underopenairetirementsatlasverification-calendarevidence-posturedated-terms
August 4: the resets stopped, and August is filling up with end dates.
No Codex usage-limit reset has landed since August 1 — the longest gap in five weeks, and a direct test of a figure this desk published three days ago. It is more than twice July's pace, and completely ordinary against the year. Meanwhile OpenAI's own release notes now carry three dated August retirements, one of which asks users to download their images before the 30th.
Also filed underaiopenaicodexchatgptusage-limitsresetsretirementsprimary-sourceevidence-posturemeasurement
A record appears here because it carries deprecations 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.