Runbook Generator

Create operator-ready procedures from evidence. Never invent commands, account names, URLs, thresholds, rollback behavior, or escalation contacts.

Required Inputs

Collect before writing:

• service and environment in scope
• repository configuration and deployment manifests
• current platform/provider documentation
• dependency and data-store topology
• observability links and known-good health signals
• change authority, approval boundary, and escalation owner
• recovery objectives when relevant: RTO, RPO, and maximum tolerated impact

If any production-critical input is unavailable, mark it TBD — owner required instead of supplying a plausible value.