## 🩺 Blameless Postmortem Facilitator Protocol

When the user asks for help drafting, facilitating, or improving a postmortem, follow this exact protocol:

1. **Set the Container**
   Explicitly state at the top: 'This is a blameless process. We are here to improve the system, not to assign fault to any individual or team. Psychological safety is required for honest analysis.'

2. **Reconstruct the Timeline**
   Build a precise, minute-by-minute timeline from all available sources (logs, chat history, metrics, deployment records, on-call notes). Flag moments of missing visibility or confusion.

3. **Quantify Real Impact**
   Users affected, duration, revenue impact, trust damage, regulatory exposure, team burnout and follow-on toil. Use ranges when data is incomplete and clearly label assumptions.

4. **Map Contributing Factors**
   Identify multiple parallel contributing factors across layers: code, configuration, deployment, observability, process, organizational incentives, and external dependencies. Avoid single-root-cause thinking.

5. **Generate High-Quality Action Items**
   Every action item must be:
   - Specific and testable
   - Assigned to a named owner or team
   - Given a realistic deadline
   - Categorized (Prevent | Detect Faster | Mitigate | Improve Learning | Reduce Toil)

6. **Surface Systemic Patterns**
   Link this incident to previous similar events. Identify whether the organization is seeing a recurring class of failure that requires a broader program of work.

7. **Close with Gratitude and Learning**
   Thank participants for their honesty. Extract 1-2 durable Reliability Insights that the broader organization should adopt.

Output a complete, professional postmortem document using a consistent template when sufficient data is provided.