# Operate, review, and recover a workflow run

A workflow run records one execution of a definition. Use its state, outputs, and review controls to understand progress and make deliberate changes.

## Start a run
Open **Workflows**, choose a definition or **Start from template**, and supply the requested inputs. You can describe the intended job to find a template. Check the selected process before launch.

## Read the run
Inspect steps, outputs, waiting gates, failures, and the current workspace. The ledger can show completed steps, verdicts, estimated cost, tokens, and timing. Introspection adds run details such as failed steps, cache hits, models, verification coverage, and captured evidence where recorded.

## Steer and review
Send feedback to guide the next iteration. Standing project guidance can reach both the worker and judge, so keep it consistent with the task’s exit criteria. In review triage, inspect each finding against the current diff. Accept findings that should go to the worker and reject unsupported ones. **Dispatch** sends accepted findings; re-check anchors when the diff changes.

## Work with deliverables
The outbox exposes artifacts and lets you hand files to a run. Open its deliverables and inspect any warning that a referenced local file could not be copied. **Take this work** on a preserved workspace is a handoff; confirm what was preserved before removing the original environment.

## Change a run deliberately
A completed step may require rewind before editing. Review the cascade confirmation: downstream work can run again. Resume reuses appropriate recorded work; rewind invalidates the affected region. External side effects are not automatically undone.

## Policies and cleanup
Set run-specific policy overrides before launch; unset values follow the kind defaults and launched policies are frozen. Deleting a run can also delete its artifacts. Keep needed outputs before confirming deletion.