Postmortem Action-Item Pre-Send Gate for Incident Leads

Incident leads at 50-300 engineer SaaS companies run postmortems where the team commits to action items meant to prevent recurrence. Lived reality: most action items are symptom-treating ('add more logging'), under-specified ('improve runbook'), or correct-in-spirit but lacking falsifiers. 60-90 days later, similar incidents recur and the lead has no signal on which classes of action items actually held. The product is a pre-commit gate: before each action item is locked into the postmortem doc, the lead pastes it in and the gate runs an adversarial interrogation — what would falsify 'this prevents recurrence', what independent signal proves root cause vs. symptom, what is the 30/60/90-day check, what specific incident class would refute it. Manual entry per item; no doc scraping. The lead's chosen resolution events are then tracked against incident-tracker ground truth. AE's adversarial multi-model debate runs the interrogation; the ten-module behavioral contracts shape each round; PagerDuty/Incident.io/Jira hold the truth.

Every postmortem tool tracks action items after they're written; AE gates them before commit, turning unfalsifiable promises into graded resolution events using machinery incumbents can't replicate.

Still in evaluation (phase: ranked). No verdict yet.