Roll out a model without betting the whole service
one move: promote with evidence
Open the code pane immediately, then use the Spec tab, optional design question, tests, and artifact when you want them.
Finish each move before carrying the artifact forward.
A model version is a deployable artifact with metrics, latency, and a reversible promotion decision—not a filename.
Deliverable: State the invariant in one sentence.Compare stable and canary quality/error/latency and return promote, hold, or rollback using explicit thresholds.
Deliverable: Type the smallest deterministic implementation.A canary with worse safety or latency must roll back; an improved canary may promote; an inconclusive one must hold.
Deliverable: Record a normal case and a boundary case.Increase traffic weight, inject a latency spike, and test that the decision remains reversible.
Deliverable: Name the failure signal and the guard you would add.A registry entry, canary decision record, and rollback command.
Deliverable: Save the contract, evidence, and handoff note.A canary with worse safety or latency must roll back; an improved canary may promote; an inconclusive one must hold.
Increase traffic weight, inject a latency spike, and test that the decision remains reversible.
A registry entry, canary decision record, and rollback command.
Deriva-authored extension beyond the supplied PDF. The five moves are Deriva’s implementation contract for this project.