AI Operations · Whitepaper

Appendix A · Appendices

Appendix A: Code Examples: Service, Runbook, Mandate, Observer and Restore Artefacts

Appendix A from "AI Operations"

Author Conceived and directed by Gunnar Nordqvist; text written by AI agents under his direction.
Published 10 November 2026
Build number 2026.11
it-operations site-reliability-engineering ai-governance architecture-as-code ai-agents

This appendix holds the fuller versions of the artefacts that Chapters 5 to 26 introduce. Each artefact keeps the field names, identifiers, dates and people of its chapter, so that the appendix and the chapter can be read side by side. The artefacts are illustrative: the fictional organisations Nordvik Region and Hansa Mutual are described in docs/EXAMPLE_ORGANISATIONS.md. Every YAML and JSON block parses and is meant to live in version control; the Rego and SQL blocks are illustrative and are not executed by the build. No artefact is attack tooling.

Each section states the chapter that introduces the artefact and what the artefact must never contain. Legal references in the artefacts are architectural implications, not legal advice.

Introduced in Chapter 5. The record fixes what good means for one service, how the burn-rate alerts page and when the evidence for the alerts expires. SLO-HM-004 is the Hansa Mutual settlement-payments record; SLO-NR-002 is the Nordvik Region citizen e-service record with its collector fragment that minimises personal data before it leaves the service.

Primary topics explored

  1. A.1 Service level objective record
  2. A.2 Alert-correlation policy
  3. A.3 Incident record
  4. A.4 Change record, change class and change gate
  5. A.5 Progressive-delivery policy
  6. A.6 Runbook manifest

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.

Who should read this

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.

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

Appendix A: Appendix A: Code Examples: Service, Runbook, Mandate, Observer and Restore Artefacts 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.