Every run, in
its full context.

A run groups a mission, its worker processes, coordination policy and execution receipts. The supervisor keeps each process attached to the workspace and budget that authorized it.

Workspaces bound what an agent can inspect and change. Snapshots and isolated branches let candidate work proceed without silently overwriting the state that another path is using.

Budgets define how much time, work or model usage a run may consume. The supervisor can surface spend against its declared ceiling and make exhaustion an explicit execution outcome.

A process view is useful only when it explains how the run reached its current state. Events make admission, handoffs, budget decisions and worker outcomes reviewable in order.

Runtime memory can inform a mission with prior observations and decisions. Scope, source and retrieval context matter: an item should remain traceable to where it came from and why it was returned.

Evidence reports connect a run's claims to the artifacts, checks and provenance behind them. Reviewers can see what passed, what remains partial and which gaps still block promotion.