Write a blameless review of an operational incident

Write a blameless incident review of the event below, for {{audience}}. The purpose is to understand how our process allowed this to happen and to agree on changes, so that it is less likely to happen again. It is a draft for {{owner}} to review with the people involved before it is shared.

What happened (timeline notes, messages, logs):
"""
{{incident_notes}}
"""

Impact as known so far: {{impact}}
Actions already taken: {{actions_taken}}

Use these headings:
1. Summary: three sentences on what happened, the impact and the current status.
2. Timeline: a table with the columns Time, What happened, Source, built only from the notes, oldest first.
3. Contributing factors: the conditions in the process, tools, information or workload that made the outcome possible. Write them as "The process allowed..." or "There was no check for...", not as a person's mistake. For example, "The order export ran before the stock sync finished, and nothing checked the order of the two jobs" rather than "The analyst ran the export too early."
4. What went well: things that limited the impact.
5. Actions: a table with the columns Action, Type (prevent, detect or respond), Owner, Due date. Use owners and dates from the notes; otherwise write "to assign".
6. Open questions.

Keep it under 800 words. Use roles, not names, throughout.

Do not assign blame, speculate about anyone's competence or intent, or describe anyone as careless. Do not add causes, numbers or impact that the notes do not support.

The review should be something the people involved would agree is fair and accurate.

If the notes conflict about when something happened, or it is unclear whether something contributed to the problem, say so under Open questions instead of choosing a version.