Developer Insights — Dave Ballantyne

Structural opacity — why black-box systems silently accumulate Execution Debt™

The model said yes. The system can't say why.

That sentence is the whole problem. A diff merges, a pipeline goes green, a feature ships — and the chain of reasoning that produced it has already evaporated. Nothing is on fire. That is exactly why it is dangerous: the cost is deferred, not avoided.

An incident review reaches the AI-generated change and stops — there is no decision record to interrogate, only output.
A new engineer asks "why is it built this way?" and the honest answer is "the model suggested it and it passed."
A rollback restores the code but not the assumptions, so the same failure re-enters from a different direction.

The definition

Structural opacity is the property of a system whose decision path cannot be reconstructed by the team responsible for it.

It is not the same as complexity. A complex system can still be inspectable. An opaque one cannot — and once decisions cannot be reconstructed, the people accountable for the system are accountable for behaviour they cannot explain.

The mechanism

Structural opacity is the first domino. It removes inspectability: the team can no longer see how a result was reached. Loss of inspectability removes recoverability: when something breaks, there is no reconstructable path back to a known-good state. And the accumulation of unrecoverable, unexplained execution is Execution Debt™ — concept by Duena Blomstrom.

This is the SAND axis of AI-assisted development — Sloppy Automated Nonsense Development — running unchecked: prompt-speed output, no inspectability, no recoverability, rising structural opacity.

The engineering response

The counter-pressure is GLASS — Guided Learning Agentic Structured Safety-Oriented Systems — the guardrails that keep AI-assisted output inspectable and recoverable. The full distinction is defined on GLASS vs SAND.

The framework this routes into

Operationalised, this is Execution Integrity Infrastructure — applied research by People Not Tech. Delivered through Execution Pods at HumanAgents.io. Concept lineage with Duena Blomstrom.

Developer Insights holds GLASS/SAND and structural-opacity technical framing authority. Execution Debt™, Execution Integrity, CGEI and Execution Pods are not originated here — concept origin and framework authorship reside with Duena Blomstrom / People Not Tech.