Model Registry & Version Pinning

Maintains the inventory of models, prompt versions and their deployment status, and pins production to specific versions rather than floating aliases. Makes a provider model update a decision rather than an event that happens to you.

Anywhere output is retained as a record, and anywhere reproducibility is required.

Exploratory work, where pinning slows access to improvements for no benefit.

Any output entering a record must carry its model and prompt version. Without it, an auditor asking why the system said something six months ago cannot be answered, because the thing that said it no longer exists.

Floating aliases in production. A provider updates the model behind the alias, behaviour changes, and nothing in the deployment records that anything happened.

A generated reconciliation narrative from March, reproducible in September because the model and prompt version were recorded against it.