Three lanes, one system.
Cadence groups every role into one of three lanes. The split isn’t about reporting structure. It’s about what each group owns. One lane sets direction, one delivers value, and one makes delivery possible while pushing AI maturity forward.
The rest of the handbook is easier to read once the lanes are in your head. Every event, artifact, and escalation path comes back to which lane is acting and which is watching.
Lane · Nº 01
Align
Direction, priority, value.
Product leadership and operations leadership.
What it owns
- Strategy and priorities
- Conflict resolution when work competes
- Ownership of the value created
How it operates
Watches signals from Deliver continuously. Can call a strategic pivot at any moment.
Lane · Nº 02
Deliver
Idea → working product, in flow.
Stable pods of 3–4 people working with AI agents.
What it owns
- Turning briefs into shipped, validated value
- Observability of their products
- Clean signals from devops, productops, and market research
How it operates
Runs in continuous flow, paused only by the four scaled events.
Lane · Nº 03
Enable
What delivery runs on.
Platform eng, harness eng, AI training, shared services.
What it owns
- Tools and patterns Deliver depends on
- Shared services across the org
- The AI Guild, the org's AI standards body
How it operates
Like Align, watches signals and can call a pivot. Routes it through communities of practice.
Lane Nº 01
Align
Align is where strategy turns into priority. Product leadership and operations leadership sit together here. Not as a steering committee that meets quarterly, but as a standing group that owns the value the org is creating.
What Align owns
- Strategy and priorities. Align decides what matters next. The output is direction the other lanes can act on without re-litigating.
- Conflict resolution. When two pieces of work compete for the same pod, the same budget, or the same week, Align is the body that decides which wins.
- Ownership of the value created. Pods ship work; Align owns whether the work moved the numbers the org said it cared about.
How Align operates
Align watches signals coming up from Deliver continuously, not on a quarterly cadence. When something on the ground changes the calculus, it routes a pivot through the usual org channels: leadership announcements, written direction, updated priorities. That mechanism is sometimes called “the red button” (covered in the Events chapter).
Lane Nº 02
Deliver
Deliver is where the work happens. It’s organized into stable pods: small, AI-powered teams that carry an idea all the way to shipped, validated customer value. Most of this handbook is, in one way or another, about how the rest of the org keeps Deliver effective.
What Deliver owns
- End-to-end product delivery. From a product brief through implementation, validation, and the signals that come back from real users.
- Observability. Pods are responsible for ensuring the product they ship can be observed in production. Without observability the rest of the system has nothing to inspect.
- Clean signals. Across devops, productops, and market research, pods make sure the data flowing back is clear enough to drive decisions at the next Signal Inspection.
How Deliver operates
The default state is continuous flow. Pods pick from their prioritized backlog, plan, implement, and ship. The four scaled events are the only moments where flow pauses for system-level alignment. The Pods chapter describes pod composition; the Events chapter describes the cadence.
Lane Nº 03
Enable
Enable is everything pods rely on but shouldn’t have to build for themselves: platform engineering, harness engineering, AI training, shared services. The lane exists so Deliver isn’t rebuilding the same plumbing in every pod.
What Enable owns
- Tools, patterns, and shared services. The CI/CD harness, identity, policy enforcement, managed model endpoints, vector stores, agent runtimes, internal libraries.
- AI training and capability uplift. Practical training, working sessions, and paired learning: the actual work of moving pods up the AI maturity curve.
- The AI Guild. The standards body for AI in the org. The Guild lives inside Enable and tracks AI maturity across five dimensions (covered in its own chapter).
How Enable operates
Enable watches the same signals Align does, but it intervenes differently. Align routes pivots through top-down communications; Enable routes them through communities of practice. A change in agent governance, a deprecated shared pattern, a new evaluation requirement: these spread through the AI CoP, not through a memo.
How the lanes connect.
The lanes aren’t parallel tracks. They form a loop. Align sets direction, Deliver acts on it and produces signals, and Enable equips Deliver while propagating standards. Both Align and Enable watch what comes back, and either can call a pivot at any time.
Read this next
The Pods chapter zooms into Deliver — what a pod looks like inside, how its inbound and outbound agents work, and how multi-pod coordination happens without restructuring. The Events chapter describes the four moments where Align, Deliver, and Enable reconnect.