Governance patterns rarely work alone. A watchdog is only as good as the telemetry it reads; a human-in-the-loop gateway needs a durable record of what the agent was doing when it paused. This graph maps the 13 formal patterns across the 12-Layer Agent Governance Stack and shows how they rely on, feed and reinforce each other, and which of the five mechanical failure invariants each one contains.
Click any pattern or invariant to see its connections. Every link carries its evidence: a sentence quoted from the pattern text, a mapping from the sixteen-pattern catalog (Table 3.5), or a clearly marked editorial inference. Use the filters to hide link types or show only links the text states directly.
The 13 formal patterns from Chapters 4–8, placed on their stack layers, with the five failure invariants from Chapter 1 on the left. Pick a maturity level to see which patterns a system at that level needs. Click any box to see its links and the sentence in the book behind each one.
Link strength: Stated means the pattern’s own text names the other pattern’s mechanism. Via Table 3.5 means the catalog in Chapter 3 assigns that invariant to a catalog pattern this pattern implements. Inferred is an editorial reading of how two mechanisms fit together, not a claim made in the text. Catalog numbers (P1–P16) are matched to formal patterns by mechanism and layer. Maturity levels follow the Agentic AI Maturity Model in Chapter 2; the level at which each pattern becomes necessary is an editorial reading. Layers 11 and 12 (Chapter 9) are not yet included.
What the graph shows
- Attested workload identity is the foundation. Five other patterns depend on it, from progressive context disclosure to the REND privacy bus.
- Dual-plane decision lineage is the hub. The watchdog, the meso verification cascade and the human-in-the-loop gateway all consume its telemetry and trajectory records.
- The runtime controls form one causal chain: decision lineage feeds the verification cascade, the cascade’s scores feed the watchdog, and the watchdog hands checkpoints to the human-in-the-loop gateway.
- Every failure invariant has at least one containing pattern, and most have two or three, so no single control carries the whole load.
