The Transformed Security Architect · Whitepaper

Chapter 15 · The Architect's AI Team

Keeping the Craft

Deskilling, Judgement and the Architect Who Still Can

Author Conceived and directed by Gunnar Nordqvist; text written by AI agents under his direction.
Published 6 November 2026
Build number 2026.11
security-architecture security-architect-role architecture-as-code ai-agents competence
Figure 15.1: The craft-keeping cycle, feeding competence records that pace agent autonomy.
Figure 15.1: The craft-keeping cycle, feeding competence records that pace agent autonomy.

The three preceding chapters gave the security architect an AI team: assistants in Modes 1 to 3 (Chapter 12), an agent team under a mandate manifest (Chapter 13), and a review protocol that does not trust the proposer (Chapter 14). This chapter deals with the condition on which all three depend: an architect who can no longer do the craft without AI cannot verify what AI proposes, because verification needs the knowledge that authorship used to exercise. The chapter concerns Shift 4, from sole author to conductor of an AI team, and argues that the shift is safe only if the conductor can still play. It sets out the evidence on deskilling, defines judgement, and prescribes the practices that keep it.

The chapter builds on the conclusion of AI Red Team, Chapters 6 and 15, that skills erode when AI does most of the work while supervision and the degraded mode after a stop still need them (164, Nordqvist, 2026), and on the conclusion of AI Threat, Chapters 6 and 14, that automating junior work removes the route by which experts are made (165, Nordqvist, 2026).

Lisanne Bainbridge observed in 1983 that automation takes over the tasks that are easy to specify and leaves people to monitor the system and take over when it fails, and that both remaining tasks need skills the automation itself erodes (104, Bainbridge, 1983). AI Threat, Chapter 14, applied her ironies to claims handling and casework (165, Nordqvist, 2026). Applied to the security architect, they take a sharper form, for three reasons.

Primary topics explored

  1. The ironies of automation, again
  2. What the evidence shows
  3. What judgement is
  4. Deliberate practice for architects
  5. No-AI exercises and seeded-error drills
  6. Mentoring when junior work is automated

About The Transformed Security Architect

The Transformed Security Architect is Book 6 of The Transformed Architecture. It describes how the security architect role is transformed when architecture is code, when AI drafts and acts, and when adversaries move at machine speed: the craft, the architect's own AI team, the role in the organisation, the competences and the career, for European enterprises and public authorities.

It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team and AI Threat.

Who should read this

Security architects, CISOs and heads of security architecture, enterprise, solution and AI architects, engineering leads, competence and hiring leads, procurement and programme leaders, and risk, compliance and audit.

Portrait of Gunnar Nordqvist

Gunnar Nordqvist

Conceived, directed and published the books of The Transformed Architecture.

Continue with the full chapter

Read the full chapter online

Chapter 15: Keeping the Craft: Deskilling, Judgement and the Architect Who Still Can in The Transformed Security Architect gives the detailed explanations, practical examples and implementation patterns behind this summary.

This whitepaper belongs to “The Architect's AI Team” and is one of 31 drawn from the manuscript.