Conceived, directed and published by Gunnar Nordqvist. The text was written by AI agents under his briefs and was reviewed and approved by him. He is not the author of the book in the ordinary sense of the word.
In plain words, the two parties did different things. Gunnar Nordqvist's part was the subject, the table of contents, the brief for every chapter, the author persona and the style rules, and then the review of every change, the approval of what was published and the responsibility for the result. The agents' part was drafting the prose, running the checks and formatting the book. Elsewhere in this book, "the author" means Gunnar Nordqvist in that role: the person who conceived, directed, approved and answers for the book, not the person who typed its sentences.
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 and AI Blue, draws on decades of practice at the intersection of enterprise architecture, infrastructure engineering, information security, and organisational change. It is directed from the perspective of a practitioner 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 the teams that attack in order to test and the teams that defend learn together when AI joins the loop between them, in large European organisations.
Primary topics explored
- Who made this book
- Gunnar Nordqvist
- About Kvadrat
- Swedish terminology reference
- How this book was made
- The book's technical foundation
About AI Purple
AI Purple is Book 9 of The Transformed Architecture. It takes the loop between the red team and the blue team as its subject and asks what happens when AI sits on both sides of the table: the five stages of the loop (target, emulate, observe, improve, verify), rules of engagement and safe emulation, continuous emulation, the independence principle, coverage as a claim that needs evidence, the loop's own AI and how to defend it, operating models, decision rights, regulation, and the people involved, 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 and AI Blue.
Chief information security officers, heads of security operations, red-team leads, penetration testers, SOC managers, detection engineers, purple-team coordinators and incident commanders, security and AI architects, boards and management bodies, procurement leads, works councils and unions, data protection and audit functions, and public-sector leaders.
Continue with the full chapter
About the Author: About the Author in AI Purple gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Appendices” and is one of 33 drawn from the manuscript.