crank

# Crank Crank executes exactly one wave. The caller selects the wave and the repair bound; crank runs that wave and returns what happened. ```text caller's wave + repair_rounds -> RPI per lane -> wave acceptance once -> evidence -> stop ``` ## Input The caller supplies all three: - **The wave** — a list of lanes, each with a write `scope`, a `brief`, and its own executable `acceptance`. - **`repair_rounds`** — the caller's repair bound, forwarded unchanged to every lane. Crank neither chooses it nor spends it. - **The wave acceptance** — the one command set that judges the wave as a whole. If a lane arrives without a scope, a brief, or an executable acceptance, report the wave as unrunnable and stop. Crank does not shape the missing part itself. ## Contract 1. Read the caller's wave as given. Do not select, extend, drop, or re-rank lanes; the wave arrives already decided. 2. Partition the lanes. Two lanes may run in parallel only when their write scopes are disjoint **and** their regen surfaces (generated outputs, mirrors, manifests) are disjoint. Any shared surface serializes them; unknown overlap counts as overlap. 3. Invoke [`rpi`](../rpi/SKILL.md) once per lane with that lane's intent, scope, acceptance, and the caller's `repair_rounds`. Each lane's traversal owns its own repair loop. Crank never repairs a lane itself, never re-invokes a returned lane, and never re-plans one. 4. Run the wave acceptance once, after every lane has returned. ...