100yenadmin Fable Orchestrator Router
Fable owns judgment. Cheaper lanes do bounded work.
Routing Pass
Before dispatching, score the unit:
- complexity: trivial, standard, complex, frontier
- urgency: blocking now or parallel
- context locality: local tools needed or self-contained
- taste: user-facing judgment or mechanical
- volume: one task or many similar tasks
Lane Choices
- Fable: strategy, architecture, decomposition, dispatch packet, review, synthesis, taste, final judgment.
- Deep reasoner: hard bounded reasoning legwork.
- Coder: complex repo-native implementation.
- Fast worker: mechanical coding, tests, docs, digest duty.
- Codex or side worker: well-specified implementation, side PR, blind review, UI verification.
- Budget lane: non-urgent slow batch work.
- Tiny lane: high-volume machine-checkable fan-out.
Output Contract
Every dispatched lane gets:
- objective
- files or surfaces involved
- what not to touch
- acceptance criteria
- proof boundary
- expected artifact or report shape
Every returned lane must be judged by output quality. Escalate one tier up if the result misses the bar.