📖What it means

The two lanes an initiative can be executed in. PLANNER mode is the autonomous build pipeline: Elrond plans phases and steps, Merlin's step-execution machinery runs them, and the pipeline's own reviewers verify — no human in the execution loop. BYPASS mode is operator-driven: with admin approval, Orion executes the initiative directly, skipping the planner's orchestration but NONE of the standards — bypass work still opens executions in the bypass book before code starts, follows the template checklists, updates initiative status throughout, and passes the same close gates (twin review, close-audit). Bypass = planner skipped, standards kept. Conceptually: bypass is the delivery lane; the pipeline is the research lane that earns lanes back by proving templates.

📖Easily confused with

[{"term": "Bypassing the standards", "distinction": "Bypass skips the PLANNER, never the standards \u2014 same records, same review, same substantiated criteria."}]

📖Nuance

Carol: while the pipeline is not yet self-hosting, ALL Carol initiatives go via Orion bypass per the cookbook; filing mode defaults to planner and must be confirmed with Ninad before opening an execution.

📖Also called

- execution mode
- bypass mode
- planner mode

📖Filed under

Category: work.

Service: Build Initiatives.