Engineering Leadership

Writing on leading engineering organisations at scale: accountability, operating models, and how technical decisions reach the business.

Divergence Rate

The divergence rate is how far a compliant, sovereign or on-prem edition runs behind the commercial one: features shipped, the share that arrive late or never, and the lag. The architecture sets it, not the regulation.

Night landscape: a bright stream of releases runs from a campus to a city while a dimmer branch turns off toward a walled complex marked as the sovereign path

The Divergence Tax

A compliance boundary is approved as a certification and operated as a second release train. The cost nobody budgets is the divergence rate, and architecture sets it.

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.

A near-future city at dusk with residential broadband devices, industrial facilities, a telecommunications tower, and a data-centre campus interconnected by glowing network lines — the physical infrastructure layer beneath the AI stack that vertical slices anchor into.

The Slice Underneath the AI Layer

Layer commoditization is now consensus. The harder question is what a defensible AI business looks like afterwards: a vertical slice fusing data and workflow to a device fleet, a jurisdiction, or a regulatory regime.

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.