dispatching-work

Prepare the dispatch

Confirm herdr status and the $HERDR_PANE_ID live record. Resolve the worker setup, register through contacting-orchestrators, and record this session's fingerprint. Team-mode cwd: shipping-task.

Write the brief

About 300 words:

• The work -- per item the current symptom and required behavior, the user's exclusions, and any input, path, or port the worker cannot reach itself. Earlier findings are evidence references.
• The anchor and who exercises it -- the anchor, what it observes, and whether the worker runs its own checkpoint or hands its evidence to a shared one. The worker and user choose the verification method inside that anchor.
• Its place and motive -- where the task sits and why.

Leave out the cause, code location, and conventions: target-app discovery and work decisions stay with the worker. Name a method skill only on the user's request. Apply choosing-graph if graph and anchor are unset. A shared-checkpoint task passes --shared-checkpoint; its checkpoint task gets a review-only brief of each covered task's requirement and evidence. Then write the instruction.

Launch

Run launch-dispatched-agent.py in the foreground until it exits. Require confirmed: true, else follow its repair command or When a launch fails.

Handle events

Persisted status drives the lifecycle (plans: the status watcher).

• awaiting-main-agent: answer with reply-to-worker.py (verified fact or coordinator result); route a work decision to the user.
• awaiting-user-input / awaiting-authorization: point the user to the worker pane; only --intent inform stays open. Retain the task and its slot.
• done / failed / cancelled: check same-task continuation, wrap up, and return the result to the scheduler.
• Feature-branch push FYI: relay it; status stays as recorded.

Redirect, cancel, and identity repair hold the other commands.

List outstanding dispatches

Run roll-call.py (--mine for this session). Resolve an unattributed pane's ownership before acting.

Wrap up

1. Require terminal status; if the pane is closed or a live worker's report is refused, recover it. A never-launched instruction needs no status.
2. For a landed programming change, settle choosing-graph's review checkpoint first.
3. Close only the terminal worker's pane (the coordinator pane and shared tab stay open) and release every remaining lock.
4. Archive with wrap-up-task.py --app <app> --slug <slug> [--plan <plan-slug> --task-id <task-id>], then run any step its remaining_steps names.

Complete when: the dispatch awaits its next event, or is terminal, reviewed, closed, unlocked, and archived.