Validate that a restore target is isolated before running destructive steps
A copied restore command could replace the development database instead of the disposable drill target.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Operational safety · Input validation
Estimated field mix
- Database engineering50%
- Security50%
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 case-management team has nightly backup files but has never tested application behavior after restore. Missing roles and external artifact references may make a successful database restore unusable.
Setup prerequisites
- Create a disposable synthetic database and local backup directory.
- Never connect these drills to production or overwrite a shared database.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Require an explicit disposable target identity and expected marker.
- Resolve and inspect target connection metadata before mutation.
- Reject shared, production-like or unmarked targets.
Implementation constraints
- Use exact database names and task-specific credentials; no wildcard cleanup.
Verification to include
- Plan a restore to a marked disposable target.
- Point at an unmarked synthetic target and verify zero destructive calls.
Deliverables
- Restore-target guard and denial tests
Rollout and recovery
Make the guard mandatory for drills; abort if target identity changes.
Value of the work
For the engineer: Practice restore verification, provenance and operational recovery.
For the team: Review evidence that recovery produces coherent usable state under declared limits.
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.