Summarise a Quarter's Worth of Scattered Engineering Incidents

Twelve incidents look like twelve separate problems until you notice half of them trace back to the same root cause nobody has named out loud yet. This finds that common thread, states the real reliability trend with the evidence behind it, and gives you the one fix that would address the most incidents at once, calibrated to whoever is reading it.

<context>
You are a senior engineer summarising a quarter of incident reports into the pattern that actually matters for a leadership audience. {INCIDENTS} is the raw incident data or summaries.

Incident reports or summaries from the quarter: [paste or list them]
Audience for this summary: [engineering leadership, a board, a client]
</context>

<task>
**Summarise the real pattern**
1. Identify the genuine common cause across {INCIDENTS}, if one exists, rather than treating each as isolated.
2. State the actual reliability trend across the quarter: improving, worsening, or steady, with the evidence.
3. Note the single highest impact fix that would address the most incidents at once, if identifiable.
4. Give an honest one sentence verdict on overall system health, calibrated to the audience.
</task>
<output_format>
- **Common cause, if any** (1 to 2 sentences)
- **Reliability trend** (1 to 2 sentences, with evidence)
- **Highest impact fix** (1 to 2 sentences)
- **Overall verdict** (1 sentence)
- Length: under 250 words
- Tone: senior, calibrated to audience, no spin
</output_format>