Five Planes Architecture Simulator
An interactive, explorable model of the Five Planes — Data, Model, Agent, Orchestration, Actuation — that scores each plane, surfaces the seams between them where most failures occur, and generates a stack-appropriate implementation path.
What it does
Chapter 4 introduces the Machine Core as a layered system: "The Machine Core doesn't operate as a single layer. It operates across five distinct planes" — Data, Model, Agent, Orchestration, Actuation — "each with different characteristics, failure modes, and governance requirements." The chapter's hardest lesson is not about any single plane. It's about the spaces between them: "the most costly failures typically occur at the seams between planes, not within planes." The data-to-model handoff that miscalibrates a capable model. The model-to-agent transfer that drops state. The agent-to-orchestration routing where two agents deadlock on a shared resource.
This simulator turns that architecture into something you can explore and stress-test. You walk each plane, score your current maturity, and the tool composites a Five Planes profile — then, crucially, it evaluates the seams, because "the strength of the whole is bounded by the weakest connection between layers." It is part learning tool (click a plane, see its components, its pitfalls, a real-world example like Glean's data plane or Cursor's model router) and part diagnostic (where is my architecture actually weak, and what do I build next, given my budget and team).
The chapter's warning frames the whole tool: "You cannot compensate for poor data governance with excellent models. You cannot compensate for underspecified agents with sophisticated orchestration." A high score on four planes and a weak Data Plane is not 80% of an architecture. It's an architecture bounded by its foundation.
Who it's for: architects, engineers, and CTOs who need implementation detail beyond the concept — plus founders deciding where to invest scarce engineering capacity first.
Figure: The Five Planes this tool simulates — an interdependent stack whose strength is bounded by its weakest inter-plane connection.
The foundation. Governed corpora and queryable memory the whole Core reasons over. Never glamorous. Always foundational — a weak Data Plane caps everything above it.
No quality contracts, missing lineage, over-engineering, access control as an afterthought.
Glean unifies enterprise data with quality contracts and lineage so every downstream plane reasons over governed, traceable context.
30 days: Consolidate scattered corpora behind one governed retrieval layer; enforce schema + freshness contracts in CI.
90 days: Wire lineage end-to-end and role-based access; backfill quality contracts across all production sources.
The Machine Core operates across five planes — Data, Model, Agent, Orchestration, Actuation. The most costly failures occur at the seams between planes, not within them.
The strength of the whole is bounded by the weakest connection between layers. You cannot compensate for poor data governance with excellent models. Switch to to score 25 maturity questions, find your binding constraint, and get a 30/90-day path.
Five Planes of Operation
Machine Core + Human Cortex
Agent Charter Builder
Cognitive Overhead Index Calculator
Defensibility Stack Assessment (A.G.E.N.T.)
AI-Born Readiness Assessment
- Book 1, Chapter 4 — "The Five Planes: Foreshadowing the Architecture" (all five planes; the seams where failures concentrate; the weakest-connection rule).
- Book 1, Chapter 5 — "The Operating System" (PRAL loop, Agent Charters, the integration loop running across the planes; Lilli mapped to all five planes).