Product

The execution layer for self-improving enterprises.

Company Twin → Charter → Work Object → Agent Runtime → Policy Gate → Receipt → Value Ledger.

Product version: May 2026
Charters

Mandates make execution safe.

Charters define what SupraOS may pursue, what it may prepare, what requires approval, and what must be proven.

Charters
SupraOS Charters screen
Charters define mandate, scope, allowed actions, held actions, and proof requirements.
Work Objects

Work becomes executable state.

Work Objects carry the operating problem, evidence state, policy boundary, assigned agents, receipt state, and lifecycle.

Work Objects
SupraOS Work Objects screen
Work Objects carry value, evidence, owner, state, policy, Receipt, and lifecycle.
Agent Execution Runtime

Agents run inside bounded authority.

SupraOS-managed agents coordinate evidence, risk, recovery, policy, verification, writebacks, and value state without escaping the Charter boundary.

Agent Execution Runtime
SupraOS Agent Control Tower screen
Agents coordinate evidence, risk, recovery, policy, writebacks, verification, and value state.
Other primitives

One loop, many surfaces.

Company Twin

Maps source coverage and operating graph. See the homepage stack section.

Value Leak Engine

Ranks exposure, evidence strength, policy state, and next action. See Company Scan.

Policy Gate

Classifies allowed, held, and blocked actions before execution. See Proof.

Receipts

Bind evidence, policy, approval, action, verifier state, and outcome. See Proof.

Value Ledger

Separates detected exposure, active risk, confirmed value, and unresolved exposure. See Proof.

Trust + Sources

Source access, blind spots, policy boundaries, and governance controls. See Trust and Company Scan.

Start with one Company Scan.

SupraOS maps approved signals, recommends the first Charter, and defines the proof model before execution rights expand.