Missions and Local State

Missions and Local State

Why missions exist

A mission gives a bounded local context to coordination. It collects a target, baseline, authority envelope, packet workspace, residual ledger, task queue, provider policy, and human-readable workbench under one declared scope.

The mission layer is local-first. Its normal role is to organize and inspect state, not to claim that a real-world objective has been achieved.

Typical local layout

With --root ccr-runtime, CCR writes inspectable state beneath that directory. Important locations include:

ccr-runtime/
  ccr.sqlite
  blackboard/events.jsonl
  packets/
  tasks/
  residuals/
  reports/
  workcells/
  experiments/

SQLite is the default one-machine store. JSON artifacts remain inspectable inputs and exports; in the distributed profile, PostgreSQL becomes authoritative and JSON files are content-addressed exports.

Inspection versus local mutation

CCR makes local write boundaries explicit.

Command family	Effect
mission status, mission next, task next, residual market, phase report, agent explain	Inspect local state; no external action.
asi quickstart, mission init, mission ingest	Create mission and local artifacts.
workbench report --out, workbench export --out	Write a local report or static workbench.
packet submit, provider import, experiment register	Add candidate evidence or preregistration artifacts locally.
task lease, task heartbeat, task complete	Change local transactional task state.
residual assign, residual resolve, residual reopen	Change a residual workflow while preserving evidence.
storage migrate --apply	Apply an additive local storage migration.

Local mutation is not an external side effect. Conversely, an inspection report is not proof merely because it is rendered as Markdown or static HTML.

Mission workflow

Create or inspect mission
        |
Find the next residual or leaseable task
        |
Produce a scoped candidate packet or repair artifact
        |
Attach verifier evidence and preserve failures as residuals
        |
Form phase diagnostics or compare a preregistered baseline
        |
Keep settlement false until all declared gates pass

mission next is advisory: it selects the next safe, local action from current state. It does not execute the action, dispatch a provider, or grant authority.

Useful local health checks

ccr --root ccr-runtime storage doctor --json
ccr --root ccr-runtime storage migrate --json
ccr --root ccr-runtime storage reconcile --json

storage migrate is a dry-run report unless --apply is specified. storage reconcile reports missing files, digest mismatches, and path escapes without silently choosing which copy is correct.

For coordinated task work, see Workcells, Tasks, and Residuals. For distributed storage, see Storage and Distributed Runtime.