Orchestrate Implementation

Worktree isolation patterns are adapted from using-git-worktrees and David Ondrej's git-worktree. Test-seam patterns are adapted from Matt Pocock's tdd, tests, and mocking guidance (all MIT). Exact pins are recorded in sources.json.

Shared-write separation, smallest-safe-decomposition, and bounded child context are adapted from Cursor's poteto-mode at commit 93b00b89ef425a9c1bac0d0b317dfc49c930ac99 (MIT, Copyright (c) 2026 Cursor).

Ownership and authority

The current session is the parent. It owns scope, decisions, routing, finding disposition, acceptance, candidate assembly, and the final conclusion. Children implement or review bounded tasks; their reports are evidence, not acceptance or publication authority. Delegate only when the current request or applicable instructions authorize it. All child roles use Pi, including workers, fixes, scouts, reviewers, and advisors. Hosts manage placement and lifecycle; model providers inside Pi are not alternative agent runtimes.

Use the smallest safe decomposition. One bounded issue can have one writer; parallel writers need independent owned surfaces and separate worktrees. Scout only when context gathering has a concrete job. Do not add workflows, specialists, reviews, or checks merely to fill stages. Children do not delegate further unless the parent explicitly authorizes fanout.

Modes

State the requested/configured mode, otherwise supervised:

• plan-only: read inputs and outline tasks/briefs; no source edits, worktrees, or child launches.
• supervised: implement, validate, and review, including disposable candidate assembly; pause before target integration.
• autonomous: keep the same loop moving while safe work is ready; neither the label nor candidate assembly grants target integration or publication authority.