“Every feature gets broken into chunks, and each chunk has exactly one owner lane. One chunk = one branch = one PR. Lanes never co-own work and never talk to each other. [...] The real break point is two lanes wanting the same file. When that happens, the second lane leaves the file alone, saves its diff for later, and picks it up after the first PR merges.”
Quote · x.com
From “16 lanes: one owner per chunk, and the second lane yields a contested file”, found 2026-10-27.
Scope caveat: a solo founder, but at 190 merged PRs a week the failure modes are real. The design is zero lane-to-lane messaging: coordination happens in the brief ("carries #N" cherry-picks for unmerged dependencies, "blocked" instead of guessing) and contested files are serialised by yielding. He chose area ownership because "agents overwriting each other's files was a bigger problem for me than idle lanes", and says he is still tuning how lanes share load, so the cost of ownership is idle capacity. Contrasts with the published claim-board and negotiation approaches (Agensh, Concord).
- Plan
- Isolate
- Coordinate
AI-drafted