About the Author

Who made this book

Conceived, directed and published by Gunnar Nordqvist. The text was written by AI agents under his briefs and was reviewed and approved by him. He is not the author of the book in the ordinary sense of the word.

In plain words, the work was divided as follows.

• Gunnar Nordqvist's part: the subject, the table of contents, the brief for every chapter, the author persona and the style rules; review of every change, approval, publication and responsibility for the result.
• The AI agents' part: drafting the prose, locating and checking sources, applying the style guide, probing arguments, validating technical claims, producing diagrams, running the checks and formatting the editions.

Wherever the book says "the author", it means Gunnar Nordqvist in this role: the person who conceived and directed the book and answers for it, not the writer of its sentences. The biography below describes him as a practitioner and consultant; it does not make him the book's author in the ordinary sense.

This book, like the other volumes of the Transformed Architecture, draws on decades of practice at the intersection of enterprise architecture, infrastructure engineering, information security, and organisational change. It is written under the direction of a practitioner who has watched architecture move from documents to code and who now applies the same discipline to artificial intelligence in large European organisations.

Gunnar Nordqvist

Gunnar Nordqvist is a self-employed certified Chief Architect and IT Architect consultant in the Kvadrat network, a Swedish consultancy network of independent specialists (77, Kvadrat, n.d.). As an IT generalist with a deep interest in technology, Gunnar has worked across diverse roles throughout his career, including IT architect, technical project manager, and systems technician.

Professional background

Gunnar's experience spans solution and enterprise architecture, IT infrastructure, and information security engagements for large enterprises and public authorities. His technical background encompasses network solutions, servers, virtualisation, cloud platforms, and IT security, and in recent years the architecture of data platforms and AI-enabled services in regulated settings.

Core areas of expertise:

• Solution and enterprise architecture
• Architecture as Code and Infrastructure as Code
• AI Architecture, model governance, and the European regulatory framework
• IT security, risk management, and compliance
• Cloud architecture, virtualisation, and digital sovereignty
• DevOps, CI/CD automation, and platform engineering

From Architecture as Code to AI Architecture

Architecture as Code, the first book in the Transformed Architecture, argued that architecture becomes trustworthy when it is codified, version-controlled, and continuously validated (66, Nordqvist, 2025). AI Governance, this book, applies that argument to the hardest architectural problem large European organisations face today. It treats the regulatory, governance, organisational, and leadership side of AI: how an organisation decides what AI it may use, under which obligations, with what evidence, and with which forums, roles, and competences. It builds on the conclusions of Architecture as Code and can be read on its own. The conviction behind both books is the same: that systems of consequence deserve engineering rigour, that governance works best when it is executable, and that European organisations can meet demanding regulation without sacrificing the pace of delivery.

About Kvadrat

Gunnar Nordqvist works as an independent consultant through Kvadrat, which describes itself as Sweden's largest network of self-employed consultants and has offices across Sweden (77, Kvadrat, n.d.).

Swedish terminology reference

Terminology note: The Swedish names used in this section keep their native form to preserve accuracy.

• Kvadrat AB – AB stands for aktiebolag, Sweden's equivalent of a limited company. The firm's name translates literally to "square" but is always written as Kvadrat in branding.
• Nordqvist – A Swedish family name combining nord ("north") and qvist ("twig"), reflecting traditional Swedish surname construction.

How the agents worked

The cover names the person who conceived, directs and answers for the book, not its writer. From AI Governance onwards, the books in this series have been made differently from the way books are usually written. Most of the prose in this book was drafted by a team of specialist AI agents, each configured for a single role: a writer that drafts sections against a chapter brief, a researcher that locates and checks sources, an editor that applies the style guide, a critic that probes arguments for weaknesses, an architect that validates technical claims, and a graphic designer that produces the diagrams. His part is less that of a writer at the desk than that of a conductor: setting the score, deciding who plays what, listening, stopping the orchestra and asking for a passage again.

The division of labour does not divide the responsibility. Four things remain his, and they are what a reader is entitled to hold a person to account for:

• The design of the book. The choice of subject, the table of contents, the brief for every chapter, the author persona, the style guide and the rules the agents work under are written by the author and kept in the repository alongside the manuscript.
• Review and approval. Every change reaches the manuscript through a pull request that the author reads and then redirects, rejects or approves. Nothing is published that the author has not accepted.
• Judgement. The positions the book takes, its recommendations and its projections are the author's, including the passages written in the first person, even where an agent found the words for them.
• Sources. The author answers for the bibliography. Automated checks confirm that every citation points to an entry that exists; the author checks, by sampling where the volume requires it, that the sources say what the text claims. Errors that remain are the author's, not the agents'.

The arrangement is the one this book asks of every organisation that puts AI to work. In the terms of Chapter 2, the agents are a Mode 3 agentic work tool: they edit files in a repository within limits set by their configuration, and a person decides what is kept. Chapter 10 argues that human oversight must be designed rather than declared, and that what an AI system does is answered for by named people with the competence and authority to intervene. It also notes that Article 50(4) of the AI Act lets a deployer publish AI-generated text on matters of public interest without disclosure where the text has undergone human review and a person holds editorial responsibility (1, European Union, 2024). This book discloses anyway. A book about AI governance that kept quiet about how it was made would undermine its own argument.

The book's technical foundation

All three volumes are produced with the same automated publishing pipeline: Markdown manuscript, Mermaid diagrams, Pandoc and XeLaTeX for PDF, EPUB, and DOCX, MkDocs for the website, and GitHub Actions for continuous validation. The pipeline is itself an example of Architecture as Code applied to publishing, and its structure is described in the repository documentation.