Rotation calendars fail when they live only in tickets. We ask learners to produce a single-page calendar with owners, windows, and rollback phone trees.

The workshop emphasizes that break-glass paths must name humans, not mailing lists that route to /dev/null. We tabletop two failures: missing approver and partial deploy.

Nothing here replaces vendor documentation. We aim for operational poetry—enough structure that night crews trust the page taped to the wall.