Write the rollback procedure and prove it on a preview environment
A rollback procedure that has actually been executed, not just written down and hoped for.
The ticket
Write the rollback procedure and execute it against a preview environment.
Acceptance criteria
- Every step is executed against a real environment and captured
- Time to roll back is measured
- Data migrations that cannot be reversed are called out with the alternative
- The procedure is linked from the deploy documentation
What lands as proof
A captured execution against a real environment, with the elapsed time recorded.
Why teams defer it
- It is only needed during an incident, which is the worst time to discover it was never tested.
- Proving it needs an environment somebody is willing to break on purpose.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: write the rollback procedure and execute it against a preview environment. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means the rollback executed and captured, not merely documented, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.