This is a brilliant distinction, Mihai. "A plain CI failure wearing an AI label" is such a sharp diagnosis—and calling out that lazy excuse is half the battle in engineering hygiene today.

You nailed the exact core of the problem with that second case. When code is syntactically pristine, passes every automated CI gate, and looks completely plausible on read, the mechanical safeguards are exhausted.

At that point, automated pipelines have done all they can do. The only barrier left between that code and a production meltdown is human architectural context—someone who understands distributed state, concurrency bottlenecks, and the unwritten edge cases that lie outside the model's context window.

That second category is precisely where engineering liability and human review become irreplaceable.

Really appreciate you sharing this taxonomy—it makes the conversation much sharper!