Safety and MLOps
Model registry
A model registry records versioned model artifacts and their lifecycle metadata.
How it works
It connects a deployable artifact to training data, code, metrics, approvals, and status. This makes rollback and audit possible.
A concrete example
Illustrative: version 17 links one artifact hash, 6 metrics, and 2 approval records.
Do not confuse it with Artifact store
an artifact store holds files; a registry adds identity, metadata, stages, and lineage.