Parts II and III described what operators do with AI in each function and how the AI services themselves are operated. This chapter turns to the operator's own AI as a team: a small set of narrow agents that observe, triage, review change, run runbooks, plan capacity and write the record, each under a written mandate and each contained by controls that do not depend on how the agent behaves. The chapter concerns all five functions: O1 Observe, O2 Diagnose, O3 Change, O4 Restore and O5 Sustain, because a team of this kind holds a role in each of them. Its subject is the design of the team: which roles exist, how an agent's skills are kept as versioned files, what a mandate manifest says, how an agent is contained and stopped, what it may remember and call, and how it earns, keeps and loses a degree of delegation.
The chapter applies a pattern that the series has built up over several volumes. An agent team works under a written mandate at an autonomy level matched to reversibility, and the person who conducts it remains the accountable verifier of what it proposes (The Transformed Security Architect, Chapter 13, F75). Containment is judged by what an agent can reach however it behaves, with task-scoped credentials, default-deny egress, control artefacts outside the agent's reach and a stop path outside the system it stops (AI Platform and Security, Chapter 19, F45) (297, Nordqvist, 2026). Operations adds two things to the pattern. The agents' credentials are among the broadest in the estate, because restarting, scaling, reconfiguring and rolling back production is what operators are for. And operations has decades of experience of what automated action does to the people who supervise it, so the design must say who still holds the skill to take over. Chapter 17 treats the observer principle in full and Chapter 18 the defence of the agents against attack. This chapter fixes the structure on which both rest.
The table gives the six roles in the figure. The policy decision point, the token issuer and mandate store, the kill switch and the independent probes sit outside all six.
Primary topics explored
- Why a team of narrow agents
- Roles of an operations agent team
- Skills as versioned files
- The mandate manifest
- Containment
- Memory and tools
About AI Operations
AI Operations is Book 10 of The Transformed Architecture. It takes IT operations as its subject and asks what happens when AI takes part in it: the five operations functions (observe, diagnose, change, restore, sustain), the autonomy budget and the Level 4 prohibitions, the observer principle, resilience as a claim that needs evidence, operating AI systems, the operator's own AI as Tier 0 and how to defend it, operating models, decision rights, regulation (DORA, NIS 2, the AI Act), 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, AI Blue and AI Purple.
CIOs and heads of IT operations, SRE and platform leads, incident commanders and on-call engineers, service-desk and service-management leads, FinOps and capacity managers, architects, CISOs and heads of resilience and third-party risk, boards and management bodies, procurement and vendor managers, supervisors and auditors, works councils and unions, data protection officers, and public-sector leaders.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 16: An AI Agent Team for Operations: Skills, Mandates and Containment in AI Operations gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “The Operator's Own AI” and is one of 35 drawn from the manuscript.