Purpose and scope
This is an operating handbook for organizations that build, buy, deploy, oversee, or audit AI agents. It addresses software agents acting in enterprise workflows, including read-only research, drafting, customer service, internal operations, and controlled transactions. Physical robotics and specialized clinical, military, or industrial safety cases require additional domain standards and validation.
The aim is to help a reader answer six practical questions: What is the agent allowed to do? Who owns the result? Which mechanisms constrain it? How are those mechanisms tested? What evidence shows what actually happened? How can the enterprise stop, correct, and recover the workflow?
The book develops The Observability Layer's emphasis on actionable control evidence. It retains traceability to the earlier 112-control compendium through an optional cross-reference index. The 45 handbook practices use a separate H-prefix and are fully explained here; the reader does not need the earlier catalog to use them. E01-E12 name the detailed implementation specifications in chapter 18. These identifiers are local to the handbook and are not regulatory clause numbers. [S01, S02]
How the knowledge is organized
| Part | Chapters | Reader's question | Practical output |
|---|---|---|---|
| Foundations | 1-4 | What is agentic AI, and which risks matter? | System boundary, impact assessment, autonomy decision, threat register. |
| Control design | 5-8 | How should authority, data, memory, and human rights be protected? | Deployment manifest, enforcement architecture, approval and outcome design. |
| Assurance and operation | 9-13 | How will the enterprise know the controls work and respond when they fail? | Evaluation plan, monitoring envelope, telemetry, assurance case, recovery playbook. |
| Enterprise application | 14-16 | How does the design work in a business process and its legal context? | Worked workflows, delivery sequence, responsibility matrix, legal scope register. |
| Research and specifications | 17-18 | What does current evidence change, and how can it be implemented? | Interpretable research exhibits and twelve detailed implementation specifications. |
| Reference | Appendices A-J | What do terms mean, and which artifacts can be reused? | Glossary, baseline controls, templates, tests, metrics, worksheets, method, sources, and maintenance guide. |
Reading paths
| Reader | Recommended route | Decision to prepare |
|---|---|---|
| Board member or executive sponsor | Executive Summary; chapters 2-3, 12, 15; Appendix F. | Approve business scope, resources, accountable ownership, and residual-risk decision. |
| Business or product owner | Chapters 1-4, 8-9, 13-15; Appendices B-C. | Define authorized utility, customer consequences, operating limits, and remedy. |
| Architect, engineer, or security lead | Chapters 4-7, 9-13, 18; Appendices C-E. | Build and demonstrate enforcement, state continuity, evidence, and recovery. |
| Responsible AI, compliance, or validation lead | Chapters 2-4, 8-12, 16-18; Appendices D-I. | Challenge test validity, rights, regulatory scope, and the assurance claim. |
| Internal auditor or procurement lead | Chapters 3, 11-13, 15-16; Appendices B, F-G. | Obtain reproducible evidence, test independence, and assess supplier limitations. |
| Reader new to the subject | Chapters 1-4 in order; then the application in chapter 14 closest to their work. | Understand the system before selecting controls. Use Appendix A for unfamiliar terms. |
How to interpret evidence and examples
Source identifiers such as [S11] resolve to Appendix I. Research findings describe an inspected study or report. Official legal text, agency announcements, technical specifications, and voluntary frameworks retain their different status. Recommendations labeled proposed practice are designs to test locally.
All worked examples, proposed autonomy tiers, templates, control practices, and acceptance tests are illustrative. Their numbers and decision rules are not measured enterprise outcomes or universal targets. Quantitative figures based on published studies identify their sample and limits beside the exhibit. Figure and table captions are part of the interpretation.
The reading flow is layered: learn the concept, examine a failure mechanism, select a control, define a test and independent outcome oracle, and preserve the evidence needed for an operating decision. This structure lets the book serve as both an introduction and an implementation reference.