Part I has asked what the loop between the red team and the blue team did before AI joined it (Chapter 2) and why its traditional rhythm no longer fits (Chapter 3). This chapter defines the loop the rest of the book uses. It fixes five stages, the record each produces, the rule by which a finding is closed, the ceiling of delegation to AI at each stage, the independence principle that governs every check with AI on both sides, and the roles that hold the loop. Two definitions in this chapter are used unchanged by every later chapter: the closure rule (a person signs every closure) and the independence principle (five kinds of separation, one rule between roles, three proofs). It concerns all five stages by name: P1 Target, P2 Emulate, P3 Observe, P4 Improve and P5 Verify. Parts II to V take the stages one by one; this chapter is the definition they refer back to.
The definition is the book's own design. It builds on observable practice: the five record states of AI Red Team, Chapter 26, the blue team's half of the loop in AI Blue, Chapter 11, and the threat-led testing frameworks of European supervisors. The ceilings of delegation are the book's own recommendation, and the chapter says so where it makes them.
An exercise produces a report. A report records that a technique was tried, what the defence saw and what it did not. A report is also the point at which most exercises end: the testers leave, the findings enter a backlog, and the next evidence about whether anything changed arrives a year later, from the next test. The earlier volumes made the same observation from two sides. AI Red Team, Chapter 26, distinguished a debrief from a loop by a fixed sequence of states and one exit condition (90, Nordqvist, 2026). AI Blue, Chapter 11, put the same point as a difference between a report, which records that a technique was missed, and a loop, which leaves behind a test that it will not be missed again and the date on which that was last shown (94, Nordqvist, 2026).
Primary topics explored
- Why a loop
- The five stages
- The records
- The closure rule
- Degrees of delegation per stage
- Independence
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.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 4: The Purple Loop Defined: Five Stages, Evidence and the Independence Principle in AI Purple gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “The Loop in Question” and is one of 33 drawn from the manuscript.