ALL-DEPL1004 · rollback_readiness
Judge whether a deployment has a usable rollback path.
This is a contextual rule for all languages. Read its implementation.
Definition
Section titled “Definition”Ask the selected judgment backend for five independently cited rollback facts and reduce them through a fixed decision table. Compare artifacts, state compatibility, steps, timing, owner authority, rehearsal evidence, and material blockers.
Evidence
Section titled “Evidence”The frozen bundle cites rollback artifacts, state, timing, owners, rehearsal runs, and
blockers.
Missing, duplicate, conflicting, or uncited answers remain unknown and reduce to uncertain.
Exceptions
Section titled “Exceptions”A change with no deployed effect can be not_required. An authorized one-way change needs a
verified recovery path and should be assessed by the migration rules instead.
Examples
Section titled “Examples”A compatible path with an owner and recent timed rehearsal is ready. A documented command
that has never run under representative conditions is unverified.
References
Section titled “References”- Cites “The Site Reliability Workbook”, Canarying Releases
- Cites “Accelerate”, continuous delivery
- Cites “Release It”, stability patterns