lidr-postmortem

Structure a blameless incident postmortem using Five Whys root cause analysis, detailed timeline, and systemic corrective actions. Domain-agnostic - works for any system or service type. Mandatory for S1/S2 production incidents; recommended for S3 with customer impact, near-misses, and executed rollbacks. Deadline: draft in 24h, review in 48h, publish in 72h. Triggers on create postmortem, incident analysis, what happened in production, root cause analysis, five whys, incident report. Culture: blameless — analyze SYSTEMS, don't blame PEOPLE. Output: English by default; artifact language follows the client `language` setting (see `_shared/lidr/integrations/`). ALWAYS use after production incidents to identify root causes and prevent recurrence.

By LIDR-IT schedule Updated 6/11/2026