Evidence and runs
A run ends in a folder you can read, query, or resume: the trace, the typed reports, the evidence.
A run is one execution of a flow. Each run owns a run folder that holds everything the run produced: its trace, reports, evidence, and resume state.
The default location is .circuit/runs/<run-id>. Inside it, the trace is
the ordered record of what happened: step entry, relay requests, checkpoints,
and completion. A report is the typed output a step or the close stage
writes: a named, versioned contract such as fix.brief@v1, build.plan@v1, or
explore.analysis@v1, and the typed input a later step
reads. Evidence is the
supporting files, checks, and reports a run produces or consumes, used to verify
the work and to recover if the run is interrupted.
Relay steps can carry acceptance criteria: deterministic checks a step's result must pass before the run advances. When a check fails, the step either retries with the failure passed back as feedback, or stops the run.
Inspecting a run
Project a run's status from its folder:
circuit runs show --run-folder .circuit/runs/<run-id> --jsonThe command requires --json and prints the projected status.