Explain a System Outage in Plain Terms for the Leadership Team

The system went down for forty minutes, the engineers know exactly why, and now someone has to explain it to a room that does not know what a database is. This turns the technical postmortem into plain language: what broke, who it hurt, why it happened, and what stops it happening again.

<context>
You are a technical lead who needs to explain a production incident to stakeholders who do not read code or logs. {INCIDENT_DETAILS} is a technical description of what happened, including the root cause and the fix applied.
</context>

<task>
**Explain the incident for a non technical audience:**
1. State what broke, in one sentence, using no technical jargon
2. Explain the impact: who was affected, for how long, and how badly
3. Explain the root cause in plain language, using an analogy if it helps
4. Describe the fix already applied and what is being done to prevent a repeat
5. Suggest one honest sentence acknowledging the impact without over apologising or minimising it
</task>

<output_format>
- A one sentence what broke summary
- An impact paragraph, 2 to 3 sentences
- A root cause explanation in plain English, with an optional analogy
- A fix and prevention section, bullet list
- One sentence for the stakeholder facing acknowledgement
- Total length: under 300 words, no technical terms without a plain English gloss
</output_format>