Editorial review pendingon version support under review
Action boundary
Before you act
- Expected result
- A sandbox run sheet contains entry evidence, release-specific actions, acceptance results, and a recorded decision.
- Failure mode
- The rehearsal mutates shared or production state, or success is declared without acceptance evidence.
- Rollback
- Stop the rehearsal, isolate the sandbox, use its approved restore path, and preserve the decision log.
Make the rehearsal boring on purpose
Use a disposable or isolated instance that represents the boundaries you care about. Record its starting version, configuration provenance, state baseline, and recovery point before applying any release-specific steps. If the sandbox cannot represent a critical integration or state boundary, say so in the decision record; do not call it equivalent.
Entry conditions
Do not start until you have the exact target release, current official release and migration sources, recovery owner, rollback trigger, acceptance checks, and a place to store redacted evidence. The installed CLI’s help and the release-specific runbook govern commands. This fixture does not prescribe them.
Acceptance checks
Choose checks that correspond to the risk score: process/service health, a bounded gateway or channel path, configuration load, expected state availability, and the absence of a regression in a known workflow. For each check, record the expected result, actual result, evidence location, and assessor.
Lab: the controlled failure
Run a synthetic rehearsal. At a planned point, introduce an agreed failure signal or stop condition. Pause, capture evidence, and decide whether the run is a rollback rehearsal or a defect investigation. Do not improvise a fix merely to complete the lesson.
Check: the run sheet should let a reviewer see the decision point in under a minute. If the outcome is “looks fine,” it is not a useful result.
Learner artifact
Draw a one-page run sheet with entry gates, action column, evidence column, stop condition, and decision. Its text alternative must preserve the sequence and identify that release-specific commands are intentionally omitted pending primary-source review.
Lesson checkpoint
Ready to move on?
Mark this lesson complete when you can apply its outcome without relying on the examples above.