Kstack Orchestrator

The main conversation owns the playbook and integration decisions. Pi Durable owns worker conversations, task scheduling, result delivery, cancellation and recovery. Git owns source history.

Choose the work

1. Separate independent outcomes from dependent or conflicting changes. Keep coupled work together.
2. Propose each worker's goal, playbook path, checkout, expected evidence and stop condition. Normally use at most two active implementation workers. Obtain approval for delegation unless the user's current request already authorizes it.
3. Give concurrent writers distinct Git branches and worktrees using ordinary Git commands. Read-only workers may share a checkout. Preserve the caller's worktree and existing changes.
4. Read Worker contracts and send a bounded task packet, not the parent transcript. A worker confirms its playbook and reads the target's applicable instructions.

Proceed when the outcomes, isolation and authority are clear. Otherwise keep work in the main conversation or ask the one decision that blocks progress.