harness-dispatch

Parallel workflow tasks are delegated to fresh workers with explicit allowed write scopes, while the primary agent retains plan ownership, integration judgment, and final verification. This prevents cross-task interference and ensures auditable governance.

Disjoint domain delegation requires clear domain boundaries, explicit allowed write scopes, and predefined verification commands. The primary agent assigns these scoped tasks to fresh workers and performs integration checks to ensure parallel work remains safe and coordinated.

Parallel dispatch is needed when a plan contains multiple disjoint domains, such as code changes and documentation updates, that can proceed concurrently. It allows controlled parallelism while maintaining final verification and integration judgment.

Dispatch governance requires clear domain boundaries and explicit allowed write scopes to prevent uncoordinated changes. Plans with overlapping write scopes are not suitable because they risk cross-task interference during parallel execution.

Primary agent verification works by running predefined verification commands and integration checks after workers complete their scoped tasks. The primary agent retains ownership to review worker outputs and ensure uncoordinated changes do not compromise the plan.

Limitations include the strict requirement for clear domain boundaries and explicit allowed write scopes. Without disjoint domains and predefined verification commands, parallel task delegation risks uncoordinated changes and fails the integration checks required for safe governance.