Model Registry & Versioning
Artefact lineage, promotion gates, rollback, and versioning models and their data together.
6concepts
67flashcards
43minutes of reading
- 01 Model Cards and Intended Use What documentation a model version needs to be safely reused by someone who did not build it, why disaggregated evaluation is the substantive part, and how model cards become checkbox exercises.
- 02 The Registry as a Promotion Gate Why a model registry is a workflow rather than a storage location, what a stage transition should require, and the difference between a registry that records decisions and one that enforces them.
- 03 Model Lineage Across Retraining Why a chain of fine-tuned and distilled models makes provenance a graph rather than a record, what has to be tracked at each edge, and the failures that follow from losing it.
- 04 Rollback, Pinning and Reproducible Serving What it takes to revert a model change under incident conditions, why the model is usually not the only thing that has to revert, and the mechanisms that make a rollback fast rather than heroic.
- 05 Versioning Compound LLM Systems Why an LLM application's version must bind the model snapshot, prompt, retrieval index, tools and decoding settings into one identifier, and how provider deprecations turn rollback from a button into a migration.
- 06 What a Model Version Actually Contains Why weights alone are not a deployable model, the full set of artefacts that must move together, and the coupling failures that occur when one of them is versioned separately.