The model registry: version lines, promotion and acceptance cards.
What you see
The acceptance card
A card is either clean or it names what is missing. It records the evidence a version shipped on — the evaluation verdict, the data sources, the run that produced it — at the moment of shipping, not as a query run later. That distinction is the point. Six months on, the run may have been reclaimed and the benchmark suite may have moved, and a question like “what did we actually check before shipping v3” has no answer unless somebody froze it.A card marked with missing items is not a failure. It is an accurate statement that a version
shipped without some piece of evidence — which is worth knowing precisely because it is easy to do
by accident.
The data flywheel
A closed flywheel means production traffic can feed the next version through Reflow.
What you can do
- Promote a version to production. Deployments pointing at the model follow it.
- Open the acceptance card — it renders as a file a reviewer can read.
- Archive a version, taking it out of circulation without deleting its history.
sf model register, sf model promote, sf model card, sf model archive.