Decision Engineering™ — Issue #006
The decision was issued. Nobody could prove what authorised it.
Issue #006 is live.
Two institutions. Two sectors. The same structural absence.
Knight Capital. 1 August 2012. A software deployment to eight production servers. Seven received the correct update. The eighth was missed. When live traffic hit that single un-updated server, a dormant legacy component reactivated via a repurposed configuration flag. Forty-five minutes. $440 million. The institution could not prove what had been authorised, verified, or running at the exact moment decisions entered the market.
Theranos. 2013 to 2016. A clinical deployment before independent validation. Patients received diagnostic results. Clinicians made treatment decisions. No traceable link between each result and the specific machine that produced it. When CMS arrived, the records that would have made the deployment defensible no longer existed in a form that could be verified.
Both failures. One thing in common. A decision was made and executed. The record that would have made it replayable was never built.
Layer 6 is where judgment becomes a recorded act. Or doesn’t. The distance between explainability and replayability is sharpest here — at the moment of commitment.
Three mechanisms. What they are. Why neither institution had them.
Layer 6 of the Decision Integrity Chain™ — Decision.