Knowing the patterns is one thing; knowing which ones your system is missing is another. This explorer approaches the catalog from the operational end — where the research weight actually sits, what patterned architecture buys you over raw prompting, and a 12-point audit that scores your own system against production-grade standards.
↗ Open the explorer full-screen — the readiness audit is interactive; tick the controls you actually have.
Where the weight sits
The density chart plots all 55 patterns across seven chapters, and the shape of it is the argument. Robustness & Fault Tolerance (Ch 7) is the largest single domain at 16 patterns — more than Coordination’s 14, and four times Compliance or System-Level. A catalog that devotes its biggest chapter to watchdogs, checkpointing, retry mutation, and envelope isolation is making a claim: in multi-agent systems the hard engineering is not getting agents to cooperate when things go well, it is containing them when one hangs, returns nonsense, or half-completes a transaction.
Prompting versus patterned architecture
The radar chart contrasts a prompt-only system with a patterned one across fault tolerance, consistency, explainability, security, and cost control. The mechanism behind the gap is worth stating plainly: patterns supply the deterministic boundaries a stochastic model cannot supply for itself. A prompt asking an agent to “be careful with production” is a suggestion; a watchdog supervisor with a token budget is a wall. The first degrades under adversarial input and long sessions; the second does not, because it never depended on the model’s cooperation.
That is also why the explorer frames the benefit as decoupling — separating cognitive reasoning from system execution is what makes tracing, auditing, and cost-controlled scaling possible at all.
The readiness audit
The most useful part is the last section. Twelve production controls — observability traces, financial circuit breakers, step-limit watchdogs, model fallback, incremental checkpoints, human review gates, PII sanitization, schema validation, instruction anchoring, tool registry, RBAC, event-driven reactivity — and a live score as you tick them off:
- 0–4 · Foundational — the system works in demos. Circuit breakers and state management come first.
- 5–8 · Production-Ready — resilience is real; tracing for compliance is the next gap.
- 9–12 · Autonomous Fabric — suitable for high-availability, regulated domains.
Score it honestly rather than aspirationally. The common failure is a system sitting at Foundational while everyone assumes it is Production-Ready, because the controls that were skipped are exactly the ones that stay invisible until an incident.
Going deeper: the full 55-pattern catalog has the complete treatment of each pattern, and the skills download packages them as installable Claude Agent Skills. The Fractal Chain-of-Thought pattern — one of the compliance patterns represented here — is written up in depth.
