LLMSwaps

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

Silent update: the change no page records

A silent update is a model changed in place: the name stays, the weights or the serving behaviour move, and no page records anything. For a production it is more disruptive than a retirement, because nothing marks the moment it happened and there is nothing to plan against. As of 2026-09-22.

Why this is the failure mode a register cannot catch. Recorded 2026-09-22.
What a register can seeWhat it cannot
A model name leaving a pageThe same name meaning something new
A dated retirement noticeAn update with no announcement
A new version appearingBehaviour changing under an old one
A price or conversion movingSafety filters or presets changing

Inclusion rule. Distinctions drawn from what the pages in this register do and do not record. No entry here publishes an update policy for a named model. Order. What is observable first, then what is not.

1One entry publishes the right to do it

A pricing footnote in this register reserves the right to update, modify or replace the models on offer. Of those three verbs only replacement changes a name on a page, so the other two are invisible by construction.

That is the most honest statement about silent updates anywhere here, and it is on the page of an entry that publishes no notice period. Candour and commitment are not the same thing.

2What catches it is a test set, not a page

Four or five prompts with known output, kept unchanged and re-run after any suspected change, is the only detection method that works. Its value is entirely in being unchanged, so improving the prompts destroys it.

That is production work rather than register work. No amount of page reading substitutes for it, and this site records what the pages say precisely so that it is not confused with measurement.

What a test set catches that a page cannotFour or five prompts with known output, kept unchanged and re-run after any suspected change, is the only detection method that works for an in-place update. Its value is entirely in being unchanged.Reading pagesA fixed test setCatches a renameYesYes, indirectlyCatches an in-place updateNoYesCatches a preset changeNoYesCostsTwo readings and a dateKeeping five prompts frozenOne pricing footnote here reserves the right to update, modify or replace
Fig. 1 Production work rather than register work, which is why this site records what pages say and calls it that.

3Why it matters more than a retirement

A retirement has a date and produces a decision. A silent update produces a look that drifts across a season, which reads as inconsistency to an audience and as a mystery to the team.

Nothing in this register addresses reproducibility, and no entry publishes anything about it. The reproducibility term sets out what that absence means.

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 recovery order after a change. Nearby terms: Endpoint, Published weights, Inference.