Guard restore commands against non-scratch targets
A restore command can overwrite an existing developer database by mistake.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Operational safety
Estimated field mix
- Developer tooling50%
- Site reliability30%
- Security20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional reporting service has successful backup jobs but no recent restore rehearsal. Database rows reference objects with different retention schedules.
Setup prerequisites
- Create disposable local database and object-store fixtures with synthetic reports; author backup and corruption examples.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Require an explicit scratch target.
- Reject nonempty or unapproved destinations.
- Display sanitized target identity.
Implementation constraints
- No remote or production endpoints in this exercise.
Verification to include
- Restore into an empty named scratch database.
- Reject an occupied or remote destination.
Deliverables
- Restore target guard.
Rollout and recovery
Default to inspection-only until target validation passes.
Value of the work
For the engineer: Practice recovery consistency, integrity validation, and honest recovery objectives.
For the team: Replace backup-job optimism with a repeatable restoration assessment.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.