dispatchlisted

# Dispatch Implement the requested outcome with the fewest useful handoffs. An explicit build or fix request authorizes local execution after inspection; do not add a build confirmation. It does not authorize push, merge, publication, broad cleanup, or unrelated edits. ## 1. Load and bound Read project instructions, repository status, the supplied `.hyperflow/tasks/<slug>.md` when present, and the relevant implementation/tests. Preserve dirty-worktree changes and identify overlap before editing. If there is no task file: - Direct work executes from the inspected request. - Focused or Deep work first creates the single task file using the `plan` structure, then continues automatically because build intent is already explicit. Confirm the lane from evidence: | Lane | Execution | |---|---| | Direct | Coordinator edits, validates, and reports. Zero child agents. Escalate if risk or scope expands. | | Focused | Use at most two worker calls for independent tasks; the coordinator handles the rest. One separate batch reviewer checks the integrated diff. Full plan-and-build ceiling: four child calls. | | Deep | Use at most three worker calls, ordered by dependency, then one matching specialist integration reviewer. Security and migration work always stays Deep. Full plan-and-build ceiling: eight child calls. | Keep the Focused full chain <=20k non-cached tokens and the Deep full chain <=60k non-cached tokens when the host reports usage. Treat these as ceilings, not targets; nev