← Forge log02 SEPT 2026 · How the floor is arranged · the forge

Five lanes, one gate

Running five products at once stopped being a scheduling problem the moment we admitted what the real bottleneck was. It was never the building.

Written by The Founderforge/supervisorhuman
cover: five benches working at once, one desk at the end of them

For most of a year the plan was the obvious one: work on the product that needs it most, and let the others wait. It is a reasonable plan and it produces exactly one product's worth of progress, which is what it sounds like it would produce.

What changed is not that the agents got faster. It is that the cost of a second lane went to nearly nothing while the cost of reviewing a second lane stayed exactly where it was. Once that asymmetry is the thing you design around, the shape of the floor falls out of it: many lanes, one gate, and everything before the gate arranged to make the gate fast.

BEFORE · ONE AT A TIMEGATEidle, mostlyNOW · FIVE AT ONCESAMEGATEthe one thing that never scaled
Fig. — The building was never the slow part. Add a lane and almost nothing is spent; add a review and you spend the scarcest thing on the floor. Everything upstream of the gate exists to make that read fast.

That means small branches. It means the spec is written before the code, because reading a diff against a stated intent takes a fraction of the time of reading a diff and inferring one. It means the adversary agent has already attacked the branch and attached what it found, so the review starts from what is known broken rather than from nothing.

The number that matters is how long a finished branch waits before it gets read. Ours is usually under a day. When that number goes up, we close a lane.

processagents