Picture a meeting room in Hamburg at Hansa Mutual, the mutual insurance group that runs through this book as an illustration, on a day in the first quarter of 2027, in the scenario that Chapter 18 tells. On the table is the first draft of a post-mortem. The subject is a drill, not an outage: the group's IT-operations agent, software that executes pre-approved operations with write access to production under an identity of its own, is to be stopped on command within five minutes. It takes seventeen. The draft's title names the agent. Its findings say that the agent's credentials, valid for fifteen minutes, outlived the stop, and that the agent is therefore not fit for the autonomy it was given. The recommendation is to tighten the agent.
The second draft, written a week later after the platform team has replayed the logs minute by minute, keeps every one of those facts and reaches a different finding. The fifteen-minute credentials explain part of the delay, as the first draft said. The rest is the route. The canary alert reaches a duty analyst in the security operations centre who does not hold the decision and has no mandate to apply the deny rule, the stop that sits at the policy decision point outside the agent, so the stop waits for someone who does (The Transformed Security Architect, Chapters 10 and 25) (6, Nordqvist, 2026). The record that governs the agent names who owns it; it does not name who is to decide, inside a five-minute budget, that the stop be made. The finding of the second draft is one sentence long: nobody has been named to decide the time to stop.
Both drafts are illustrative: Hansa Mutual is fictional, and so is the drill. The second draft is the harder one to write: it finds nothing wrong with anyone and something missing from the design. On 31 March 2027, in the scenario, the executive board receives the drill as a failure and takes the decision right over every agent with write access to production for itself. The agent's credentials are cut to five minutes. The agent is not changed.
Primary topics explored
- The questions
- The instinct
- The evidence
- The picture corrected
- The rule of thumb
- What to do
About Landscape
Landscape is a companion to The Transformed Architecture. It examines what happens when artificial intelligence takes the manager's chair: algorithmic management of direction, evaluation, consequence, development and care, the effects on people, the management of AI agents, Europe's legal answer, and how to design an accountable AI boss, 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 and The Transformed Security Architect.
Executives, line managers, HR and people leaders, works councils and trade unions, public employers, architects and AI governance leads, data protection and legal officers, procurement and programme leaders, and risk, compliance and audit.
Continue with the full chapter
Chapter 13: The Blame Instinct: When Nobody Designed Who Decides in Landscape gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “The Instincts” and is one of 26 drawn from the manuscript.