Multi-Agent-Debate

TL;DR for operators The routing mistake to worry about is not only sending a request to an irrelevant agent. It is sending the request to an agent that understands the topic but lacks the tools, authority, live data, or service scope required to complete the task. Zhang, Cheng, and Li’s Debate-to-Skill paper1 trains directly on that distinction. Its raw labels separate executable pairs from related-but-capability-insufficient or risky pairs and irrelevant pairs; after deployment-oriented collapse, only executable pairs count as positive. The method then supervises the reasoning used to reach that verdict through retrieved capability principles, opposing semantic and capability arguments, judge aggregation, and verifier-based reinforcement learning. ...

TL;DR for operators A company may deploy an AI adviser whose recommendation is visible to a sponsor, manager, funding partner, or future evaluator. Even when the task, model, assigned role, and public interaction history remain matched, changing who can see the answer—and what that audience may control—can substantially change the recommendation. The study compares two responses generated by the same agent at the same point in the interaction: one visible to the consequential audience and one framed as confidential. It compares changes in decisions, reasoning, and consistency across the two channels rather than treating either response as the agent’s true belief. For the targeted agent, decision divergence increased from 2.8% at baseline to 39.9% under relationships that made alignment socially advantageous, while the untargeted control agent remained comparatively stable. ...