SUPERVISION/SUPERVISED PROCESSES
01 / SUPERVISED PROCESSES

Launch work with
clear limits.

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.

EXAMPLE MODEL This page describes a runtime surface; values and events are illustrative.
PROCESS LIFECYCLE

A reviewable
sequence.

Each transition keeps its relationship to the mission and the state that authorized it. That makes later review more useful than a detached success message.

01 · ADMIT

Validate the run

Resolve the mission, worker configuration, permissions and available budget before execution.

01
02 · START

Launch workers

Start configured processes and preserve their identities, roles and parent run.

02
03 · OBSERVE

Collect outcomes

Track state changes, handoffs, failures and completion through runtime events.

03
04 · CLOSE

Keep the execution trace

Attach outputs and execution receipts as traces; link separate evidence only when it is available for review.

04
WHAT THE OPERATOR CAN INSPECT

Context is part
of the control.

Process statesqueued · running · stoppedLifecycle is visible per worker
Run boundaryworkspace + policyWorkers inherit explicit scope
On completionreceipt ≠ evidenceExecution traces and proof stay separate
“
RUNTIME PRINCIPLE
A process exit records execution status; a mission outcome needs separate evaluation, and a receipt alone is not evidence.
← Back to supervision overview