Model Orchestration

TL;DR for operators GRADE treats a collection of language models less like a brainstorming circle and more like an operations team with an unusually strict meeting policy. For each query, the system learns: how far the request should travel through the hierarchy; which expert agents should be activated; which agents should be allowed to read one another’s work; which branches should be discarded before the final answer is assembled. That restraint is the paper’s most important result. The winning configuration is not the one that activates every model and encourages maximum communication. Fixed three-agent routing beats fixed five-agent routing. Allowing every agent pair to communicate reduces MMLUPro accuracy by 2.1 points relative to the learned communication setting. Easy questions can bypass the expert pool entirely. ...

Opening — Why this matters now AI reasoning has become the software industry’s favorite magic word. Every product now claims to “reason,” usually after adding a longer prompt, a larger model, and a pricing page with the emotional warmth of a hospital bill. But three recent arXiv papers point to a more useful conclusion: reasoning is not a single capability that lives inside one heroic model. It is becoming a system architecture. ...