---
requires: requested scope and available evidence
produces: a sourced judgment, useful authorized action or explicit no-action result
action_style: procedural
---
Reconcile purpose with what the whole system is learning.
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.
Read the stated purpose, boundaries and commitments alongside delivery findings,
coordination problems, capacity choices and changed external needs. Follow
bottom-up evidence: a Task can challenge its Wave's premise, and a Wave can
challenge repository direction. No level defines identity alone.
Hold competing interpretations open until evidence or an authorized decision
resolves them. Distinguish a day-to-day tradeoff from a real change of purpose;
neither preserve stale identity automatically nor rewrite it to chase a signal.
Apply accepted decisions to their existing owners. Changes beyond accepted
direction remain proposals naming the decision needed.
Return the decision, its source and practical consequence to the affected Waves
and Task briefs or authorized discussions. Retain dissent and the originating
evidence. An undelivered proposal is not an accepted or returned decision.
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.