titan-postmortem-templatelisted

# Titan Post-Mortem Template ## Why post-mortems matter A titan runs 4-6 hours, dispatches dozens of sub-workers, touches 5+ phases, and emits hundreds of bus events. Without a structured post-mortem, the institutional knowledge from that run evaporates: failure modes that were resolved in the moment never feed back into the next titan's mission, regression signals stay invisible until they resurface, and memory candidates rot in READY-REPORTs that nobody re-reads. The post-mortem is the **bridge from one titan run to the next**. It feeds: - [[titan-evolution-loop]] — lessons become prompt-brain patches - [[intelligence-accumulation]] — memory candidates become canonical memories - [[self-healing-loop]] — failure patterns become induction sidecar triggers ## Where post-mortems live Every titan MUST write its post-mortem to one of these paths (prefer the blueprint folder for source-committed runs): ``` .local/blueprints/<titan-name>/POSTMORTEM.md ← preferred (lives with other artifacts) .local/audits/<titan-name>/POSTMORTEM.md ← use if blueprint folder doesn't exist ``` The file is written by the titan in its REPORT phase, immediately after `READY-REPORT.md`. ## Bus event on completion After writing the post-mortem, publish: ``` topic: claws.<lineage>.titan.<name>.postmortem.written payload: { titan: "<name>", path: ".local/blueprints/<titan-name>/POSTMORTEM.md", score: <N/100>, outcome: "success" | "partial" | "failed", memory_candidate_count: <