LLMSwaps

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

Successor model: the destination, named or not

A successor is the model a retirement notice names as the destination. One dated row in this register carries one, and it is a later version of the same model. Everywhere else the ending arrives without a destination and the customer chooses, which is the expensive half of a migration. As of 2026-09-22.

What naming a successor settles, and what it does not. Recorded 2026-09-22.
Settled by naming oneStill open
Where to start testingWhether prompts carry over
Which version the vendor expects you to useWhether pricing is comparable
That somebody thought about continuityWhether the move is performed for you
A candidate, before the runway is spentWhether the successor has its own date

Inclusion rule. Filled only where the notice that announced an ending also names what follows it. A newer version existing is not a published statement. Order. What naming one settles first, then what it leaves open.

1A runway cannot be spent without a candidate

The work a notice period is for is testing whatever comes next, and that cannot start until somebody decides what next is. So a date without a destination hands a reader the easier half of the problem.

Five months of warning is worth much less when the target is unstated, because choosing wrong spends the runway twice.

A complete disclosure has three partsA date says when work stops. A destination says where it goes. A statement about who performs the move says whose job it is. No entry in this register publishes all three for the same model.Three parts of a retirement disclosureA datePublished by five entries. Says when, and sometimes only theearliest when.A destinationPublished once, in one dated row, as a later version of the samemodel.Who moves youStated once, and the answer is that migration will not happenautomatically.Guessing the obvious successor makes the cell unverifiable, which is the trade refused here
Fig. 1 One dated row here names a successor, and it is a later version of the same model.

2The obvious guess is still a guess

Most readers will assume the maker's newer model is the route, and most will be right. Writing that into a register would make every such cell unverifiable, which is the trade refused in every column here.

The cost of guessing is not abstract. A team that migrated to an assumed successor and found the pricing or region coverage different has spent its runway on the wrong test.

3Naming is not moving

Even where a successor is named, nothing says the platform performs the change. One entry states outright that migration will not happen automatically, which is more useful than leaving it implied.

So a complete disclosure has three parts: a date, a destination, and who does the work. No entry in this register publishes all three.

A definition rather than a dated entry: no line above is a vendor statement. Where this word turns up in a real notice, the wording and the date are on the named replacement column. Nearby terms: Silent update, Endpoint, Published weights.