Quick Reference Index: Organizational Problem → Actionable Solution
Operational support guide. This volume is consulted by organizational role and operational context. This index maps critical organizational challenges to specific chapters, highlighting direct implementation assets (worked exercises and templates) where available.
1. By Organizational Challenge
Section titled “1. By Organizational Challenge”| If Your Challenge Is… | Consult | Direct Implementation Asset |
|---|---|---|
| “Leadership demands AI compliance against unfamiliar statutory regulations” | Ch. 1 (Global Regulatory Frameworks) | — |
| “I must defend a multi-agent architectural proposal before an executive committee” | Ch. 4 (ATAM Framework + Critical Agent Review) | Worked Exercise 4.1 (Translating Technical Risk into CFO Financials) |
| “Stakeholders expect AI delivery speed far beyond empirical engineering realities” | Ch. 10 (Managing Expectations and Timelines) | — |
| “I need to assess whether my engineering team is equipped to orchestrate agents” | Ch. 8 (Agentic Maturity Model) | — |
| “Developers are burned out and synthetic code quality is degrading” | Ch. 13 (Fatigued Programmer Symptom, Context Watchdogs) | — |
| “I need to structure agile delivery sprints for autonomous agents” | Ch. 6 (Cadence Template, Swarm Roles) | Worked Exercise 6.1 (Swarm Quarterly Closing) |
| “I must bridge the velocity gap between technical execution and business delivery” | Ch. 7 (DORA Metrics, Just-in-Time Pattern) | Worked Exercise 7.1 (Quantifying the Financial Value of Lead Time Reduction) |
| “We are unsure how to scope and govern agent runtime permissions” | Ch. 20 (Permission Lifecycle, Autonomy Index) | — |
| “Liability is ambiguous when an autonomous agent introduces a critical defect” | Ch. 15 & 21 (Agentic RACI, Liability for Synthetic Code) | — |
| “We want to launch an agent initiative without risking company reputation” | Ch. 22 (Agentic MVP, RACE Framework) | — |
| “We need complete, production-grade enterprise case studies to benchmark against” | Ch. 3 & 5 (El Niño Climate System, Automated Bug Hunting) | Worked Exercises 3.1 & 5.1 |
| “I want to train engineers with reproducible, test-driven katas” | Ch. 14 (Agentic Katas) | — |
| “We need to build a defensible business model and monetize agent capabilities” | Ch. 19 (Four Monetization Archetypes, Defensible Moats) | — |
| “Our engineering team is overwhelmed by tool sprawl across the AI ecosystem” | Ch. 18 (Layered Architecture Map, Disciplined Non-Adoption) | — |
| “We need to reclaim genuine agility from ceremonial corporate bloat” | Ch. 25 (The Twelve Agile Principles Reclaimed) | — |
2. Index of Worked Exercises in This Volume
Section titled “2. Index of Worked Exercises in This Volume”| Exercise | Core Capability Trained | Chapter |
|---|---|---|
| Worked Exercise 3.1 | Designing the Critical Review Agent for High-Risk Systems | 3 |
| Worked Exercise 4.1 | Translating Technical Risk into Executive Financial Terminology | 4 |
| Worked Exercise 5.1 | Deploying the Adversarial Refutation Agent | 5 |
| Worked Exercise 6.1 | Structuring the Swarm Quarterly Closing | 6 |
| Worked Exercise 7.1 | Calculating the Capital ROI of Lead Time Reduction | 7 |
3. Cross-Volume Demarcation
Section titled “3. Cross-Volume Demarcation”If your challenge involves foundational systems architecture (agents, context windows, tools, orchestration patterns), consult Volume 1. If it involves cybersecurity attack surfaces, vertical industry case studies, or geopolitical dynamics, consult Volume 2. If it centers on runtime operations and scale (token economics, CIU metrics, chaos engineering, observability), consult Volume 4. This volume addresses how to organize, govern, and upskill engineering teams around agentic systems, not how to write their underlying code.
4. Operational Usage Warning
Section titled “4. Operational Usage Warning”The templates and governance frameworks in this volume are sensitive to organizational context: the delivery cadence template in Chapter 6 presumes an engineering team empowered to refactor its own ceremonies, and the agentic MVP in Chapter 22 presumes a business sponsor willing to tolerate low-cost failure. Prior to implementing any framework, verify both preconditions; where either is absent, the respective chapter details a degraded, defensive fallback.