Skip to main content
The native kernel wraps selected domain mutations in a command, policy decision, and durable receipt. It is separate from direct accessors: commerce.orders.createExact() does not become governed merely because an agent called it.

Keep authority outside model arguments

A command carries identity/delegation, tenant/store, command type, stable retry key, mode, payload, and optional versions, deadline, approval and exact commitment. Policy is deny by default. Required approval binds the intended scope/key; signed authority binds semantic intent. A host must authenticate identity and load policy from operator-owned configuration. EconomicAgent and EconomicAuthority support explicit delegated actors, autonomous and approval ceilings, and deny ranges. Economic intents provide a framework-neutral vocabulary; their existence does not implement every business verb as one atomic workflow. Economic receipt signatures need an independently trusted key map; embedded keys do not establish trust.

Run a local receipt example

Install @stateset/embedded@1.39.0 in a fresh directory. The policy below is an application-owned fixture allowing one reservation command in one test store. Do not accept this policy or its principal from an agent’s tool arguments. Save as governed-reservation.mjs:

Replay from another process

Retain the exact request before dispatch. Save as replay-reservation.mjs and run after the first process exits. This test repeats the original command, not a new business action.
The governed mutation, its receipt, and receipt-audit chain commit together. Inspect receipt status, error/retry disposition, versions and event IDs. A preview, rejection, succeeded local mutation, and external completion establish different facts. Preserve original identity after response loss; new keys can create new effects. This fixture does not test host power loss.

Strict MCP configuration

For an autonomous endpoint load --kernel-policy, --kernel-principal, and --kernel-store-id from protected operator files before enabling --apply. The matching STATESET_KERNEL_POLICY, STATESET_KERNEL_PRINCIPAL, and STATESET_KERNEL_STORE_ID environment settings are available. Strict discovery exposes typed governed writes and available reads; a domain profile does not grant capabilities or make an unsupported write governed. Inspect the actual catalog and policy. See MCP, CLI safety, and recovery.
Last modified on October 20, 2026