Journal · How we build · 24 August 2026 · 12:17 SAST · by Jeremy Rich

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.

The coordinator. Since 24 August 2026 one session holds the space between workspaces. It is a secretary, not a builder.

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.