📖What it means

How many initiatives one execution lane may run at the same time. The limit belongs to the LANE, and each lane has its own: the planner lane and the Albus bypass lane are one each, to be raised if those lanes start delivering results.

For the OPERATOR'S BYPASS LANE the limit is NOT DEFINED AND NOT APPLICABLE — which is not the same as unlimited. A surface must say 'not applicable' in words rather than print a number or an infinity sign, because an infinity reads as a cap that happens to be large. A human is in the loop on every action of that lane, so the limit that stops an autonomous lane compounding on a failure has nothing to bind.

The lane that counts is the lane that OWNS the work, not the one performing it: a ladder rescue carried out by Albus's runner is the planner lane's, so it fills a planner slot and leaves Albus's own free.

📖Easily confused with

[{"term": "Blocked-initiative limit", "distinction": "Concurrency is how many may RUN at once; the blocked limit is how many may be STUCK before the lane halts."}, {"term": "Dispatch cap", "distinction": "One pick per tick is the shape of a runner's loop, not a governance limit on the lane."}, {"term": "Unlimited", "distinction": "The operator lane's limit is NOT APPLICABLE, not unlimited \u2014 the concept does not apply, rather than applying with no bound."}, {"term": "Lane ownership (the doer is not the owner)", "distinction": "Ownership decides WHICH lane's limit applies; this term is the limit itself."}]

📖Nuance

Ninad's ruling, 2026-09-05 (CLI-350). Before it, Albus's runner treated one claim in flight as one claim of ANY kind, so a ladder rescue — planner-lane work by cookbook 1586 — stopped his own urgent and wish work, and his urgent work stopped a planner rescue. Each lane also kept its limits as literals in its own module; they are now derived from one place (cookbook 1126).

📖Also called

- concurrency cap
- lane concurrency
- max concurrent per lane
- one at a time

📖Filed under

Category: work.

Service: Build Initiatives.