Part VI turns the book's analysis into designs, and this chapter supplies the two artefacts on which the others rest. The Management Decision Record (MDR) records one management decision that AI made or shaped about a person: what the system proposed, who decided, why, what the person was told and how to contest it. The delegation register of management functions, management/delegation-register.yaml, records what has been delegated across the organisation, whether each delegation can still be undone, and where further delegation is frozen. The chapter gives their schema, shows how records arise from normal operation, places them among the book's other artefacts, and answers open question Q3: how a decision made by or with AI is shown to the worker, a works council, a court and a supervisory authority. It concerns all five management functions, with most weight on M3 Consequence, where every decision needs a record, and on M1 Direction and M2 Evaluation, where records are sampled; M4 Development and M5 Care enter through the decisions they touch.
The series has argued for decision records since its first volume. Architecture as Code (Chapter 4) concluded that architectural decisions are kept as short, numbered, immutable records beside the code (F8), and its closing chapter added that an AI-assisted decision without a traceable human rationale should receive a record, written retrospectively if necessary (F14) (30, Nordqvist, 2025). Nygard's original proposal is modest: a title, context, decision, status and consequences, one or two pages, numbered sequentially, with a reversed decision kept and marked superseded (12, Nygard, 2011). AI Platform and Security, Chapter 5, kept that discipline for AI Decision Records, validated them on every pull request and let evidence re-open them (F38) (32, Nordqvist, 2026), and AI Governance, Chapter 11, concluded that evidence is a by-product of delivery rather than something assembled in audit season (F20) (31, Nordqvist, 2026).
An Architecture Decision Record is about a system; a Management Decision Record is about a person. The record is therefore personal data, to be minimised and deleted on time; it has a reader with rights; it is evidence in disputes that may reach a labour court; and its volume is high, so it must be produced by the work rather than written beside it.
Primary topics explored
- Why records
- The Management Decision Record
- Records by operation
- Schema, validation and change
- The delegation profile and the delegation register
- The record set
About AI Boss
AI Boss is Book 7 of 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.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 25: Management Decisions as Records: Decision Records and the Delegation Register in AI Boss gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Designing the Accountable AI Boss” and is one of 37 drawn from the manuscript.