Prompt & Configuration Registry · View 04 of 21 · People and journeys
The trough, and what answers it
- Release is where the sentiment line falls, and it is not a UX problem: the engineer cannot tell whether the change is live on the whole fleet, half of it, or none of it.
- The answer is structural — the convergence metric on view 14 and the digest on every answer from view 12. Without them this phase is a guess dressed as a deploy.
- The second pain, an eleven-minute eval, is accepted rather than solved: a gate that is fast enough to feel instant is a gate measuring something trivial.
Assumptions
- Evaluation of a digest completes in ≈ 11 minutes at p50 (stated assumption; the number drives whether the gate is synchronous in the promotion flow or a precondition on it).
- Guardrail signals for prompt quality lag the change by minutes to hours, which is why Watch has no automatic verdict in the MVP (ADR-15).
What the platform owes this journey
- A digest on the answer, so the ticket can be traced to a version before anything is edited.
- A diff against what is live, not against the previous draft.
- Rollback reachable in one action from the same screen that did the promotion.
