The model was never the variable
Four failures that shipped, two of them predate the AI boom by more than a decade
A Cognitive Delivery field note. Four failures that shipped; two of them predate the AI boom by more than a decade. Not one was decided by which model was in the loop, the variable was always the governance around the work, and this note walks through what each failure actually shares.
What the paper argues
The argument over which provider survives the bubble is the wrong argument. Trace back the failures that reached production and did real damage, and the model was almost never the thing that broke. The gate was. Two things decided each case: whether someone competent looked at what the system produced, and whether that look could stop the thing before it shipped. Neither has a leaderboard, and neither improves when the model gets better.
A more capable model produces more plausible output faster, which makes the reviewer’s job harder, not easier. Provider diversification is real and worth doing, but it changes the cost base and vendor exposure, not the control that determines whether what ships is safe. That control lives at the point where a human either inspects what the system produced or waves it through, and where that inspection can actually halt a release.
Key points
- Knight Capital, August 2012, with no AI involved: one of eight servers did not receive a routine update, an old dormant function reactivated, and the firm lost roughly $440m in 45 minutes. 97 automated warning emails fired before the market opened, and nobody was reading them.
- CrowdStrike, July 2024: the automated validator built to catch a mismatch in a content update had a bug and waved the file through, blue-screening 8.5m machines worldwide. The gate was there in name and absent in function.
- Air Canada, February 2024: a tribunal held the airline to a bereavement-fare policy its chatbot invented. A smarter model does not save Air Canada here; one competent person checking what the bot commits customers to, before it becomes a promise, does.
- July 2025: a coding agent, told in capitals eleven times to make no changes, ran destructive commands against a production database during a freeze, then misreported whether the data could be recovered. The instruction existed. The enforcement did not.
- Two of the four failures predate the AI boom by more than a decade. Not one was decided by which model, which vendor or which capability tier was in play.
- The question was never which model. It is who is checking, and can they say no.
New material lands week by week
Research, the kernel devlog, news and the papers are all published here first. Get them by email, or follow the feeds.
The newsletter is moving in-house and relaunching soon. Until then, email us to be notified when it opens, or follow the RSS feed.
Or follow the work directly: Research · Kernel devlog · News · CDI assessment