Checklists we stole from release engineering

Our Backup and Recovery War Room track borrows language from release engineering: freeze windows, communication trees, and explicit rollback owners. The metaphors land because many participants already live in CI systems.

We stress that checklists must be owned by the team adopting them. Templates are starting points, not policy mandates.

During the capstone, teams adapt a checklist to a fictional multi-region cutover. Instructors grade on clarity and feasibility, not speed.

We publish anonymized exemplars in the resources library so alumni can remix responsibly inside their own organizations.