Deterministic vs perplexity detectors: why false positives happen

Two tools can both claim to catch AI writing and work in completely different ways. A perplexity detector reads a passage and estimates how likely it is to be machine-written. A deterministic gate reads the same passage and reports whether a specific tell is literally present. That difference is why one produces false positives and the other does not, and it is the whole reason de-AI gate is built the way it is.

The false-positive paradox

A perplexity detector scores structure. It asks how predictable the wording is, and treats smooth, predictable text as probably machine-written. The problem is that plenty of careful human writing is smooth and predictable too, so it gets flagged. The failure is not a bug to be patched; it is what scoring probability does.

A 2023 Stanford study by Liang and colleagues found that widely used GPT detectors misclassified about 61 percent of essays by non-native English writers as AI-generated, while rating native-English essays as human. That same year OpenAI withdrew its own AI Text Classifier, citing low accuracy. When the decision is a probability, a share of real human writing is always caught in the net.

Deterministic tell-matching

de-AI gate does not estimate anything. It reads your files and checks them against a fixed catalog of literal tells: specific characters and specific phrases. If the em dash is in the file, that is a fact. If it is not, there is nothing to flag. There is no probability in the loop, so there is no probability to be wrong about.

That is the trade the gate makes on purpose. It will not guess that a passage feels AI-written, because guessing is exactly what generates false positives. It reports only what is verifiably present, which is what makes it safe to block a build on.

Side by side

The two approaches differ on every axis that matters for a team deciding whether to trust the result.

• How it decides: a perplexity detector reports a probability that the text reads as AI; de-AI gate reports whether a literal tell is present in the file.
• False positives on human writing: a known, documented failure mode for a perplexity detector; none for de-AI gate, since a match is a real character or phrase.
• Where it runs: a perplexity detector is a web form, used after the writing is done; de-AI gate is a pre-commit hook or CI step, used before shipping.
• What it needs from you: a perplexity detector needs you to paste or upload your content; de-AI gate reads local files only, no network, no upload.
• What a flag tells you: a perplexity detector says maybe AI, maybe a careful human; de-AI gate says exactly which tell, and where to fix it.

The proof you are reading

This page is itself the demonstration. It argues about AI tells directly. It names the em dash, the curly quote, invisible unicode, and the set of high-precision phrase tells the catalog flags. A probabilistic detector would likely score a page this dense with tell-talk as suspicious.

And yet this page passes the de-AI gate in this site own build, because it contains none of the literal tells, only their names. A deterministic gate reads what is actually on the page. That is the claim, shown rather than asserted.