This chapter fixes the frame that the rest of the book uses, in the way Chapter 4 of AI Operations fixed the operations loop and Chapter 4 of AI Leader the leadership loop. It defines the five developer functions, D1 Frame, D2 Design, D3 Build, D4 Prove and D5 Steward; the ten classes of development work; the delegation ladder, which sets how far AI may take part in each class, and the five prohibitions that keep Level 4 Autonomous out of work where it does not belong; and the stewardship principle: AI may draft, generate, refactor and, within a mandate, execute, but may not own. It then states the corollary that the test oracle must be independent of the generator, sets the rule for claims about productivity, security and competence, relates the frame to the instruments that assign duties for software, and ends with the delegation profile DLG-*. Chapters 8, 9, 12 and 14 apply the stewardship principle in full.
The definition is the book's own design; the sources cited here support its parts, never the whole.
Six conclusions of the earlier volumes carry the frame. AI Governance, Chapter 2, concluded that the usage mode, not the brand, sets the governance; this book keeps that vocabulary from Mode 0 Ambient AI to Mode 5 Autonomous production agents (162, Nordqvist, 2026). AI Red Team, Chapter 6, defined five autonomy levels set per action from reversibility and blast radius, with the most important line between Level 2 Supervised and Level 3 Bounded, where actions begin without per-action approval (164, Nordqvist, 2026). AI Blue, Chapter 4, made the delegation profile an artefact in which an unlisted action is undelegated (168, Nordqvist, 2026). AI Purple, Chapters 4 and 15, and AI Operations, Chapters 4 and 17, added the independence principle and the observer principle: what verifies an action must not share the failure modes of what performed it (169, Nordqvist, 2026); (170, Nordqvist, 2026). AI Boss, Chapter 4, concluded that AI may direct work but may not, on its own, decide about people (167, Nordqvist, 2026). AI Leader, Chapters 4 and 12, applied the ladder to leadership decisions and stated the answerability principle: AI may inform, draft, prepare and, within a mandate, execute, but may not answer, and a named leader passes the tests Name, Explain and Reach (174, Nordqvist, 2026).
Primary topics explored
- What this chapter builds on
- The loop in one picture
- Five functions
- Classes of development work
- The delegation ladder
- The Level 4 prohibitions
About AI Developer
AI Developer is Book 12 of The Transformed Architecture. It takes the developer as its subject and asks what happens when AI is used broadly in software development: the five developer functions (frame, design, build, prove, steward), the delegation ladder and the Level 4 prohibitions, the stewardship principle (name, understand, revert), verification as the scarce skill, the junior pipeline, adoption and productivity as claims that need evidence, regulation (the AI Act, the Cyber Resilience Act, the Product Liability Directive, NIS 2, DORA, the GDPR), ethics, intellectual property and sovereignty in the toolchain, and the developer as a person, for European enterprises and public authorities.
It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team, AI Threat, The Transformed Security Architect, AI Boss, AI Blue, AI Purple, AI Operations and AI Leader.
developers at every level, tech leads and engineering managers, architects, platform engineers, site reliability engineers and testers, product owners and designers, leaders who decide on developer tooling, heads of public-sector IT and procurement, works councils and unions, educators, and supervisors and auditors.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 4: The Developer Loop Defined: Five Functions, Delegation Ladder and Stewardship in AI Developer gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “The Developer Role in Question” and is one of 37 drawn from the manuscript.