The Planner decides what can run together
Planning produces task IDs, responsibilities, file scopes, and dependencies. PiGO rejects unknown, self-referential, and cyclic dependencies before a Worker starts.
MULTI-AGENT DEVELOPMENT
Parallel work is not more chat windows.
PiGO converts a request into engineering tasks with dependencies, file scope, and completion conditions. Independent work runs in separate worktrees; dependencies and path conflicts determine execution waves.
Conflict detection happens before execution
When two tasks declare equal or nested file paths, they cannot share a parallel batch. Concurrency follows explicit boundaries instead of optimistic assumptions.
Every result returns to an integration branch
Sub-agents commit inside isolated worktrees. The Integrator assembles outcomes in a controlled order while failures, commit hashes, and integration state join the same run history.
IMPLEMENTED, NOT IMPLIED
Controls present in the implementation
- Dependency cycle rejection
- Declared file-overlap checks
- Conflict-free execution batches
- Isolated worktrees and agent commits
- Integrator state and conflict reporting