The Consequence Library · How records are made and graded
A deployment error left dormant code active on one of eight servers in Knight Capital's order routing system. On the morning of 1 August 2012 the system sent millions of unintended orders into the market over about 45 minutes, producing a loss of roughly $440 million and effectively ending the firm's independence.
Evidence caveat. Analog record. Knight Capital predates large language models and involved no AI system. It is included because the fail-stop and machine-speed authority failures it documents are the same class this library records, and because its evidentiary quality is a benchmark for what a public record of these failures can look like.
What happened
Knight deployed new code to eight servers but the deployment was incomplete on one. Repurposed flags activated dormant functionality on that server, which began generating erroneous orders when the market opened. The SEC's subsequent administrative order documented that Knight had no procedure requiring a second technician to review deployments, no written procedures for the code that failed, and no effective controls to halt the erroneous order flow. Staff received system alerts before the market opened but the messages were not treated as requiring action. During the event, personnel attempted responses that in one case made the flow worse. The firm was recapitalised and later acquired. The SEC charged Knight with violating the Market Access Rule and imposed a $12 million penalty.
Where control failed
There was no working stop. The controls that failed were, in the SEC's account, the absence of deployment verification, the absence of written procedures, and the absence of a mechanism able to halt the order flow once it began. Pre-market alerts existed and did not reach anyone who acted on them, which is the same nominal-control pattern that recurs throughout this library.
The authority question
The erroneous orders were generated automatically following a deployment failure. The SEC record documents deficiencies in deployment review and in mechanisms for stopping the resulting order flow once it began.
What could be proven afterward
The SEC administrative order provides a detailed public reconstruction of the deployment, alerts, trading activity and control deficiencies. It provides a useful historical comparison for evaluating the quality of evidence available after machine-speed automated events.
Control state, before and after
Before the consequence
No second-technician review of deployments. No written procedures for the affected code. No mechanism to halt erroneous order flow. Pre-market alerts with no defined response.
After the consequence
SEC order for violating the Market Access Rule, $12 million penalty. Firm recapitalised and subsequently acquired.
Sources
- Primary: SEC, Administrative Proceeding File No. 3-15570, In the Matter of Knight Capital Americas LLC, 16 Oct 2013 · https://www.sec.gov/litigation/admin/2013/34-70694.pdf
Record history
Published 16 August 2026. Load-bearing facts re-verified against the cited sources on 16 August 2026. Corrections and material changes are appended here with their dates. To report an error in this record, write to hello@regulayer.com with the record slug and the source you believe is authoritative.
This record describes what sources establish about a consequence and the control state around it. It separates confirmed fact from source-stated cause and from architectural analysis, and it makes no claim that any control or product would have prevented the outcome. Gap codes identify a failure class, not a remedy.