Reliability

Reliability engineering, SRE operating models, incident review, and what breaks when code generation outpaces human review.

Decision Lineage

Three vendors use decision lineage for the reasoning behind a system’s conclusion. I use it for the human acceptance nobody records: who generated a change, how deeply it was reviewed, what it can break, and who owns the risk.

Machine-speed code generation flowing into a merge decision hub that carries generator, blast radius and named owner, with one path leading to production release and another to a postmortem

Verification Is Not Accountability

Verification tells you AI-generated code is sound. It cannot tell you who decided to accept the risk. The case for recording decision lineage in the merge path.

Make Accountability a System Property

Accountability for AI-generated code has to be built into the development process, not bolted on after an incident. Three operational shifts, a tooling reality check, and a governance control plane concept.

Accountability and AI-generated code

AI Didn't Break Accountability. It Exposed the Gap.

AI coding tools broke the accountability chain engineering organizations relied on for decades. Developers report 42% of the code they commit is AI-generated, and most haven’t decided who owns the outcome when it fails.