Promotion Is A Transaction, Treat It Like One
Six weeks after a model went live, a reviewer asks what the approver actually saw on screen at sign-off. The registry has the artefact. The ticket has the name. Nobody can reconstruct the decision. This piece argues the missing primitive is an immutable promotion event, and shows what belongs inside it.
May 29, 2026
Your Model Registry Is A Catalog, Not A Court Record
Your registry knows which model shipped. It does not know what the approver agreed to. When an auditor asks which challenger comparison was on screen the moment v17 was promoted, three Slack messages and a timestamp will not answer the question. Here is the promotion event pattern that does, routed by materiality instead of ceremony.
May 28, 2026
Your Registry Cannot Reconstruct the Approver's Screen
Six weeks after a credit model goes live, an auditor asks what the approver actually saw before clicking approve. The registry has the artefact, the metrics, the dataset hash. None of that reconstructs the screen. This is a recording discipline problem, not a tooling one, and the fix is a separate immutable record of decision state.
May 22, 2026
The Approval Click Needs Its Own Event
Your model registry knows the version, the metrics, and the dataset hash. It does not know what the approver was looking at when they clicked approve. Six months later, that is the gap an auditor will sit in. Here is the event you should have been writing all along, and what belongs inside it.
May 20, 2026