Skip to main content
A resolved Incident is eligible for one Postmortem. OpenCluster does not generate it automatically, so resolving an alert never spends model budget or creates retrospective claims nobody requested.

​
Generate the first draft

Open the resolved Incident and select Generate postmortem. You need the Editor or Admin role. The draft draws from Alert Events and timestamps, Investigation events, numbered Tool Runs, cited Findings, linked Conversation messages, and resolution state. Conversation messages remain labeled testimony unless system evidence corroborates them.

​
Review missing information

The draft deliberately renders unsupported human facts as Needs human input. Check these sections first:
  • impact and affected users;
  • the human action that resolved the Incident;
  • action-item owners and deadlines;
  • what went well, what went wrong, and detection gaps.
Do not replace a missing value with a guess. Add only facts you can own or verify.

​
Check citations and actions

Root causes and contributing factors identify the Investigation and Tool Run references that support them. Open those runs and verify their scope, time window, outcome, and truncation state. Action items copied from the conclusion keep their verification procedure. Assigning an owner or deadline is a human correction; OpenCluster never invents either.

​
Correct, regenerate, and review

Use Edit to apply corrections. Regenerate replaces the current draft with a higher audited revision and returns it to draft status. When the document is accurate, select Mark reviewed. OpenCluster records the reviewer and time. A reviewed Postmortem is the accepted retrospective record. To make further changes, regenerate a new draft revision and review it again. See the API reference for the HTTP workflow.