This section lists the sources cited throughout the book. The numbered source index, ordered by source number, is the canonical bibliography: every inline citation of the form (N, author or organisation, year) links to the entry with that number. The index is grouped by category so that readers can locate European legislation, frameworks, incident reports, research on software development, AI-assisted coding, security and work, and practitioner literature quickly.
The bibliography was seeded from the entries of AI Leader (Book 11) and the series entries, with a small number of entries added for the topics of the developer role (Sources 233 to 248). Every seeded entry was opened and checked against the primary text or a bibliographic record in the earlier volume; the entries added for this book were checked against the primary page on 2026-11-11. The categories for software engineering evidence, developer productivity, the secure software supply chain, software law, intellectual property and open source, developer skills and public-sector software are filled by the chapters that need them. Sources added while this book is drafted are written in the reserved range of the chapter that cites them and verified before release, and sources that no chapter cites are removed before the book is merged.
Inline citations give the source number, the author or organisation, and the year, for example (9, MITRE, n.d.), and link to the entry here. Where an author is named in the sentence, the citation carries the year. Each chapter closes with a ## Sources section that lists the works it cites, using the same numbering as this bibliography. New sources are appended to the appropriate category with the next free number; existing numbers are never reused.
Primary topics explored
- Numbered source index
- How to cite
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
References: References and Sources 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.