tote.ai

이 이메일 도메인이 관측된 논문 2건

arXiv:2610.02036v3cs.AI

Global Coherence: When Every Agent Is Right and the Team Is Still Wrong - A Local-to-Global Semantic Foundation for Multi-Agent Collaboration

AI agents share code, documents, tools, and analyses. No participant sees the whole state, so every step can look right while the combined result is wrong. We call this the global coherence problem. It is a problem of state, not only of intelligence: a stronger model decides better locally, but cannot see what is missing from its context. The Observation-Aliasing Impossibility Theorem gives the exact condition. An agent can always act validly exactly when every world consistent with its context allows a common action. When look-alike worlds need different actions, no reasoning, role, message, or sample can guarantee the right one; with k such worlds whose valid actions are disjoint, the best randomized policy succeeds with probability 1/k. Finding the smallest sufficient context is NP-hard, but refinement finds one and keeps it current as rules change. A second failure survives full information: valid pieces can fail to fit into one world. The same theorem sets the conditions for coherence; sheaves and groupoids are one way to meet them. Models propose, and the harness decides what is valid. Ten studies test it. On TeamBench, teams overspend a shared budget in 5/5 runs; showing them the live count still leaves 4/5, and a harness that owns the budget leaves 0/5. Identity collisions that no pairwise check can see appear in 23 of 45 public alignment networks; split-view agents create them in 9 of 40 merges, and a network check removes all nine. A frontier LLM solves 40/40 revision tasks when it sees the deciding event; with the event hidden, no arm that reasons longer, votes, or splits into roles significantly beats chance, and a companion study replicates this on models from a second provider. In tau2-bench Telecom, after a silent revert, the harness scores 1.00 against 0.07 for call-time policy checks. Refinement keeps a sufficient context at 28% of the cost of sharing every field.

arXiv:2609.23058v2cs.AI

LazyAgent: Demand-Driven Materialization and Physical Optimization of Agentic Programs

Agent runtimes that plan before acting run every step as soon as it is ready. Neither these runtimes nor their benchmarks distinguish a step that is ready from a step the request needs, and the difference is large: across 303 requests on 154 production workflows, an eager runtime that stops once the goal is met spends 62.2% of its CPU on work the request never needed. LazyAgent is, to our knowledge, the first complete formulation of demand-driven execution for agent runtimes. Its rule: run a ready step only if the current request needs it, and keep that answer exact as the plan changes. A demanded set derived from the program decides, in one traversal with no model calls, so LazyAgent spends nothing outside the request. Because demand is defined exactly, its behavior is proved: builders know before any run where demand must save and where it must tie. The bill is known before a plan runs, so LazyAgent can act as a query optimizer to choose among candidate workflows. Measured live against that eager runtime, LazyAgent saves 51.7% and 52.1% of container time on release gates where a frontier LLM writes the patches, 12.8% of tokens on DataSciBench plans at matched quality, and 24.0% of dollars inside a live LangGraph application, with no losses. When the LLM re-plans after real code failures, it solves every solvable goal with 11.7% fewer tokens per goal. On the production workflows it saves 42.0% of CPU, ties exactly where a request needs the whole graph, and adds at most 0.43% overhead. The same set steers every physical operation: projection saves 80-89% of a shared CI step, where the identical eager control saves 0.0%. Public agent benchmarks are designed the same way as eager runtimes, so they cannot show this difference. We compose our test programs from their tasks and call on industry to build benchmarks that measure how efficiently agent workflows run.