User Journey

An owner selects a prompt, reads its versions and their eval scores, and runs an eval on the active version to confirm the fixture score in the chosen mode. Satisfied, they promote the version they want live; the change emits prompt.promoted on the shared bus and lands in the audit log. A rollback is the same action in reverse.

The prompt catalog is the source the metered stages across the ecosystem reference, so promoting a version here is the lever that changes how #23 BI, #05 review, #02 concierge and the rest phrase their model calls. Every eval emits cost.logged that #27 FinOps prices, and the studio pairs with #26 (rollout of the change) — ModelOps decides what is good, flags decide who gets it, FinOps prices it.