Five lanes per developer, and a coordinator between them
Each developer on LedgerTM works several lanes at once. A lane is a piece of implementation work in its own isolated workspace, run by an AI-assisted session. The developer stays in the loop on every one.
Why five. Five lanes is a balance we arrived at, not a hard limit. With fewer, the developer sits waiting on builds and tests. With more, questions queue faster than one person can answer them, and quality slips. Five is where we found the two meet. Parallel work is fast. The space between the workspaces is where it goes wrong.
The problem. Before the coordinator, we saw the same failures again and again.
- Finished work sat unmerged. One morning showed nine branches in progress and nine merged branches nobody had tidied.
- The status of a design drifted from reality. A design read “Accepted” while its work was 39 commits along.
- Each workspace asked its questions in its own window, and waited until someone happened to look.
- Good follow-up ideas from a finishing session evaporated if nobody was watching.
The coordinator. Since 24 August 2026 one session holds the space between workspaces. It is a secretary, not a builder.
- It never writes code. It does not edit the product or the tests. Merging, pushing and anything destructive happen only on the developer’s word.
- One place for questions. A workspace that needs a decision sends it to the coordinator. The developer answers in one pane, not one per lane.
- Nothing lost. Every follow-up a session suggests goes into a findings queue with a number. It is scheduled or dismissed, never forgotten.
- A heartbeat. On each tick the coordinator reads the real state from git and the design records. It repairs status drift, cleans up merged branches and keeps session titles readable.
- Standing permissions, in writing. If the developer has written that work may land when its tests are green, the coordinator lands it. Otherwise it asks.
Proof. In its first two days of use, eleven designs shipped across four releases, with no accident between workspaces.
Why it matters. Each developer delivers what would otherwise take a small team, without a project manager. The throughput comes from parallel lanes of AI-assisted implementation. The safety comes from a coordinator that watches, routes and records, and never builds.
Written by Jeremy Rich.