Token-efficient, quality-preserving model routing

Complete work with the fewest model tokens and least DRIVER-context growth that still meets the acceptance criteria. Route each task to the least expensive configured model that can own it completely, and escalate only when evidence shows that route cannot meet quality. Profiles and exact identifiers preserve approved bindings; they are mechanisms, not the product goal.

Fable/Opus/Haiku and Sol/Terra/Luna are illustrative names, not defaults or tiers. Never infer a model from one of those examples, a provider, a nickname, or a harness default.

When to Use

• Work can be decomposed so expensive-model reasoning is reserved for judgment, synthesis, and acceptance.
• Delegated research, implementation, review, or mechanical processing would otherwise inflate DRIVER context or use a stronger model than necessary.
• A user asks to set up, inspect, change, switch, clear, reset, delete, or use a routing profile.