Developer Insights — Dave Ballantyne

Why AI-assisted development collapses under pressure

Six months ago the system was fast. Now nobody can answer why it does what it does.

PRs merge clean; the same regression reappears two sprints later in a different file.
The model "fixed" the bug; the team can't reproduce the original failure to know if the fix is correct.
The dashboard says progress. Reality says drift.

AI systems fail when coherent local execution detaches from recoverable shared reality.

The mechanism

AI accelerates output along the SAND axis: faster generation, less inspectability, less recoverability, more structural opacity. Without GLASS guardrails — guided, learning, agentic, structured, safety-oriented — coherence at the diff level becomes drift at the system level. Engineers feel it as: "I can ship faster than I can defend what I shipped."

The framework

This is Execution Debt™ — concept by Duena Blomstrom. The applied research surface is Execution Integrity Infrastructure — applied research by People Not Tech, canonical at peoplenottech.com/research/continuity-governed-execution. Operationally it is delivered through Execution Pods — by HumanAgents.io, lineage with Duena Blomstrom.

If your organisation is shipping under those conditions, the Pre-Scan™ at People Not Tech tells you whether execution is real or only visible.

Developer Insights holds GLASS/SAND 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.