What Belongs in an Integration Incident Brief
A short structure that keeps post-incident writing honest without dumping logs on stakeholders.
An integration incident brief should answer four questions: what path failed, for how long, what business effect followed, and what changed to restore flow. Everything else is optional appendix material.
Include the first trusted signal, the confirmation signal, and the recovery signal with timestamps. Name the connectors involved and whether payload loss, delay, or duplication occurred. Skip speculative root causes until they are evidenced.
Circulate the brief to owners within two working days while memory is fresh. A late brief becomes archaeology; a timely one becomes shared operational memory.