escalation-router

Escalation routing evaluates error complexity and directs reports to researchers when knowledge is sufficient or to humans when intervention is needed. Provide an error report; the router outputs a routing decision and structured handoff document for the next stage.

Escalate when fix-engine retries are exhausted or errors reveal knowledge gaps, API confusion, vague requirements, external dependency blocks, or prior research failure. The router identifies these conditions and signals appropriate escalation type while preserving API contracts.

The handoff document formats error analysis, routing rationale, and context for downstream agents. It structures the escalation signal with preserved API contracts and test compatibility so researchers or humans can act immediately.

Yes. The router preserves API contracts and existing tests during escalation, maintaining compatibility with current error-handling workflows while adding structured routing and handoff documentation.

The router applies decision criteria evaluating whether sufficient domain knowledge exists to resolve the issue. Knowledge gaps, library confusion, or requirement ambiguity trigger human escalation; resolvable technical issues route to researchers.

Escalation activates when retries exhaust, knowledge gaps emerge, API or library confusion occurs, PRDs lack clarity, external dependencies block progress, or prior research attempts failed. The router analyzes each condition and formats the appropriate handoff.