One word applied twice against a listing that is the state
Neither of these makers publishes a state vocabulary and both convey a condition anyway. One used a single undefined word and applied it to two surfaces on dates five months apart. On the other, appearing on the deprecations table is itself the state, because it means a date has been written down. From 2 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.
| On this point | Sora | Gemini API |
|---|---|---|
| What signals the condition | The word used in the notice | Presence on the deprecations table |
| Is it defined | Not defined anywhere | Not applicable; presence is binary |
| Does it carry a date | Two dates, both fixed | A date stated as the earliest |
| Is there a middle condition | None was ever published | None; a model is listed or not |
| What a completed case looks like | Both surfaces closed | A past date, with the row remaining |
Inclusion rule. Both cells on a row come from the maker's own published pages. Coverage of either announcement is not used. Order. What signals the condition first, then what it carries.
1Binary conditions are clear and coarse
Both arrangements tell a reader one thing unambiguously: something has been scheduled. Neither can express the condition most models in this field are actually in, which is available with no date and no plan published.
A three-state vocabulary can say that. These two cannot, and both are honest about it by simply not having a word for it.
2One case has already completed on each
One maker's two closures both arrived. The other's preview identifiers passed their date and the row remains readable. So between them these two entries hold the register's only evidence about how such endings finish.
A completed row is worth keeping for calibration. It shows the wording, the interval and the absence of a successor as they actually resolved rather than as they read in advance.
3Absence means different things on each page
Not being listed on a deprecations table could mean new, healthy, or simply unscheduled. Not being mentioned in a one-off notice means nothing at all, because the notice was about one product.
The register records both as no announced date. The blank date question sets out why that phrasing is the only defensible one.
4The same question, put to a third entry
| On this point | SceneMixer | Source |
|---|---|---|
| A tier briefly unavailable | A tier that is temporarily unavailable is hidden from the tier list rather than offered and refused | SceneMixer, withdrawn tier guide |
| A tier that has been retired | A segment submitted on a retired tier is refused with a message before anything is held, and the selector no longer lists that tier | SceneMixer, tier no longer exists guide |
Inclusion rule. SceneMixer's own statements that bear on the column this pair was chosen for. Order. The statement closest to the column first.
All of its readings are on the SceneMixer entry.
- Sora web and app26 April 2026discontinued
- veo-3.0-generate-preview and veo-3.0-fast-generate-preview12 November 2025shutdown date
5Sources
Both readings come from the pages the entries publish themselves: Sora and Gemini API, read 2026-09-22. The column being compared is Lifecycle states. Other pairs: LTX Studio and Kling AI, invideo AI and fal.