LLMSwaps

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

Reproducibility: the absence every entry shares

Reproducibility is whether output made on a version can still be produced later. No entry in this register publishes anything about it. For a series that is the most consequential silence here, because it decides whether a season can be finished in the look it started in. As of 2026-09-22.

Why this is the silence that matters most to a series. Recorded 2026-09-22.
What the register can recordWhat nobody publishes
A retirement date, where one existsWhether a version behaves the same next month
A notice period, on three entriesWhether an update will be announced
A model and version named on a pageWhether a project keeps the model it started on
A licence for downloaded weightsWhether the weights keep running on new tooling

Inclusion rule. Applied across every entry in this register. No page read for this site addresses whether output stays reproducible. Order. What is recorded first, then what is missing.

1A retirement is a deadline; drift is a mystery

A shutdown date produces a decision. A model that changes behaviour while keeping its name produces a look that moves across a season, which reads as inconsistency to an audience and as an unexplained problem to the team.

Nothing in this register warns about the second, because no vendor publishes anything to record. That is the gap the explainers address and the columns cannot.

A retirement is a deadline; drift is a mysteryA shutdown date produces a decision. A model that changes behaviour while keeping its name produces a look that moves across a season, which reads as inconsistency to an audience and as an unexplained problem to the team.A retirementDrift under one nameHas a dateSometimesNeverProducesA decisionA mysteryRecorded anywhereOn five entriesNowhere at allCaught byReading a pageA frozen test setThe delivered file is the one asset that does not depend on somebody else's roadmap
Fig. 1 Recorded as a term rather than a column, because a column would be sixteen identical blanks.

2What a production can hold instead

The delivered files at the quality delivered, stored outside the vendor, with the model and version recorded per file. That is the only asset in this field that does not depend on somebody else's roadmap.

A prompt archive is not a substitute, because the thing that will not exist later is the model. A prompt without its model reproduces nothing.

3Why it is not a column

Columns in this register hold values vendors publish into. Nothing is published about reproducibility anywhere, so a column would be sixteen identical blanks and would imply the question had been asked and refused.

Recording it as a term instead keeps it visible without pretending it is a measurement. The planning page covers what to do about it.

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 in-place update term. Nearby terms: Deprecated, Retirement date, Shutdown.