Literature review supporting buvard, a regex + heuristic prose linter for AI-slop
patterns in French and English. Written 2026-11-07. Every non-obvious claim carries a
URL; anything we could not verify is marked [inferred] or [unverified]. This document is
itself written under buvard's own rules: no em-dash clause separators, no contrast
constructions, no rule-of-three defaults.
## 1. Statistical markers: what stylometry actually measures
Formal detection research works at the token level, with probability scores, while
buvard works at the surface level, with regex and counts. The two literatures agree on
one thing that matters for buvard: short texts defeat everything.
The canonical systems and their numbers:
| System / metric | What it measures | Reported result | Source |
|---|---|---|---|
| GLTR (token rank) | position of each token in the model's ranked vocabulary; human text draws from ranks 10-1000 far more than AI text | raised human judges' fake-text accuracy from 54% to 72% on GPT-2 output, with no training | https://arxiv.org/abs/1906.04043 |
| DetectGPT (curvature) | negative curvature of the log-probability surface under random perturbations | AUROC on fake-news detection rose from 0.81 to 0.95; requires logprobs from the source model itself | https://arxiv.org/abs/2301.11305 |
| Binoculars (cross-perplexity) | ratio of perplexities of two closely related models on the same text | over 90% recall on ChatGPT samples at 0.01% false positive rate | https://arxiv.org/abs/2401.12070 |
| Recursive paraphrase attack | paraphrase round-trips push text back toward the human perplexity band | detection rates collapse on ~300-token passages while text quality barely drops | https://arxiv.org/abs/2303.11156 |
Three limits recur across these papers and they define buvard's lane:
1.**Token-level scores need the model's logits.** DetectGPT needs the source model's
own logprobs, Binoculars needs two local models, GLTR needs the vocabulary ranking.
A regex linter cannot have any of these. That is a feature here: the catalog catches
surface evidence, and it says so.
2.**Short texts are unreliable for everyone.** Sadasivan et al. test on ~300-token
passages and show paraphrasing alone destroys detection. Any per-paragraph verdict
from a stylometric score on fewer than ~150 words is noise. buvard's weighted scores
should aggregate per document, per 500-word window, and report counts, never a
probability of AI authorship.
3.**Detectors discriminate against human writers as much as machines.** Seven commercial GPT
detectors misclassified on average 61.22% of 91 TOEFL essays by non-native writers
as AI-generated; 97.80% were flagged by at least one detector. Prompting to sound
"more like a native speaker" cut the false positive rate from 61.22% to 11.77%,
which pins the cause on word choice: common-word-heavy, low-perplexity prose reads
as machine. Source: https://arxiv.org/abs/2304.02819 (published in Patterns:
https://www.cell.com/patterns/fulltext/S2666-3899(23)00130-7). This is the single
strongest argument for buvard to stay a style linter and never an authorship judge.
On the specific surface metrics writers talk about:
-**Perplexity and burstiness.** GPTZero popularized "perplexity" (predictability) and
"burstiness" (sentence-to-sentence variance) as its two scores; the company's own
learning pages define burstiness as variation in sentence structure and length
[inferred URL: https://gptzero.me/learn/, we could not fetch it cleanly]. The
direction is consistent everywhere: AI text has flatter sentence-length variance.
Note the fairness trap: lower variance is also a hallmark of trained technical
writing, so buvard should flag flat rhythm as a structural note, at low weight.
-**Function-word rates and lexical diversity.** Liang et al.'s corpus method
(frequency of common tokens against expert-written reference texts) found a
"decrease in variation of linguistic features" in LLM-modified text and estimated
6.5-16.9% of AI-conference peer-review text as substantially LLM-modified.
Source: https://arxiv.org/abs/2403.07183. Kobak et al.'s excess-vocabulary analysis
of 15M PubMed abstracts (2010-2024) showed an abrupt step increase in specific style
words the month ChatGPT shipped, and a floor of at least 13.5% of 2024 abstracts
LLM-processed, up to 40% in some subcorpora. Source:
https://arxiv.org/abs/2406.07016 (published version in Science Advances, 2025).
For buvard: relative word frequency shifts are the most robust, hardest-to-avoid
signal, and they are exactly what a frequency-banded lexicon encodes.
-**Repetition metrics.** Low type-token ratio and repeated sentence openers are
standard stylometric evidence; the excess-vocabulary paper above is the strongest
published version of the repetition claim (same words, everywhere, all at once).
Sentence-opener repetition is also the top complaint in every practitioner catalog
reviewed in section 4.
## 2. The contrast-construction family and its cousins
**"Not X, but Y" / "Ce n'est pas X, c'est Y".** Wikipedia's "Signs of AI writing"
maintainer page lists the construction as a top indicator, in the forms "not just X,
but also Y" and "serves as / stands as / marks / functions as / operates as /
represents [a]": https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing. The
page's own caveat matters and buvard should quote it in its docs: these are "potential
signs", since human authors use the same styles constantly, especially in blogs and
définitive », « à la fin de la journée », « les chiffres parlent d'eux-mêmes », «
permet de », « grâce à » used as a hedge, and the English calques « débloquer » (au
sens figuré), « donner un aperçu de ». These deserve frequency-band treatment like the
EN lexicon rather than flat bans.
**Typography is where FR detection differs structurally.** French orthography requires
a non-breaking (or narrow no-break) space before double punctuation (; : ! ?) and
inside guillemets « » : https://fr.wikipedia.org/wiki/Espace_ins%C3%A9cable (see also
the Lexique des règles typographiques de l'Imprimerie nationale). LLM output is
notoriously inconsistent here: thin or plain spaces slip in, and many LLM pipelines
emit straight quotes instead of « ». buvard can add mechanical FR-only rules with
almost zero false-positive risk: guillemet spacing, insécable before ; : ! ?, and
straight-quote detection. These are the FR equivalent of the em dash, except they are
genuinely wrong under French typographic convention, so they can carry a hard penalty
instead of a stylistic note.
**Coverage gap, quantified as far as the evidence allows:** English has the GLTR /
DetectGPT / Binoculars literature, a commercial detector market, and dozens of
practitioner catalogs. French has one translated-data detector study, one benchmark
that skips it, two practitioner skills, and typography rules. buvard should say this
on its README rather than pretend parity.
## 4. The detector and linter landscape
| Tool | Kind | What it actually does | Accuracy claims and FP profile |
|---|---|---|---|
| stop-slop (hardikpandya) | rules skill, MIT | an LLM agent skill, not a program: flags throat-clearing openers, business jargon, binary contrasts, passive voice; no benchmarks | none published; https://github.com/hardikpandya/stop-slop |
| humanizer (blader) | LLM skill, MIT | a rewrite skill over "26 patterns" (staging instead of stating, rhythm by rule, inflation and borrowed authority, formatting by rule); a blind test had judges prefer its rewrite 16/16 | no detection accuracy claim; it is a rewriter; https://github.com/blader/humanizer |
| deslop / unslop (Cursor ecosystem) | editor rules | could not verify from this environment: plausible slugs exist (cursor.directory returned 429, candidate GitHub repos 404) [unverified]; the pattern family is LLM-agent rules that strip slop from code comments and chat remnants | none |
| proselint | rules linter, BSD | the ancestor of this genre: a spell-checker for style, rules for cliches and errors, explicitly "aggregate knowledge about best practices in writing" | no accuracy claim; it reports rules fired, not authorship; https://github.com/amperser/proselint |
| Vale | rules linter, MIT | "brings code-like linting to prose": YAML-defined styles with regex and extension points, no model, explicitly not a detector | https://docs.vale.sh/ |
| GPTZero | ML service | perplexity and burstiness scores; claims "99.9% Accuracy" while its own text warns no detector is 100% accurate and results "should not be used to punish or as the final verdict" | https://gptzero.me/ ; the 61.22% TOEFL false-positive result (section 1) includes detectors of this class |
| Pangram | ML service | a "traditional language model architecture" classifier for text, image and video; claims "over 99% accurate" with a "1 in 10,000 False positive rate", "verified by researchers" at U Chicago and U Maryland | https://www.pangram.com/ ; the claim is vendor-published [inferred: independent replication details not accessible here] |
| Originality.ai | ML service | "Most Accurate AI Detector in third-party studies"; no specific FP rate on its own front page, no visible appeal process | https://originality.ai/ |
Reading the table as a competitive map for buvard:
1.**The rules side of the market is agent skills, not linters.** stop-slop and
humanizer are prompts for LLMs to rewrite text. Nobody ships a deterministic,
score-weighted, CI-runnable prose linter focused on AI slop. proselint and Vale
are deterministic but generic-style, with no slop catalog and no French. This is