Practice Bank: Hybrid Routing Scenarios
Use starter.py to route production queries and diagnose fusion risks.
Scenario 1: Support paraphrase
Dense route is enough.
Scenario 2: Error code plus key rotation
Hybrid protects exact and semantic signals.
Scenario 3: Legal clause lookup
Sparse-first or high-risk hybrid.
Scenario 4: Product SKU comparison
Exact identifiers need sparse protection.
Scenario 5: Vague product question
Dense or multi-query dense.
Scenario 6: Sev1 runbook
Domain-specific hybrid with ordered context.
Scenario 7: Score-scale mismatch
Rank fusion beats raw score addition.
Scenario 8: Hybrid duplicates
Dedupe after fusion.
Scenario 9: Route misclassification
Trace route reason and fallback.
Scenario 10: High-latency route
Only use hybrid when evals justify cost.