/3 CONNECTED STEPS
Prove an application can recover
Produce a recovery runbook backed by an isolated restoration and successful application writes.
Download complete workflow .md ↓Use with your AI
Complete workflow download included with library membership. Try the free starters without signup.
What you need
A named authorized backup, compatible runtime, application files and a disposable isolated target.
Why these fit together
Recovery classification prevents confusing a code rollback with recovered data; the restore checks readability; write and sequence checks prove the recovered app can continue operating.
Follow this order
Separate deploy rollback from data recovery
Separate code, database and object-file recovery.
Prove a backup restores in isolation
Restore and observe an isolated copy.
Test writes and sequences after restoration
Verify writes, readback, cleanup and identifier continuity.
Give this task to your AI
Use the Prove an application can recover workflow. My task and inputs are supplied below. Read the prerequisites and check your available tools. Follow the core steps in order, passing the actual output of each step to the next. Adapt installation and commands to this environment; do not copy another agent's configuration blindly. If a required tool or input is missing, identify it before that step. Run the completion check and report observed results and unresolved work.
Setup to provide or build
A concrete supported app/database stack, disposable fixture backup, restoration commands and cleanup verification.
Check the result
Restore the fixture, read representative records, create and delete a record without reusing archived IDs, record recovery time and verify cleanup.
Curated implementation workflow. End-to-end execution must be verified in your environment.
Optional additions
Load these only when your task needs them.