The Software Rollback Readiness Evaluator

 Build a release readiness tool that evaluates whether a software deployment can be safely reversed if production problems occur.

Users define an upcoming release, application changes, database migrations, configuration changes, external service dependencies, and available recovery procedures.

The application must:

1. Classify changes as reversible, conditionally reversible, or potentially irreversible.

2. Identify database migrations that may prevent the previous application version from functioning.

3. Track backups, restore procedures, feature switches, and recovery dependencies.

4. Model rollback scenarios involving partial deployments, failed migrations, and configuration mismatches.

5. Identify data written by the new version that older versions may not understand.

6. Generate a pre-release checklist and explicit rollback prerequisites.

7. Record rehearsal results, recovery duration estimates, and unresolved risks.

8. Produce a release decision report with evidence for each readiness claim.

Include a dependency graph, rollback scenario builder, recovery checklist, and downloadable report.

Do not claim that a rollback is safe merely because an application artifact is available. Distinguish documented procedures from successfully rehearsed procedures, and require explicit confirmation before any production action. Include sample migration scenarios and tests for incompatible schemas and irreversible data transformations.