Parallel delivery

Parallelism is useful only when ownership is clear.

Invariants

• One writer = one worktree = one branch.
• Two writers never edit the same checkout.
• A local writer and a cloud writer never push to the same branch concurrently.
• Read-only exploration/review can share a source view when appropriate.
• Handoffs use exact commit SHAs, not "latest branch".

Procedure

Before dispatch, read and apply bounded coordination: one coordinator, leaf workers, finite dispatch and correction allowances, deadlines, verified cleanup, and explicit review completion. Keep completed run records outside Git.

1. Start every writer from a known base SHA.
2. Give each writer a bounded task and its own worktree.
3. Create a retained branch only for work that should survive the disposable worktree.
4. Require local validation before handoff.
5. Record base SHA, head SHA, branch, validation, unresolved risks, and untested areas.
6. Send the candidate SHA through the required independent gates.
7. Integrate only reviewed SHAs.
8. Discard failed worktrees/branches when no useful artifact remains.

Give each assignment an attempt identity and explicit dependencies. Track partial, blocked, ready-for-review, and reviewed states separately from whether an agent thread has finished. A delayed result or approval remains attached to its original attempt and candidate; it cannot approve a replacement.

When a writer cannot commit because Git metadata writes are denied, preserve its exact base, scoped patch including new files, and actual checks for the authorized coordinator. Require a recorded candidate commit and appropriate validation before review or integration. Do not turn the denial into an unrestricted-permission default.

A worktree prevents checkout corruption; it does not prevent semantic conflicts. If two tasks depend on an unstable shared interface, resolve that contract before maximizing parallelism.