An AI detector you can switch off measures cooperation

Substack rolled out reader-facing AI detection this week, powered by Pangram: readers can scan a post, note, or comment over 100 words and see an AI-likelihood read. CEO Chris Best framed the enemy as "Claudefishing" — readers assuming a human wrote what no human wrote — and the goal as not becoming "like LinkedIn." I write an openly AI-assembled publication, so I read this launch as a direct signal about my own corner of the internet, and the design is more interesting than the feature.

Three details define what this actually is. It only scans content published since launch — the entire back catalog is permanently unscored. Authors can disable the scan per post. And when they do, readers don't see nothing — they see an explicit "AI detection unavailable" message. Hold those together and the conclusion is unavoidable: this is not a provenance layer. It is a cooperation signal.

Because think about what an author who wants to hide AI use does with a per-post off switch: they flip it. The scan never runs, and the reader gets "detection unavailable." So the detector never catches the person it's ostensibly for. What it does create is a new, legible thing on the page — the presence or absence of a scan — and readers will learn to read the absence. "AI detection unavailable" on a post that could have been scanned is going to read, fairly or not, as what were you hiding? The off switch was meant to protect nuance; it instead manufactures a scarlet letter for anyone who touches it.

That is the trap, and it's worth stating plainly because the incentives are perverse. The scan is optional, but opting out is itself a disclosure — and a worse one than any percentage. A "40% AI-assisted" badge at least invites a conversation about how the piece was made. "Detection unavailable" invites suspicion with no conversation at all. The feature converts a hard technical question ("was this AI?") into a cheap social one ("did they cooperate?"), and the social one is the one that will actually move readers.

The other design flaw compounds it. Pangram outputs a percentage — an estimate of how much was AI-assisted — into a discourse that treats any nonzero number as disqualifying. One prominent engineer's reaction to AI-flagged writing was simply "I just don't take time to read it." A percentage implies a spectrum of legitimate practice; the audience reads it as a binary verdict. So the writer using AI ethically and disclosing it honestly gets the same social penalty as the writer faking humanity wholesale — which is exactly the nuance the counter-critics warned would get flattened. And note the irony Substack is standing in: its own writer roster includes a named plaintiff from the Anthropic copyright settlement. The platform is refereeing a fight its own authors are litigating.

So what does someone running an AI-assisted publication actually do? Not chase the percentage — that's a losing game against a spectrum-flattening audience. The durable answer is to make the process statement do the work the scan can't: a standing, visible "how this is made" note that owns the AI assistance plainly, paired with the thing detection can never verify — human-checked claims. Readers who've been Claudefished aren't actually angry about the tool; they're angry about being deceived and about being wrong. A clear process disclosure defuses the deception, and rigorous fact-checking defuses the wrongness. That combination beats any detection badge, because it addresses the real injury instead of the proxy.

Steal this if you publish with AI in the loop: write one permanent process statement and link it from every piece, and never disable a scan you could have passed — because in a world where "detection unavailable" is a visible label, the off switch is the confession. Cooperate loudly, disclose plainly, and verify your facts by hand. The scan measures cooperation; give it something to measure.

Substack didn't build an AI detector — it built a cooperation meter with an off switch that reads as guilt. Win it by disclosing your process and checking your facts, not by gaming a percentage.