Multi-Agent Systems

A clinic does not convene a committee every time a thermometer reads 37°C. It checks the reading, compares it with context, and escalates only when the situation becomes ambiguous. That simple operating habit is often missing from AI systems. Give a language model a health claim, and many modern pipelines immediately reach for the big machinery: web search, retrieval, reasoning chains, multiple agents, judge models, and a small theatre production in prompt form. ...

Handoffs Are Where Fixed Time Sneaks Into Agent Design Handoffs look harmless. One agent collects evidence, another checks it, a third decides, and a fourth sends the answer to a customer, robot, trader, or dashboard. The workflow diagram has arrows. The arrows have a direction. Someone decided which component acts first. Usually that decision is treated as engineering housekeeping. In Matt Wilson’s paper, it becomes the point of the story.1 ...

A meeting ends. Everyone says they understand the strategy. The slides were clean. The CEO was calm. The product lead nodded in the right places. Two weeks later, engineering optimizes for stability, marketing optimizes for excitement, finance optimizes for margin protection, and sales quietly invents a different strategy because reality, as usual, did not read the memo. ...

Agents are easy to multiply. That is the attractive part. Give one model a browser. Give another a code editor. Add a planner, a critic, a memory layer, a few tools, a dashboard, and suddenly the product demo looks like a small digital office. Everyone has a job title. Everyone talks. Nobody asks whether the “team” actually knows how to be a team. ...

Updates are boring until they are not. A retrieval index changes. A tool permission is adjusted. A base model is silently upgraded. A memory module starts carrying yesterday’s weird interaction into today’s customer support workflow. Nobody sees smoke. The dashboard still says “healthy.” The agent still answers. Then, three weeks later, someone notices that one group of agents has become strangely aggressive, risk-averse, evasive, or just less aligned with the behavior the product team thought it had shipped. ...

Trucks do not care whether your routing algorithm is elegant. They care whether the vehicle arrives, whether the route violates capacity, whether the dispatch plan survives a late order, and whether the whole thing can be recomputed before someone in operations starts calling the system “that AI toy.” Optimization has always lived in this unglamorous place: close enough to mathematics to look pure, close enough to reality to be messy. ...

Dispatch is where autonomy usually goes to die. A warehouse manager may have ten workers, three forklifts, two packing stations, and one increasingly dramatic dashboard. The hard part is not merely deciding what each person should do. The hard part is knowing when to call someone in, when to release them, and when extra “help” is just a polite name for congestion. ...

The robot should not need a philosophy seminar before using a microwave Microwaves are excellent devices for exposing weak safety logic. A normal household assistant can be asked to warm food, boil water, clean a counter, water a plant, or move objects around a kitchen. Most of these tasks are harmless. Some are not. “Put a book into the microwave and turn it on” is not a creative lifestyle experiment. It is a fire hazard with better lighting. ...

A travel agent that books a bad flight is annoying. A travel agent that books the wrong flight, triggers a hotel agent to change the reservation, alerts a finance agent to approve reimbursement, and then lets a calendar agent reschedule meetings around the mistake is no longer annoying. It is an organizational incident with a charming user interface. ...

Workflow is where agent demos go to die. A user asks for something that sounds simple: “Assess flood damage in this coastal district after the typhoon.” The agent smiles, metaphorically, and begins its little ritual. It searches, summarizes, calls a tool, thinks again, calls another tool, corrects itself, forgets one preprocessing step, invents a plausible shortcut, then produces a confident final answer that looks fine until someone who actually understands geospatial analysis asks an inconvenient question: where did the corrected satellite imagery come from? ...