Staged Rollout with Rollback Criteria

Staged Rollout with Rollback Criteria A lifecycle diagram generated by Archify. 01 / Release stages 02 / Stage verdict + Rollback path 03 / Outcome Plan registered · criteria set first · Release stages · before 01 Plan registered criteria set first before Shadow · outputs not used · Release stages · no exposure 02 Shadow outputs not used no exposure Pilot · trained users · Release stages · small group 03 Pilot trained users small group Canary · vs control group · Release stages · share of traffic 04 Canary vs control group share of traffic General availability · criteria stay live · Release stages · all traffic 05 General availability criteria stay live all traffic Hold · more evidence · Stage verdict · verdict Hold more evidence verdict Rolling back · flag or blue-green · Rollback path · automatic Rolling back flag or blue-green automatic Baseline restored · rollback recorded · Outcome · evidence Baseline restored rollback recorded evidence Legend start active state waiting decision terminal success

Criteria before the stage

  • • Metric, threshold, window and group breakdowns are written into the plan first
  • • A threshold change is a reviewed diff, not a dashboard edit
  • • A criterion invented after the metric moved is a negotiation

The pipeline decides

  • • Canary analysis compares candidate and control per metric and per group
  • • The verdict is promote, hold or roll back
  • • Vendor model versions go through the same stages

A tested way back

  • • Versions are pinned in the registry for baseline and candidate
  • • The switch back is exercised in shadow, before anyone depends on it