Each party did a different part of the work. Gunnar Nordqvist's part was the design and the responsibility: the subject, the table of contents, the brief for every chapter, the author persona and the style rules the agents work under, the review of every change, the approval of what is published, and the responsibility for the result. The part of the AI agents was the execution: drafting the prose, checking sources and consistency, applying the style guide, producing the diagrams and formatting the editions. Wherever this book says "the author", it means Gunnar Nordqvist in that role, as the person who conceived and directed the book and answers for it, not as the person who wrote its sentences.
The way of working is described further in the section "How this book was made" below.
This book, like the other volumes of The Transformed Architecture, 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, draws on decades of practice at the intersection of enterprise architecture, infrastructure engineering, information security, and organisational change. The book is conceived from the perspective of a practitioner, Gunnar Nordqvist, who has watched architecture move from documents to code and who has applied the same discipline to artificial intelligence and, in this book, to the way software is framed, built, proven and owned when AI is used broadly across large European organisations.
Primary topics explored
- Who made this book
- Gunnar Nordqvist
- The series
- About Kvadrat
- Swedish terminology reference
- How this book was made
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.
Continue with the full chapter
About the Author: About the Author in AI Developer gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Appendices” and is one of 37 drawn from the manuscript.