Design · Orchestration
Difficulty-Aware Orchestration
Estimate each query's difficulty first, then adapt workflow depth, which operators fire, and which model handles it. Hard queries get more agents + a stronger model; easy ones get a shallow cheap path.
Verified against arxiv.org
How it works
Estimate each query's difficulty first, then adapt workflow depth, which operators fire, and which model handles it. Hard queries get more agents + a stronger model; easy ones get a shallow cheap path.
At a glance
TechniqueRouting
Cost leverLower on average, spends compute only where difficulty warrants
Latency leverVariable, matched to query difficulty
Quality leverHolds quality on hard queries without over-spending on easy ones
ExampleDAAO · MoMA generalised routing
When to use
Agent workflows facing a wide difficulty range, where a fixed pipeline over-serves easy tasks and under-serves hard ones.
Basis
Verified against
https://arxiv.org/abs/2509.11079 The corpus does not rewrite vendor documentation. Where copy is quoted verbatim it is marked as such and attributed to its source.