Persistent
Mandates survive restarts, upgrades, and runtime replacement.
CONFIDENTIAL AUTHORITY LAYER
Attach a confidential operating mandate to an autonomous runtime. Update authority without replacing the agent. Keep every consequential action inside a proposal-bound, versioned perimeter.
Mandates survive restarts, upgrades, and runtime replacement.
Sensitive thresholds remain encrypted and access-controlled.
Every authority change creates an immutable audit point.
02 — The Primitive
Messages can influence what an agent considers. Engravings determine what consequential behavior remains permitted across time, restarts, and different runtimes.
Changes intent. Often temporary.
Defines authority. Durable.
03 — Why Engravings
Authority should survive the process that interprets it. The runtime can change. The governing boundary remains attributable and inspectable.
Mandates survive restarts, upgrades, and runtime replacement.
Sensitive thresholds remain encrypted and access-controlled.
Every authority change creates an immutable audit point.
Consequences require proposal-bound authorization.
04 — Architecture
Confidential coordination, encrypted mandate evaluation, and private consequences are one continuous authority path—not separate privacy features.
COTI encrypted coordination
Autonomous agent runtime
Confidential mandate store
COTI MPC evaluation
Private ERC-20 consequence
Why COTI: confidential computation, private coordination, and private value all share one enforceable authority path.
Give autonomous agents room to operate without letting capability silently expand authority.