Agent orchestration

The third-largest theme in the research: 194 of 268 documents, 70 organizations. Decomposed into 6 topics, each with its own issues, evidence and steps.

194documents in the theme
12issues named
45sourced citations
17organizations cited
0sourced statistics

The topics

Each opens a dossier with the same shape: what the state of it is, the issues ranked by how many independent organizations name them - or marked as our own analysis where none does - the disagreements, the numbers, and the concrete steps under each remedy.

Multi-agent systems

Several agents on one problem, and the coordination that costs more than it looks.

  • Multi-agent systems work largely by spending more tokens, and the budget rarely says so 3
  • Multi-agent is being adopted as a maturity stage rather than chosen for a problem 1

48 documents · 27 organizations · 2 issues · 7 steps

Tools & integration

What the agent can reach, how it is granted, and what breaks at the boundary.

  • Tool definitions are permission grants, and are being designed as features 2
  • Three different kinds of tool are being governed as one ours

37 documents · 23 organizations · 2 issues · 8 steps

Autonomy limits & human control

How far the system may act alone, and what stops it.

  • Risk to people rises with autonomy, and the trade is almost never stated 4
  • Autonomy is being set once, as a binary, instead of earned incrementally 2

21 documents · 17 organizations · 2 issues · 8 steps

Context & memory

The finite budget every agent runs against, and what happens when it fills.

  • Context is a finite budget, and long-running agents spend it without anyone watching 2
  • Cost compounds invisibly because one request is not one request 2

16 documents · 13 organizations · 2 issues · 8 steps

Reliability & failure modes

Non-determinism, compounding error, and how agent failure differs from software failure.

  • Non-determinism breaks the testing process the organization already has 2
  • There is no accepted way to evaluate an agent, so every team invents one 1

15 documents · 12 organizations · 2 issues · 8 steps

Agent, or just a workflow?

The question most of the material says to ask first, and most deployments skip.

  • An agent is being built where a predefined workflow would do the job 3
  • Agent frameworks hide the one thing you most need to control 1

6 documents · 5 organizations · 2 issues · 8 steps

Where the sources disagree

No contradictions recorded yet.