Goal
Define the operator-facing product experience for model routing and query classification.
Why This Matters
The runtime already supports route hints and classification rules, but that does not automatically make the feature easy to adopt. Corvus needs a clear product story for:
- how users discover the capability,
- how they configure it safely,
- how they validate routing behavior,
- and how they reason about fallback behavior.
Evidence in Current Repo
- Runtime support exists in
clients/agent-runtime/src/config/schema.rs, clients/agent-runtime/src/agent/classifier.rs, and clients/agent-runtime/src/providers/router.rs.
- There is no clear docs surface today in the web docs for model routing and query classification as a first-class feature.
Questions to Close
- Where should routing/classification be documented in the docs site?
- What examples should be considered canonical?
- What diagnostics or doctor output should operators rely on?
- How should fallback behavior for unknown hints or unmatched rules be explained?
- What guardrails should exist to reduce misconfiguration risk?
Acceptance Criteria
- The operator-facing docs and UX expectations are defined.
- The minimum examples and diagnostics story are defined.
- Follow-up docs and UX work can be split cleanly.
Goal
Define the operator-facing product experience for model routing and query classification.
Why This Matters
The runtime already supports route hints and classification rules, but that does not automatically make the feature easy to adopt. Corvus needs a clear product story for:
Evidence in Current Repo
clients/agent-runtime/src/config/schema.rs,clients/agent-runtime/src/agent/classifier.rs, andclients/agent-runtime/src/providers/router.rs.Questions to Close
Acceptance Criteria