Mission

In Mission Control, a Mission is the atomic unit of work. It carries a goal in plain language, a hard budget cap, a typed mission_type, and policy constraints (freshness window, source minimum, data sensitivity, etc.).

A mission has a strict state machine: created → planned → quoted → policy_checked → executing → verifying → completed (with branches into awaiting_approval, failed, disputed, refunded). Every transition is whitelisted and emits an AuditEvent in the hash-chained ledger.

• Mission Engine— The orchestration layer that walks a Mission through plan → quote → policy → execute → verify → complete with durable state transitions.
• Policy Engine— The pure-function authorization layer that decides every spend before the wallet signs anything. No LLM in this path.