Skip to content
Press / to search

Component Specs

Reference specs for each runtime component, organized by plane.

Reference DesignLast reviewed: Edit on GitHub
At a glance

These pages provide interface details, JSON envelopes, and operational concerns for each runtime component. Components are grouped by plane.

These are logical ownership and integration designs. The repository implements the compiler and deterministic execution validators, not all listed runtime services. The Execution Contract maps exact action/approval, boundary/data/memory, operation/checkpoint and budget obligations onto those owners. Control Profiles select cumulative requirements; Conformance requires current deployment evidence. A component name or declared support cannot establish enforcement.

Decision plane

Context plane

Action plane

  • Tool Gateway pattern — Action-plane boundary every external effect must cross
  • Tool Manager — Tool Gateway component design: typed envelopes, native-risk enforcement, identity brokering, v1 projection and provider-specific effect recovery

Intelligence plane

Trust plane

  • Policy Engine — deterministic JsonLogic and native action-risk boundary; emits structured decisions and obligations
  • Evaluation Engine — scorecards, golden replays, release gates
  • Observability — OTEL-first tracing, audit persistence, tail-based sampling

Operator surface

  • Admin Console — operator surface across all registries and queues