Each party did a different part of the work. Gunnar Nordqvist's part was the design and the responsibility: the subject, the table of contents, the brief for every chapter, the author persona and the style rules the agents work under, the review of every change, the approval of what is published, and the responsibility for the result. The part of the AI agents was the execution: drafting the prose, checking sources and consistency, applying the style guide, producing the diagrams and formatting the editions. Wherever this book says "the author", it means Gunnar Nordqvist in that role, as the person who conceived and directed the book and answers for it, not as the person who wrote its sentences.
The way of working is described further in the section "How this book was made" below.
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, AI Blue and AI Purple, draws on decades of practice at the intersection of enterprise architecture, infrastructure engineering, information security, and organisational change. The book is conceived from the perspective of a practitioner, Gunnar Nordqvist, 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 IT operations is carried out and verified when AI takes part in observing, diagnosing, changing and restoring the services of large European organisations.
Primary topics explored
- Who made this book
- Gunnar Nordqvist
- The series
- About Kvadrat
- Swedish terminology reference
- How this book was made
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.
Continue with the full chapter
About the Author: About the Author in AI Operations gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Appendices” and is one of 35 drawn from the manuscript.