\cleardoublepage \part{The Architect's AI Team} \setbookpart{The Architect's AI Team}

Part III: The Architect's AI Team

The security architect now works with AI as well as designing for it. This part is about Shift 4, from sole author to conductor of an AI team: what the architect does with assistants and agentic work tools, how an agent team for security architecture is governed, how its proposals are verified, and how the architect keeps the craft on which verification depends. It also shows that Shift 4 rests on the other shifts: the architect's drafts, mandates, oracles and review records are versioned artefacts (Shift 1, from documents to code), and the agent team is safe only inside boundaries that hold whatever it produces (Shift 2, from gatekeeper to boundary designer).

The part takes up an open question that Architecture as Code (Chapter 27) left for the series: version control shows what changed, not whether the reasoning behind the change was sound. When the reviewer depends on the AI that proposed the change, review must be designed rather than assumed. The chapters treat human verification as both the bottleneck and the value of the transformed role.

Chapters in this part:

  • Chapter 12, The Architect's Own Use of AI, covers drafting, research and review in Modes 1 to 3 and what the evidence says about the results.
  • Chapter 13, An AI Agent Team for Security Architecture, governs an agent team under a mandate manifest and containment that does not depend on intent, and shows why a single-architect authority may rightly defer one.
  • Chapter 14, Verifying What AI Proposes, sets out review techniques for soundness and the signals of review that has become a formality.
  • Chapter 15, Keeping the Craft, addresses deskilling, deliberate practice, seeded-error drills and apprenticeship, and paces agent autonomy to the skills available to supervise it.

What you will learn in this part:

  • Where AI helps the architect's own work, where studies found it did not, and how to keep architecture information confidential
  • How to write a mandate manifest for an agent team at an autonomy level matched to reversibility
  • How to verify AI proposals by independent re-derivation, tests as oracle, an adversarial second agent, provenance and sampling
  • How to keep the skills that verification requires

Each chapter shows how its subject differs across the usage modes or the autonomy levels.