Buddy Postmortem generation

A Postmortem is a doc_type: "postmortem" document that captures the timeline, root cause, and follow-ups for one resolved incident. Buddy can draft a Postmortem directly from the conversation in the incident room, with the timeline and tool calls already cited.

Postmortems use the same versioning and review flow as every other document. See Document management for versions, rollback, and comments.

When to use Buddy for Postmortems

Right after a Bundle is resolved, while the incident room context is still loaded.
When pulling a recent resolved Bundle from list_recent_resolved_bundles and asking for a writeup.
When you want a consistent structure across incidents — pin a template (see Templates).

How it works

Buddy uses the same three write tools described for Runbooks, but with doc_type = "postmortem" and a Postmortem-shaped prompt. Every write goes through the approval flow described in Buddy AI chat.

Tool	What it does
`create_document`	Creates a new Postmortem document.
`update_document_content`	Replaces the whole `content` with a new version.
`patch_document_content`	Edits one block of the Postmortem in place.

A Postmortem is linked to one or more Bundles. The link is recorded in the document's bundle_ids and shows on the Bundle page so responders can find it later. Buddy fills bundle_ids automatically when the Postmortem is drafted from an incident room or a list_recent_resolved_bundles reference.

What goes into the draft

When Buddy drafts a Postmortem, it pulls:

The incident room conversation (the working chat between responders).
Tool call results used during the investigation (for example, MCP queries to GitHub or Datadog).
The Bundle's alert timeline (severity changes, members notified, status transitions).
Related documents already linked from the Bundle.

Buddy never invents facts. If a piece of context is missing (for example, no chat history because the Bundle was resolved manually without using the incident room), Buddy says so in the draft and leaves a placeholder for the human to fill in.

Templates

A Postmortem can be drafted from a Document Template (template_type = "postmortem"). Templates follow the same model as Runbook templates:

name, description — used by Buddy to pick the right one.
content — the Markdown skeleton (typical sections: Summary, Timeline, Root Cause, Impact, Follow-ups).
is_default — at most one default per template type.
Optional team_id — null means Org-wide; otherwise Team-scoped.
Optional path — controls Explorer tree placement.

If no template is selected, Buddy uses the Organization's built-in default Postmortem skeleton.

Status and publication

A Postmortem follows the same status model as all other documents — see Document management → Status lifecycle for the canonical reference (published / unpublished / archived and how the next-version "draft" workflow relates to it).

A common Postmortem flow is: Buddy drafts the document in published status, the team uses inline comments to discuss, then opens a draft version (Create draft version) for the rewrite, and finally publishes the draft to roll forward.

Language

Postmortem content follows the Organization's default_locale. Like Runbooks, Postmortems are read by every responder on the Team, so they use the Org-wide language, not the requester's personal language. See Organization settings for default_locale.

Examples

Draft a Postmortem from a freshly resolved Bundle:

In the incident room of a resolved Bundle, ask Buddy: "Write a postmortem for this incident."
Buddy proposes a draft with sections filled in from the conversation, timeline, and tool results.
The approval card shows the title, doc_type = "postmortem", the linked bundle_ids, and the full Markdown.
Approve to save. The Postmortem is created as version 1.

Draft a Postmortem for an older Bundle from a personal chat:

From the Buddy side panel, ask: "Postmortem for the database alert we had on Tuesday."
Buddy calls list_recent_resolved_bundles to identify the right Bundle.
Buddy calls get_chat_history(bundle_id=...) to pull the incident room conversation.
Buddy proposes a draft and asks for approval before saving.

Buddy AI chat — how the chat session, tools, and approval flow work.
Buddy Runbook generation — the matching feature for procedural runbooks.
Buddy Knowledge Base — how Postmortems are searched during later incidents.
Document management — versions, drafts, rollback, and comments.
Organization settings — post_mortem toggle and default_locale.