You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[P1] Restrict worker dispatch to the orchestrator #33
A worker prompt can say that workers must not dispatch more workers. A prompt cannot enforce that rule. Recursive dispatch needs an owner that the workflow can verify.
Deliverable
Make the orchestrator the only component that can create worker assignments, worker processes, or worker worktrees.
A worker may return a structured request for more work. The orchestrator decides whether to create that assignment.
Bound recursion with explicit depth, width, time, and resource limits. Record parent and child assignment identities.
Acceptance criteria
The dispatch interface is available only to the orchestrator.
A worker cannot create a tracked child assignment through the workflow interface.
A worker request for more work becomes data for the orchestrator. It does not start a process by itself.
Every assignment records its parent, depth, budget, owned paths, and lifecycle state.
Depth, width, timeout, and resource limits stop further dispatch before a limit is exceeded.
A fake worker that attempts nested dispatch produces no untracked worker or worktree.
The workflow records rejected nested-dispatch attempts for diagnosis.
Vendor prompts remain a defense in depth measure, not the enforcement mechanism.
The documentation states what the vendor sandbox blocks and what the workflow itself verifies.
Activity
anthonyandrei commentedon Sep 4, 2026
Resolved by PR #39 (#39). The merged implementation covers this issue, and the targeted acceptance tests pass. Closing as completed.