choosing-graphlisted

## Coordination graphs State the graph before work starts, using the first matching case: - **orchestrator-worker** — multiple app-rooted workers coordinated through status events, including capped batches and dependency plans. - **sub-agent fan-out/fan-in** — independent work branches run in subagents and their caller integrates the results. Work needing the target app's own harness uses an app-rooted dispatch. - **single-loop** — one bounded task carried by one agent, including coordination of one dispatch. An independent review is a checkpoint, so it does not change the graph. Only `orchestrator-worker` writes `~/.straw-boss/plans/<slug>/plan.json`, through [boss-say](../boss-say/SKILL.md#plan-and-schedule). The other graphs create no Straw Boss plan or repo-local spec. A dispatch's instruction, contract, and status under `~/.straw-boss/dispatch/` are lifecycle records, archived at wrap-up. The app's own development artifacts follow its local workflow. ## Reality anchors The main agent names the anchor and checkpoint; the worker and user choose the verification method inside that anchor. - **testing** — default for programming changes. Use the smallest credible seam that can go red before the change, plus the app's own verification commands such as its test script, lint, and type check; escalate to integration or E2E according to the app's conventions. - **pseudo-human** — a browser or computer operates the real interface, with screenshots and measurements as eviden