Skip to content

SOP-008: Post-Incident & Regression Loop ​

Version: 1.0 · Owner: SRE + Developer · Gate: G5

Purpose & scope ​

Close the quality feedback loop: postmortem, mandatory regression artifacts, and updates to spec/ADR when needed.

Roles ​

RoleRACI
SREA — postmortem process
DEVR — regression test PR
ARCHC — ADR updates
POC — spec amendments

Prerequisites ​

  • Sev-1 or Sev-2 incident resolved (SOP-007)
  • Incident ticket with timeline

Procedure ​

  1. Schedule blamesless postmortem — Within 48h for Sev-1; 5 business days for Sev-2.
  2. AI draft postmortem — From ticket + logs + deploy history; human edits all sections.
  3. Identify gaps — Classify: test gap, spec gap, ADR gap, monitoring gap, process gap.
  4. Create action items — Each with owner and due date in ticket.

Mandatory artifacts (by gap type) ​

GapRequired actionDue
Test gapRegression test PR merged48h (Sev-1), 5 days (Sev-2)
Monitoring gapNew alert or baseline update5 days
Spec gapSOP-003 amendment PR5 days
ADR gapSOP-002 new/supersede ADR10 days
Process gapSOP update PR10 days
  1. Regression test — AI drafts from incident; DEV reviews; must fail on reproduced condition pre-fix.
  2. Publish postmortem — Internal wiki + link from Backstage service page.
  3. Verify closure — SRE confirms all action items done before incident closed.

Definition of Done ​

  • [ ] Postmortem published
  • [ ] Regression test merged (Sev-1/2)
  • [ ] Monitoring/spec/ADR actions tracked to completion
  • [ ] Incident ticket closed

Reference template only — no production code. Adapt in your own project.