LLMSwaps

Which model each app runs today, and when it last changed

A number of days against a promise of notice

Both entries are lifecycle documents from large platforms, and only one of them yields a runway. A period counted in days can be scheduled against. A promise of advance notice with no number is a statement of intent, and this register records it as an unfilled cell rather than a generous one. As of 2026-09-22.

What each lifecycle page commits to before a model goes. Recorded 2026-09-22.
On this pointMicrosoft FoundryGemini API
Is a period publishedYes, thirty days at preview stageAdvance notice promised, not counted
Can a runway be calculatedYes, from the stage of the modelNo, nothing yields a figure
Are dates published tooTwo dated rows for the video modelFive dated video identifiers
What the dates meanFixed, and stated as non-extendableThe earliest a model might go
Is a successor namedFor one of the two dated rowsNot on the deprecations table

Inclusion rule. Both cells on a row come from the entry's own lifecycle documentation. A figure stated for a non-video model still counts, because the policy is written for every model served. Order. The period first, then the dates, then what follows them.

1More dates and less commitment

The entry with more published dates is the one with no published period, which is the pairing worth noticing. A reader who finds five dated rows will feel informed and stop looking for the figure that actually decides a plan.

The other entry has two dated rows and a policy that says how much warning precedes any future one. That is the more useful document and the less impressive-looking page.

More published dates, less published commitmentThe entry with five dated rows publishes no notice period. The entry with two dated rows publishes a figure in days that covers every future retirement. A reader who finds the longer table will feel informed and stop looking.What each lifecycle page actually yieldsOnly five datesDates onlyidentifiers, earliest-possiblewordingBoth listsBoth havea lifecycle page, no successor forvideoOnly a policyA figure30 or 60 days, non-extendable datesOnly one of the two supports a calendar entry
Fig. 1 The more useful document is the less impressive-looking page, which is the pairing worth noticing.

2Fixed dates and floor dates

One page states its dates cannot be pushed back. The other describes its dates as the earliest a model might be retired, so they can quietly become later with nothing published.

Those two sentences look similar and produce opposite plans. One supports a calendar entry; the other supports a migration held in readiness for an unknown length of time.

3Where a promise without a number leaves a reader

It cannot be relied on and it cannot be dismissed. A platform that says it will give advance notice probably will, and a production cannot size the work from the sentence.

So the practical answer is to plan from the published date rather than from the promise, while treating the date as a floor. Both halves are recorded in the ending early reading.

4Sources

Both readings come from the pages the entries publish themselves: Microsoft Foundry and Gemini API, read 2026-09-22. The column being compared is Notice period. Other pairs: Bedrock and the Gemini API, Foundry and Sora.