matt-bat Restore Drill
Mission
Demonstrate recoverability instead of assuming that a backup is usable.
Preconditions
Require:
- an identified backup artifact
- an authorized isolated restore target
- an ordered restore runbook
- recovery point and recovery time objectives
- success, stop, and cleanup criteria
If an external target or authority is missing, remain blocked without creating one implicitly.
Drill Selection
Choose the smallest drill that proves the exposed risk:
tabletop: validate people, prerequisites, sequence, and failure branchestechnical_partial: restore one affected subsystemtechnical_full: restore the complete exposed systemfailure_variant: inject a controlled artifact, credential, or dependency failure
A critical production release may require a recent full drill. Local source changes do not.
Execution Contract
- Verify artifact identity and integrity before restoration.
- Restore only into the authorized isolated target.
- Capture phase timestamps and exact failures.
- Validate functional, data, security, and compatibility expectations.
- Compare achieved recovery point and recovery time to targets.
- Clean up the drill environment according to its authorization.
Read restore-drill-runbook.md for detailed evidence and failure scenarios.
Pass and Veto Rules
Pass only when:
- restoration completes without unrecoverable error
- integrity and critical functional/data checks pass
- required recovery objectives are met
- no unresolved critical remediation remains
A stale, incomplete, unauthorized, or failed drill vetoes the dependent external operation. It does not block unrelated local work.
Output Contract
Provide:
- target, artifact, and drill type
- validation and timing evidence
- pass, conditional, blocked, or failed result
- remediation and dependent-operation status
Related Skills
- Project Backup: establish backup identity and coverage.
- Skill Governance: decide when recovery evidence gates an operation.
- Regression Prevention: validate source and local runtime changes.