# Write the rollback trigger before deployment

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Write the rollback trigger before deployment

ID: MHC-D-RESEARCH-0345 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/write-the-rollback-trigger-before-deployment

'We will know when to roll back' is not a rollback condition.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A change can degrade service and people may hesitate to roll back once effort has been invested.

### Avoid when

- Thresholds can be noisy or incomplete; allow human escalation when evidence is serious but the predefined metric misses it.

### Explanation

Before deployment, define observable signals that mean the change should stop or reverse: error rate, failed reconciliation, latency, business invariant, unexpected side effect or another relevant threshold. Also define who can call the rollback. This converts a stressful judgment into a prepared decision and reduces the temptation to wait for certainty while impact grows.

### Checklist

- The rollback condition is observable during the rollout.
- The signal is tied to the change's real failure modes.
- An owner has authority to stop or reverse the rollout.
- The condition distinguishes rollback from a tolerable transient effect.
- The recovery path is known before the trigger fires.

### Example

Rollback if more than 0.5% of updated records fail the post-write invariant or if replication backlog exceeds the agreed threshold for ten minutes.

### Check

A responder can decide whether the trigger fired without inventing a new rule during the incident.

### Limits

- Thresholds can be noisy or incomplete; allow human escalation when evidence is serious but the predefined metric misses it.

### Evidence and sources

- supports: AWS recommends documenting rollback criteria and the rollback or fix-forward plan before deploying a change. — RS-0B17D9040762A762. Rollback is not always safer than fixing forward, particularly for irreversible data migrations; the strategy must match the change. (Implementation guidance)
- RS-0B17D9040762A762: OPS06-BP01 Plan for unsuccessful changes — https://docs.aws.amazon.com/wellarchitected/latest/framework/ops_mit_deploy_risks_plan_for_unsucessful_changes.html

### Vedokrok editorial review

Define the stop signal and recovery choice

Before deployment, decide what failure will stop the rollout and what happens next. Stopping new changes and reversing completed changes are different decisions.

#### Make the trigger observable

Name the signal, its threshold or clear failure condition, the observation period and the person or automation allowed to act. For a data migration, a broken required relationship can trigger a halt while the affected records are examined. Choose values for the actual failure mode; an example percentage is not a general safety threshold.

#### Choose a recovery path that fits

State when to restore the previous version and when to fix the current state. A rollback must remain compatible with changed data and dependencies. If reversing the change is unsafe or incomplete, specify containment and a tested fix-forward plan. Keep an escalation route for serious evidence that the chosen metrics miss.

**Editorial takeaway:** Walk through one simulated breach: can the responder identify the trigger, stop further exposure and choose a viable recovery path without inventing a rule?

#### Editorial evidence

- supports: AWS calls for documented, tested recovery plans and explicit requirements for rollback. — RS-0B17D9040762A762. Selected official passages read on 2026-10-04. Signal selection and the simulated breach are editorial review actions, not experimentally validated thresholds. (Implementation guidance; Implementation steps 1 and 5)
- limits: AWS explicitly allows fix-forward circumstances and discusses changes that cannot be rolled back. — RS-0B17D9040762A762. Selected official passages read on 2026-10-04. A failure signal does not establish that reversal is the safest recovery action. (Implementation guidance; Implementation steps 1.1 and 4)
- RS-0B17D9040762A762: OPS06-BP01 Plan for unsuccessful changes — https://docs.aws.amazon.com/wellarchitected/latest/framework/ops_mit_deploy_risks_plan_for_unsucessful_changes.html

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/make-the-rollout-stop-itself-on-a-known-bad-signal
