Check relational invariants after restoration
A restore exits successfully but an earlier disabled constraint allowed orphan case assignments into the backup.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Relational integrity · Schema verification
Estimated field mix
- Database engineering70%
- Quality engineering30%
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.
- ARESTORE-101 · Inventory database recovery inputs beyond the dump file
- ARESTORE-102 · Create a backup manifest that binds bytes to schema revision
- ARESTORE-103 · Validate that a restore target is isolated before running destructive steps
- ARESTORE-104 · Restore a verified backup into a new database generation
Acceptance criteria
- Check expected foreign keys, unique constraints and required indexes.
- Run explicit orphan and duplicate queries on restored data.
- Fail application activation when invariants do not hold.
Implementation constraints
- Compare actual catalog metadata with the declared migration contract.
Verification to include
- Validate a clean synthetic restored database.
- Restore a deliberately inconsistent fixture and report exact invariant failures.
Deliverables
- Post-restore SQL verification suite
Rollout and recovery
Run before connecting application traffic; retain the failed generation for bounded diagnosis.
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.