A date that may move against a right with no date

Both entries tell a reader their published position is softer than it looks. One describes its dates as the earliest a model might be retired, so each is a floor. The other publishes no dates and a reserved right to replace models, so every ending is unscheduled. From 2 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.

Fig. 1 Filled where the entry's own page addresses that point, hollow where the page is silent on it.

What each entry admits about the reliability of its own position. Recorded 2026-09-22.
On this point	Gemini API	LTX Studio
Are dates published	Five video identifiers carry one	None anywhere on the page
What the published position admits	The date is the earliest, not the day	That no availability is guaranteed
Direction of the uncertainty	Later than stated	At any time, with no statement
Is notice described	Promised in words, never counted	Not described at all
What a reader should watch	The table, for new rows	The plan table, on two readings

Inclusion rule. Both cells on a row come from the entry's own published pages: a deprecations page for the platform, a priced page and footnote for the application. Order. Whether dates exist first, then what each position admits.

1Two forms of candour about the same weakness

Both pages decline to pretend their positions are firmer than they are. One does it by qualifying its dates, the other by publishing a right instead of a date. Neither leaves a reader with a false floor.

That is rarer in this register than either arrangement's weakness suggests. Most pages here simply say nothing, which lets a reader invent a stability nobody offered.

Fig. 2 A floor narrows the possibilities; a reserved right narrows nothing, so the comparison is not symmetrical.

2Qualified dates are still better than no dates

A floor narrows the possibilities: work can be scheduled up to it and nothing ends before it. A reserved right narrows nothing, because the ending can land in any week.

So the comparison is not symmetrical. One page gives a soft date and the other gives an honest absence, and the soft date supports more planning.

3Where each leaves the work

With a floor, the work is to have a migration ready and hold it. With a reserved right, the work is bookkeeping from the first episode, because there is no moment to prepare for.

Both conclusions are in the explainers rather than in the register, since neither depends on which entry a production chose. The planning page sets out the parts that apply either way.

4The same question, put to a third entry

What SceneMixer publishes on this column, beside Gemini API and LTX Studio. Recorded 2026-10-13.
On this point	SceneMixer	Source
Work already made	Sheets and segments already made keep their pixels and their record of which tier made them; versions are kept, and nothing is regenerated or charged by a fallback	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.

What a date in that table commits to
The shutdown dates listed indicate the earliest possible dates on which a model might be retiredGoogle, Gemini deprecations / recorded 2026-09-22
Published notice
The pricing page reserves the right to update, modify or replace available models and does not guarantee continued availability of any specific modelthe only one of its kind hereLTX Studio, pricing / recorded 2026-09-12

5Sources

Both readings come from the pages the entries publish themselves: Gemini API and LTX Studio, read 2026-09-22. The column being compared is Ending early. Other pairs: Foundry and Bedrock on states, Sora and the Gemini API.