← Back to concept explainers

Concept Fable

Router

Conclusion first:A Router is a component that dispatches requests, tasks, or intermediate steps to the appropriate model, tool, workflow, skill, or Agent. It can make decisions based on intent, capability, cost, latency, risk, permissions, load, and policy. Semantic routing emphasizes dispatching by meaning, while Router is broader and can include rule routing, policy routing, model routing, failover, and load balancing.

Router · Orchestration component

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

The person at the city gate who doesn't fix carts but decides where they go

Twin Rivers City had four roads. The east road was fast but expensive, the west road slow but steady, the south road could carry heavy goods, and the north road was only suitable for light carts. In the past, cart drivers chose their own route at the city gate.

Experienced people chose accurately, while newcomers often went the wrong way. Once, to save time, fragile porcelain took the eastern road; the eastern road was indeed fast, but had a bumpy stone slope, and half the porcelain shattered. Another time, an urgent letter took the western road; it was safe but arrived two days late.

The city lord first posted a road-condition chart at the gate. But cart drivers had to consider cargo weight, deadlines, cost, risk, weather, and congestion. The chart grew longer and longer, yet drivers still could not be sure.

Later, a route officer appeared at the city gate. He did not repair carts or move goods; he asked only a few things: what the cargo was, how tight the deadline was, how much could be spent, whether risk or speed came first, and how each road was doing today.

After asking, he gave the cart driver a road sign. Urgent letters take the east road, porcelain takes the west road, heavy goods take the south road, and only empty carts might take the north road; in heavy rain, assignments would also be changed temporarily.

Years later, Twin Rivers City had more carts and roads. Drivers did not need to remember all the rules; they only had to hand the task to the entry point. Efficiency came from a dispatcher who understood strategy, capabilities, and costs.

The road dispatcher also explained his signs. Porcelain took the west road, not because the west road was best, but because this shipment feared bumps; urgent letters took the east road because the cost of arriving late was higher than the toll.

With these reasons, the drivers began to trust the dispatcher. The route official didn't drive for them, but matched tasks to roads at the entry point. The larger the city, the more the entry judgment reduced later rework and losses. Later, when newcomers started, the veteran drivers no longer began with abstract labels, but had them review that failure: where intuition had been relied on before, why the first fix wasn't enough, and how the new arrangement kept risk in a place that could be checked. Only when they could explain these details clearly, and point out when to keep using the approach and when to upgrade it, were they considered to truly understand the method. Later they also had newcomers practice it: first let them do it the old way and see how errors appeared; then redo it under the new rules and see which step was blocked earlier and which step left evidence. If newcomers could only recite names, they would still misuse it in similar scenarios; only those who could state the applicable boundaries, costs and remedies after failure were allowed to take jobs independently.

Reveal

This story is about: routers

A Router is a component that dispatches requests, tasks, or intermediate steps to the appropriate model, tool, workflow, skill, or Agent. It can make decisions based on intent, capability, cost, latency, risk, permissions, load, and policy. Semantic routing emphasizes dispatching by meaning, while Router is broader and can include rule routing, policy routing, model routing, failover, and load balancing.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Four paths: different models, tools, Agents, workflows or vendors
  • The driver chooses the route himself: the caller directly selects capabilities, making mismatches easy
  • Porcelain taking the fast route and shattering: task-capability mismatch causing quality or risk problems
  • Urgent Letters Take Slow Roads: Misrouting Causes Delays and Business Losses
  • The road-condition table grows longer and longer: simple static rules struggle to cover complex conditions
  • Route adjuster: Router component
  • Cargo, deadline, cost, risk, weather: routing decision signals, including task attributes, cost, latency, risk, and system state
  • Temporary reassignment: failover, degradation or dynamic routing
  • Dispatcher at the entrance: the Router centralizes governance of complex choices, making the system more controllable

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

orchestrationskillshandoffmodel routingclassifiertool selection
京ICP备2026014272号