# Postmortem: # The controller starts one after any revert or S1 fix of a merged crew PR: when that fix's brief goes out, or at the latest when its READY arrives. The controller or a lane it names writes it to `reports/postmortem-.md` in the controller's drive and links it from the fixing PR's body by that path. A revert records what was wrong with the code; this records why everyone who passed it believed it was right. Write it from the record, not from memory and not from the diff alone. Split the reading across read-only subagents when it is long, and keep each section to a table or one short paragraph. ## What broke ## How it was found ## Impact ## Timeline | Time (UTC) | Event | Source | |---|---|---| |