AI Orchestration

Budget is where many impressive AI demos go to become ordinary software. A model can reason longer. It can sample more. It can revise itself, compare candidates, aggregate outputs, and repeat the whole ritual until the invoice starts looking like a small infrastructure project. The obvious response is to ask whether the strongest model should simply do all of this work. Obvious, yes. Economically elegant, not quite. ...

A supercomputer is not impressed by a clever chatbot. That sounds rude, but it is also a useful starting point. Modern high-performance computing systems are built to run thousands of jobs in parallel, move data across specialized hardware, and tolerate the minor chaos of long simulation campaigns. A language model, by contrast, is very good at interpreting a request, proposing steps, and calling tools. Left alone, it often behaves like an overworked project manager with one phone line: think, call a tool, wait, think again, call the next tool, wait again. ...

Meetings are expensive, even when the employees are synthetic Every organization has seen the meeting that should have been an email. Everyone attends, everyone hears everything, and somehow the person who needed one precise fact receives it after forty minutes of theatrical alignment. Multi-agent AI systems often reproduce the same disease, only faster. A coding agent, a testing agent, a research agent, a planning agent, and a manager agent are assembled into a “team.” Then the system lets them talk through a fixed pipeline, a broadcast channel, or a reusable graph. It feels collaborative. It is also a polite way to dump irrelevant context into everyone’s prompt and call the mess intelligence. ...

Maps are easy until someone asks the system to reason over them. A person looking at a maze does not merely “see” it. They clean up the visual clutter, identify obstacles, locate the start and goal, infer the grid structure, compute a path, and then translate that path into actions. Some of this is perception. Some is spatial reasoning. Some is symbolic logic. Some is visual transformation. The sequence matters. The order matters. And no, asking one large multimodal model to “think carefully” is not quite the same thing, however confidently the demo smiles. ...

TL;DR for operators Most enterprise data work is not blocked by a lack of models. It is blocked by orchestration. A company may already have Spark, Pandas, SQL engines, notebooks, dashboards, semantic layers, data lakes, vector stores, ETL jobs, monitoring tools, and a growing pile of LLM wrappers. The awkward part is deciding which tool should act, in what order, on which data, under which assumptions, and how to recover when the first plan fails. This is the gap the Data Agent paper tries to formalise.1 ...