Missions

A Mission records one bounded job. It links the declared purpose, allowed services, operational caps, Passports, runtime events, and terminal result under one Mission ID.

Lifecycle

• Open: define the job, expected counterparties, optional output shape, and deny-and-flag or auto-revoke caps.
• Run: bind Passports and Intents to the Mission. STACK records proxy calls, checkpoints, detector signals, and handoffs against it.
• Complete: store the terminal result and its signed claim.
• Revoke: stop the Mission. Adversarial and hard-cap revocations cascade to bound Passports.
• Review: reconstruct the signed timeline and add human Operator review evidence after the work ends.

Caps

A Mission can cap actions, bytes deposited into Drop-offs, duration, concurrent Intents, actions per service, and covered spend. The response from GET /v1/missions/:id includes current cap use.

A Mission is also not a legal or operational mandate. An authority binding can pin one or more Mission IDs so externally proved authority is usable only inside those jobs. The binding still owns the principal, receiver, purpose, scope, proof lineage, and expiry. See Authority.

Evidence

Replay reads the Mission's signed claim set in time order. Signed records export the claims and verification material available at export time.

A dossier is a human-authored post-incident account. It requires a same-operator member principal. An Operator review is a separate signed record. Its source, creation, and revision routes require a signed-in dashboard session.

See Missions API, Evidence API, and Passport Lifecycle.