Skip to content
Private preview — Design partners are now being selected for controlled agent-execution pilots.Apply now
System Architecture

Architecture

How DecisionHypervisor sits between agents and execution: the decision path, the deployment model, and the data plane.

The Boundary

DecisionHypervisor is model-independent infrastructure. Any agent framework, any model — the intelligence plane proposes actions; the authority plane decides what executes. The two planes meet at exactly one place: the decision path below. Nothing crosses except through it.

The decision path

01

Intercept

A proposed action is intercepted in the execution path — before any tool, API, database, payment rail, or machine is touched.

02

Normalize

The action becomes an immutable Execution Intent: a strictly typed decision object. Unknown or malformed fields are rejected at the boundary.

03

Evaluate

A deterministic Rust policy engine resolves the applicable, approved policy versions against the intent and its context. Same inputs, same decision — every time.

04

Decide

The kernel returns an explicit outcome: authorize, deny, or escalate. Escalations are first-class human review workflows, not log entries.

05

Record & publish

Every decision appends to a SHA-256 hash-chained audit trace and publishes through a transactional outbox to the event stream for downstream systems.

The kernel

Deterministic engine

Policy evaluation is implemented in Rust with reproducible outcomes — no model inference anywhere in the decision path.

Immutable intents

Execution Intents are write-once records with typed, sortable identifiers. Decisions are never silently rewritten.

Versioned policy

Policies carry an explicit lifecycle — draft, approval, activation — so the exact policy version behind every decision is knowable.

Open contract

The runtime exposes an OpenAPI 3.1 contract. The boundary is documented and testable, not implied.

Deployment model

Decision nodes deploy at the edge — inside your private VPC, including air-gapped environments — with policies cached at the node. Evaluation happens locally, at machine latency, without your actions leaving your boundary to be decided.

Isolation & data plane

Every record is scoped by tenant and environment, enforced by PostgreSQL row-level security — database-enforced isolation, not application convention. Decision events stream through a transactional outbox to NATS JetStream. Security principles →

Request a Control Pilot
Architecture | DecisionHypervisor