Implementation profile

Mission Gate 0.2

The machine-readable contract implemented by the current Mission Gate beta: classify exact inputs, pause at authority boundaries, resume only an approved action, and prove completed effects with signed, trace-correlated receipts.

Version 0.2 Status Beta Updated August 2026 License Apache-2.0

1.Boundary¶

This is an implementation profile, not a replacement for the portable Trust Graduation v0.1 method. It records exactly what Mission Gate emits and validates today so adopters can test interoperability without treating Mission's storage or product UI as protocol requirements.

A host MUST distinguish preparation, approval, execution, and outcome. Approval authorizes one bounded action; it is not proof that the action happened.

2.Current objects¶

mission-action/v1Normalized proposed action and exact input mission-grant/v1Bounded authority granted to one action mission-decision/v2Gate result with exact-input binding mission-capability-policy/v1Capability policy evaluated by the gate mission-desktop-execution/v1Approved execution envelope mission-execution-receipt/v2Signed completion proof mission-outcome/v1Attributed later outcome mission-authority-interruption/v1Portable paused-run state mission-receipt-signature/v1Ed25519 workspace signature envelope mission-public-key-manifest/v1Verifier key discovery

3.Action classes¶

The Gate beta deliberately implements a smaller registry than the portable v0.1 examples. Unknown classes fail closed unless the host declares an extension.

Identifier	Risk	Effect
`browser.research.read`	read-only	none
`agent.plan.prepare`	plan-only	none
`gmail.draft.create`	reversible write	draft only
`mission.task.update.local`	local state move	local only
`email.send.external`	external consequence	email send

4.Signed receipt v2¶

A completion receipt binds the workspace, execution, grant, capability, target, exact input, provider result, and trace context. SHA-256 digests cover the action, grant, decision, policy, and payload. The workspace signs canonical JSON with Ed25519; the signature envelope itself is excluded from the signed bytes.

proposal → decision → authority interruption
         → principal approval → resume once
         → provider effect → signed receipt → outcome

Queued, blocked, prepared, and approved states MUST NOT be represented as completed execution receipts.

5.Conformance¶

The zero-dependency package includes JSON Schemas, canonicalization helpers, a CLI, cross-object checks, and positive and adversarial fixtures.

npx @gomission/mission-schemas mission-schemas-conform \
  --schema mission-execution-receipt/v2 \
  --file receipt.json

npx @gomission/mission-schemas mission-schemas-conform \
  --chain --file chain.json

Until the npm package is published, use the source in the public repository. The profile does not claim publication before the registry confirms it.

Inspect source and fixtures ↗ Read portable v0.1 →