If your change freeze lives in one wiki sentence, every pager turns into a negotiation, and the loudest voice in the incident channel decides what production is allowed to do at 3am. The fix is unglamorous: make the freeze window a value that runbook steps evaluate, make the unfreeze a recorded decision with named exit criteria, and generate the on-call card from the same file that holds your alerts, first commands, and escalation ladder. Everything below is the artifact I would hand a team on a Monday, including the parts that are deliberately boring.
The 3am question nobody can answer
Picture a CheckoutErrorRateHigh page landing in the middle of a holiday freeze, with a rollback, a config flag flip, and a schema migration all on the table. Three people have three opinions about which of those is allowed, the doc says "freeze", the channel says "just ship it", and the release manager who could arbitrate is asleep.…