The fundamental execution unit of the Metaprise Agent OS. Every agent action — from a simple tool call to a multi-step enterprise workflow — is declared, constrained, executed, and recorded as a Mission.
Every Mission flows through six precisely defined primitives. Together they guarantee that agent execution is declared, constrained, traceable, and immutable — from launch to close.
Four-Field Declaration
The foundational declaration of what a Mission is: objective, tools, authority level, and timeout. Immutable once the Mission launches — no scope creep, no privilege escalation.
Strict 8-State Machine
Every Mission transitions through exactly 8 states: CREATED → PLANNING → WAITING_APPROVAL → APPROVED → PENDING_EXECUTION → IN_PROGRESS → EXECUTED → CLOSED. No shortcuts, no hidden states.
Immutable Input Environment
The input environment provided to the Mission at launch. Once launched, MissionContext is frozen — the agent cannot modify its own input data. This prevents self-justification loops and data contamination.
Four Constraint Groups
Four constraint groups — authority, policy, data, and runtime — snapshot-frozen at launch. The agent operates within these boundaries for the entire execution. No boundary can be widened mid-flight.
Immutable Result Record
The final result of the Mission — written once when state transitions to CLOSED, then sealed permanently. Cannot be modified, deleted, or overwritten. The definitive record of what the agent accomplished.
Audited Mutable State
The only mutable primitive — the agent's working memory during execution. Every write to MissionStateData generates an AuditChain entry. Full transparency into how the agent's understanding evolved.
A Mission begins with a four-field declaration: what it must do, which tools it may use, what authority it needs, and how long it may run. The input environment — MissionContext — is snapshot-frozen at launch. The agent reads its context but can never modify it.
Every Mission transitions through exactly 8 deterministic states. Each transition is validated by the Control Plane, recorded in the AuditChain, and visible in real-time via Observability. No state can be skipped; no transition can be forced.
MissionBoundary defines the cage the agent operates within — four constraint groups frozen at launch. MissionOutcome is the sealed result — written once, read forever. Together they guarantee that what the agent was allowed to do, and what it actually did, are permanently recorded.
Every Mission follows this exact path. Each state transition is validated, recorded in the AuditChain, and visible in real-time through Observability.