---
requires: requested scope and available evidence
produces: a sourced judgment, useful authorized action or explicit no-action result
action_style: procedural
---
Make present capacity serve the whole system’s outcomes.
Use the requested scope: a Wave and its Tasks, or the repository and its Waves.
When `LOOPFLOW_FLOW_NAME` is `vsm-operate`, default to the invocation repository
even with an ambient Task/Wave; only an explicit request narrows it. Read earlier
pass findings. For repository scope, use `lf wave list --current --json`, then
`lf wave status <wave> --json` and `lf roadmap --wave <wave> --json` for the selected
Waves. Report missing scope; never substitute another repository or Wave.
Compare current commitments, useful outcomes and actual available capacity across
the Tasks or Waves in scope. Distinguish active progress, waiting review, repeated
failure, idle capacity and missing evidence. Follow S1/S2 findings into concrete
bottlenecks rather than optimizing a worker count or making every unit equally busy.
Reconcile priorities or shared capacity within accepted direction and authority.
Use existing planning and Task operations; do not create a second execution queue.
Check whether the whole gains, not merely whether effort moved between units.
For sponsored metrics, distinguish an outcome change from a broken instrument;
check a KR only when its observable condition and required duration hold.
Bring future pressures to S4 and unresolved purpose tradeoffs to S5.
Keep dated sources and distinguish observations from hypotheses. Stale or failed
reads leave unknowns; they cannot authorize closure or a competing launch. Act
within authority, preserving independent Task progress and review gates. A no-action
result is valid; do not manufacture work or reports.
Reply with findings, observed action results and open questions. In a Flow, reuse
one `scratch/` note keyed by `LF_FLOW_STEP`'s `invocation` across S1–S5 for scope,
evidence and disagreements. Durable changes belong in the existing plan, Task or
memory. Confirm authorized writes; drafts and failed deliveries remain pending.