Context Routing
One mega-context for every intent wastes tokens and leaks the wrong tools.
Different briefings for legal vs support. Same company, different folders.
Visual Workflows
Start here — scroll inside each diagram frame to explore, then use + / − to zoom up to 200% if needed.
Overview
Scroll inside the frame to explore · use + / − to zoom up to 200%
Scroll inside the frame to explore · use + / − to zoom up to 200%
This turn
Scroll inside the frame to explore · use + / − to zoom up to 200%
Different briefings for legal vs support. Same company, different folders.
Key Takeaways
- 1.Routing sends different tasks to different context packs or models.
- 2.A refund pack is not a search pack.
- 3.Cheap model for classify, expensive model for the hard step.
- 4.Wrong pack is a silent failure.
- 5.One mega-context for every intent wastes tokens and leaks the wrong tools.
Learn elsewhere
- →Model Routing — Phase 21
Real Example
Scenario
Routing: pack only what this turn needs.
What you would do
In Context Engineering, apply Context Routing to this scenario: Routing: pack only what this turn needs. Identify the inputs, run the technique, validate the output, and note one thing you would monitor in production.
Commands
Commands to Remember
Routing sends different tasks to different context packs or modelsA refund pack is not a search packCheap model for classify, expensive model for the hard stepWrong pack is a silent failure
Cheat Sheet
Quick recap
quick ref- •Routing
- •Budget
- •Don't dump
Common Mistakes
- ✕Skipping evaluation for Context Routing before production
- ✕No logging or tracing around context routing steps
- ✕Ignoring cost and latency implications