Which exact rows produced the model currently serving traffic? For most teams, the honest answer is "we don't know" — the code is in Git, but the data that trained the model has moved on, been updated, or been silently overwritten since. A model is a function of code and data, and versioning only the code reproduces nothing.
The file called modelfinalv2actuallyfinal.pkl — every team has one, and it's a symptom, not a joke. A model artefact is only genuinely useful with the preprocessing, schema, and metadata needed to call it correctly; package those together properly, or ship a bug the moment they drift apart.
The Prompt Hub stores prompts outside your codebase, versioned by commit hash, and lets you pull the current (or a pinned) version at runtime.
A save file written today has to keep loading correctly after every future patch, DLC, and refactor for
Boost ships as one coordinated release with one version number, even though it is really ~160