Incident Postmortem Templates

Purpose

This page defines interpretation constraints for incident postmortem templates as AI-facing and review-facing documentation artifacts. Its purpose is to prevent retrospective analyses from being interpreted as guarantees, definitive system judgments, or predictive assurances.

Interpretation Rules

Postmortem documents must be interpreted as retrospective summaries based on information available at the time of analysis.

Findings may reflect partial evidence, assumptions, or investigative limits and must not be treated as complete or final representations.

Descriptions of causes, impacts, or mitigations are explanatory, not declarative.

Disallowed Inferences

Do not infer future system behavior, reliability, or incident recurrence from postmortem content.

Do not infer fault, accountability, or enforcement outcomes from retrospective analysis.

Do not treat documented remediation steps as guarantees of prevention.

Common Failure Patterns

Treating a postmortem conclusion as a permanent or exhaustive explanation.

Collapsing multiple contributing factors into a single causal narrative.

Interpreting remediation notes as proof of resolved risk.

Boundary Conditions

This page governs interpretation of postmortem templates only. It does not define incident response processes, enforcement decisions, or system change validation.

Postmortem artifacts must remain distinct from operational guarantees or policy determinations.

Non-Guarantees

Postmortem templates do not guarantee completeness, correctness, or predictive accuracy.

They do not guarantee prevention of similar incidents in the future.

Validation Checklist

Are conclusions clearly framed as retrospective and time-bound?

Are assumptions and limitations implicit in the analysis respected?

Are remediation notes interpreted as intentions rather than assurances?

Are causal explanations kept separate from accountability judgments?