Cheap Code, Costly Judgment: A Case Study on Governable Agentic Software Engineering
This paper presents a case study on using AI coding agents in software engineering and develops a process model for governing high-velocity agentic implementation.
Presents a process model for governing high-velocity agentic implementation, which derives controls from failures discovered during the work.
Before reading this…
Applications
- →Software development using AI coding agents
To understand this paper, make sure you know these concepts first:
- Understanding of software engineering conceptsfind papers →
- Familiarity with AI and machine learningfind papers →
Abstract
More Like ThisGenerative AI is shifting software engineering from a practice organized around scarce implementation effort toward one organized around abundant, low-cost code production. This shift changes the central engineering problem: not whether AI can generate useful code, but how engineers organize architectures, tools, evidence, and feedback loops so that AI-mediated development remains inspectable, correctable, and maintainable. We study this problem through a first-person case study: a 12-week development effort in which a single expert software engineer used frontier AI coding agents to build a document accessibility remediation system. The empirical record comprises 88 contemporaneous field notes, 420 KLOC of production code, and 1.16 MLOC of tests, lints, supporting documentation, and agent tooling. From this record, we develop a candidate middle-range theory of governance conversion, expressed as a process model explaining how high-velocity agentic implementation becomes governable. The model explains how agentic implementation velocity surfaces recurring structural failure classes, and how engineering judgment sustains velocity by converting those failures into durable governance mechanisms. In contrast to existing governance models that derive controls from known obligations, governance conversion explains how controls are discovered from failures that become visible only during agentic work. We use our model to make testable predictions and to describe implications for software engineering research and practice.