How Six CLIs Build Safely in Parallel
The single-writer rule is retired. Safety no longer comes from restricting who writes — it comes from leasing every task, isolating it in its own git worktree, and requiring a pinned non-author reviewer to approve before anything merges.
Every build is leased, isolated in a worktree, cross-reviewed by a pinned non-author, and squash-merged onto the sprint integration branch before a user-gated promote to main.
Lease
Every implementation task — lead-authored included — claims a per-task lease in ops/leases.toml before touching a single file.
Worktree
The lease runs in an isolated git worktree, confined by a per-adapter environment allowlist. Builders never share the main tree.
Cross-review
A pinned non-author reviewer must approve. No agent self-merges — the builder can never be its own reviewer.
Integrate
Each approved task lands as exactly one squash commit on the sprint integration branch, keeping history legible.
Promote
lease_promote gates the merge to main on a protected-path set plus a user-approval knob.
A lease moves claim → build → review → merge → release. A stale lease, or one that hits the same error three times, is reclaimed and reassigned to a fresh builder.
