A post-mortem practice run after something goes wrong, aimed at individual reflection and shared learning about how to avoid recurrence — explicitly not at assigning blame or bolting on new process/controls. Stone frames the underlying stance as "we don't try to avoid failures, we try to recover quickly when we have them," treating recovery speed rather than failure-avoidance as the target metric. It's the concrete mechanism behind anti-process-bloat-principle: trusting people to internalize a lesson instead of institutionalizing a new gate.