Deliberately small
Python standard library. Local CSV input. Text or JSON output. No credentials, third-party dependencies, or network access.
ENGINEERING PROJECT / PROJECT DETAILS
Recovery Readiness Auditor
ENGINEERING ARTIFACT / PYTHON
Recovery is a process.
Start with the evidence.
Download the preserved Recovery Readiness Auditor archive
The Recovery Readiness Auditor checks a declared service inventory for missing owners, overdue backups, stale restore tests, and incomplete recovery information.
Explicit assumptions
Checks recorded evidence against declared objectives. A clean report does not prove recoverability; restore exercises remain essential.
Testable behavior
13 automated tests cover time boundaries, timezone offsets, malformed input, missing fields, duplicate services, and CLI behavior.
EXAMPLEInspect the sample findings
Three fictional services · Audit time: September 6, 2026, 12:00 UTC
- Inventory API: no recorded gaps under the configured checks.
- Reporting Database: backup older than its 4-hour RPO; restore test older than the 90-day policy.
- File Services: missing accountable owner and recovery runbook reference.
Source code, fictional sample data, automated tests, design notes, and the CI workflow are available on GitHub.
Problem, implementation and evidence
A configured backup schedule does not establish a usable recovery.
The source project audits recovery-readiness evidence. The new recovery notebook separately checks fictional RTO, RPO and application-validation results.
What the evidence establishes
Source-linked project plus executed educational fixture; no restore of a production workload was performed.
Reproduce or extend
Retain a dated restoration log, data-integrity check and business acceptance record for an actual recovery test.
Open the related experiment or review surface →