Operations Runbook
Write a bounded procedure that a qualified operator can follow under pressure.
- Define purpose, scope, prerequisites, permissions, owner, and stop conditions.
- Use numbered steps with expected result and evidence after meaningful actions.
- Include diagnostics before remediation, escalation triggers, rollback/recovery, and contact/ownership placeholders.
- Label destructive, external, privileged, and irreversible actions explicitly.
- Add a drill/review date and a lightweight change log.
Never hide commands that can delete data, change production, expose secrets, or bypass approvals. A runbook does not authorize its own execution.