deploy-pipeline-runbooklisted

# Deploy Pipeline Runbook This is a trust-sensitive runbook for multi-system deployments. Every write or promotion action requires explicit human approval. ## When to Use - A release spans multiple systems or vendors (billing, database, app, notifications). - Order of operations matters and rollback must be planned before execution starts. - A failed step in one system could corrupt state in a downstream system. ## Core Rules - Inspect current state before each external step. - Dry-run whenever the target system supports it. - Show side effects before asking for approval — never surprise. - Require explicit approval before every write, promotion, or announcement. - Define the rollback path before the first irreversible step. ## Runbook Structure ### 1. Preparation - List every system touched. - State the exact intended change per system (e.g., "bump subscription plan from X to Y in billing API"). - Confirm credentials, access paths, and required permissions. - Identify which steps are reversible and which are not. ### 2. Sequence the rollout 1. Config or billing prerequisites. 2. Schema migrations or data backfills. 3. Application deploy or feature promotion. 4. Smoke checks and health validation. 5. Stakeholder notifications. ### 3. Approval checkpoint (required before every write) Use this exact format: ``` NEXT ACTION: [exact command or API call] SYSTEM: [target system / environment] SIDE EFFECTS: [what changes, what is created, what is sent] IRREVERSIBLE: yes/no