📖What it means

A route work travels along to get executed, and therefore also a route accountability travels along. Carolverse has three: the planner (the autonomous pipeline), the Orion bypass (the operator's own CLI) and the Albus bypass. A lane holds no money and no subscription of its own: it carries one or more TRACKS, and the track is what carries the budget and the subscription. Choosing a lane is therefore choosing WHO executes the work and under what accountability — not automatically choosing a cost, since two lanes may run on the same subscription and their costs differ only where their tracks differ.

📖Easily confused with

[{"term": "mode", "distinction": "Not a MODE: a mode is what an initiative REQUESTS at filing; the lane is the route that actually runs it, decided by the escalation ladder. Not a TRACK: the track is the thing that carries budget and subscription, and one lane can carry more than one. Not a SUBSCRIPTION: lanes may share one. Not a PATH either: DIRECT PATH and SHARED PATH are about how a single conversation TURN is composed, and carry no initiative, mode or escalation ladder. The code calls the chat one \"Carol's lane\", which is the source of that confusion."}]

📖Nuance

Carol: three lanes, but FOUR lane-aligned tracks on the initiatives service — Planner (owner Merlin), Planner - Escalated (owner Albus, the rescue of failed planner work), Albus Bypass (owner Albus) and Orion Bypass (owner Orion). Which subscription those tracks run on is a dated decision kept in the cookbook, never a property of the lane — a lane whose track is re-pointed is the same lane.

📖Also called

- execution lane
- route
- pipeline lane

📖Filed under

Category: work.

Service: Build Initiatives.