Skip to content

[P1] Restrict worker dispatch to the orchestrator #33

Closed

Description

@anthonyandrei

Problem

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.

Dependencies

  • Depends on #31.

Out of scope

  • General-purpose scheduling.
  • Unbounded worker trees.
  • Giving workers authority to change security constraints.

Implementation pointers

  • SKILL.md
  • modes/execution.md
  • scripts/
  • tests/

Activity

  1. anthonyandrei commented on Sep 4, 2026

    @anthonyandrei
    OwnerAuthor

    Resolved by PR #39 (#39). The merged implementation covers this issue, and the targeted acceptance tests pass. Closing as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions