What problem does it solve? Teams often assume their backups protect them without ever proving a restore works, leaving unknown RTO/RPO gaps, silent backup failures, and untested failover plans that only surface during a real outage. ## Core Features & Use Cases - Recovery Posture Assessment: Builds a posture table comparing stated RPO/RTO targets against achievable values implied by actual backup configuration, with the last proven restore date per asset. - Read-Only Evidence Gathering: Inspects IaC, cloud snapshots, bucket versioning, object lock, and restore-test records using read-only commands like aws rds describe-db-snapshots and velero get backups without ever triggering a restore or failover. - Remediation Planning: Produces self-contained drill plans that restore into isolated scratch environments with STOP conditions protecting production, measured validation, and a recurring test cadence. - Use Case: Ask whether your production PostgreSQL database could survive a region loss, and receive a findings table showing that snapshots exist but no restore has ever been tested, so RTO is unknown, plus a plan to run a quarterly restore drill. ## Quick Start Run a disaster recovery review of my production infrastructure and tell me whether the backups for the main database have ever been restore-tested and what the real RPO and RTO are.
