Planes describe operational responsibility across the layered stack. They are useful only when each plane has clear ownership, data flow, and failure behavior.
Control plane and execution plane
Text description
Two large horizontal regions are connected by versioned configuration. The control plane contains model catalog, policies, routes, deployment configuration, evaluation gates, and rollout controls. The execution plane contains admission, context assembly, inference, tool execution, validation, and response handling. An evidence plane receives telemetry and decisions from both and returns evaluation findings to the control plane. A data plane contains model artifacts, retrieved context, caches, and business records, with labeled boundaries rather than unrestricted access.
Control plane
Publishes configuration, deployment state, routing rules, policy bundles, model versions, rollout intent, and capacity targets. Execution should continue on a known-good snapshot when control-plane dependencies are unavailable.
Execution plane
Admits requests, schedules work, runs models and tools, enforces request-time decisions, and returns or persists outcomes.
Data plane
Moves model artifacts, context, request payloads, tool data, caches, and product records. Use this plane only where separating data movement clarifies trust and residency.
Evidence plane
Correlates metrics, traces, decisions, approvals, effects, evaluations, and incidents without assuming raw prompts can be retained.