THE POSTMORTEM — Project Post-Mortem OS Brain
THE POSTMORTEM — Project Post-Mortem OS Brain
For the review that actually changes something. One orchestrator plus ten specialists that rebuild what happened as a dated timeline, separate contributing factors from whoever stood nearest the failure, and produce actions with owners rather than a list of feelings.
Most post-mortems find a person. It is the cheapest available answer and it fixes nothing, because the next person in the same system does the same thing. The timeline script takes events with timestamps and decision points and rebuilds the sequence, marking where information existed somewhere but had not reached the person who needed it. That one distinction — the gap between what was knowable and what was known at the point of decision — accounts for most failures and is almost never in the write-up. Blame is the failure mode this refuses.
timeline_build.py
Builds a dated event and decision timeline, marks each decision with what was knowable at that moment against what was actually known, and surfaces information gaps rather than individuals. Ranks contributing factors by how many decisions each one touched. Every OS Brain in this drop carries its own executable component, so the judgement calls stay with you and the arithmetic stops being a matter of opinion. Runs anywhere Python runs, and the specialists still work on their own if you never open it.
Say it in plain words — it works out the rest
Inside · orchestrator + 10 specialists
Where it refuses to skip ahead
- No conclusions before the timeline — a narrative written first will find the facts that fit it.
- No single root cause — real failures have several contributing factors, and picking one hides the rest.
- No action without an owner and a date — unowned actions are why the same review happens again next year.
- No naming individuals as causes — if the process allowed it, the process is the finding.