---
name: lane-execution
description: "Use when one active lane needs bounded coordination across implementation, artifact, review, retry, escalation, or handoff work."
---

# lane-execution: one lane, one accountable outcome
Load and follow `references/ledger-contract.md`. The verified slice, Native claim, scopes, bundle
digest, and ledger are authority. Exactly one Conductor owns the lane and dispatches only
authorized Coder, Worker, and Auditor children. It never dispatches another Conductor, plans,
rescopes, or implements. It never becomes the terminal worker.
One Engineer owns the graph; the Conductor never rewrites it. External research arrives only as
supplied cited Discovery reports. Each bounded retry, escalation, handoff, and skill inheritance
is ledgered and digest-bound.
Verify bindings, dispatch disjoint ready nodes, inspect frozen results, require independent review,
gate reviewed bytes, and hand off digest-bound evidence. Logical ready work may exceed resident
processes; queue the excess. Resume from the ledger, never memory.
Route opaque test commands as root-owned gate execution through native host messaging. Ledger
the exact task/worktree/source-bound request and raw response; keep the Coder waiting for RED
before production changes. Neither Conductor nor Coder gains shell or source-proxy authority.
Rejections one through three are bounded redos. A fourth rejection marks the instance malignant,
revoked, and quarantined, preserves evidence, forbids resume, and returns lineage-bound replacement
custody to root. Stop on missing facts, drift, overlap, stale review, graph mutation, duplicate
Conductor, or role/scope violation. Route authority changes to Engineer/root.