What problem does it solve? When a build pipeline step gate fails, models either dump raw error traces or thrash through unbounded fixes that compile but violate the architecture. This Skill replaces both failure modes with a disciplined router that decides, for every gate failure, whether the fix is bounded and nameable (autonomous retry) or unbounded and doctrine-violating (hard halt to the user). ## Core Features & Use Cases - Bounded vs. unbounded routing: Classifies failures by whether a named, contract-preserving fix exists, not by which subsystem complained. - Capped autonomous Debugger loop: Runs at most 3 retries, feeds the full batched cargo check output to the Debugger, re-gates every retry against the same gate, and logs each attempt to a retry ledger. - Hard halt with a trail: Suspends the build, names the violated doctrine, and surfaces the retry history so the user decides next steps. - Use Case: A Rust build step fails its gate with a borrow-checker error whose only compiling fix would leak Arcs and break bus discipline. The router recognizes this as unbounded thrash, halts the build, and reports the violated doctrine instead of letting the loop ship working-but-wrong code. ## Quick Start When a step gate returns Fail, invoke the ordo-error-router skill to classify the failure and either run the capped Debugger retry loop or halt with the full error trail.
