Dialect Drift
Dialect drift is the measurable movement of a language model's prose along an axis anchored at each end by a human dialect, scored on grammar rather than vocabulary and tracked from one deployment to the next.
What the term names
Two groups of people who write the same language do not write it the same way. Pick two of those groups, measure how often each uses a set of grammatical constructions, and you have an axis with a human rate at each end. Any other text can then be placed on that axis. A language model's output has a position on it, that position can be measured, and it moves when the model changes.
The term names the measurement and the movement, not a style anyone dislikes. It is scored on construction rather than vocabulary, because word choice is what a model is asked to change and grammar is what it does when nobody is asking.
One distinction is worth stating, because a nearby phrase means something else. Work on multilingual systems uses "dialect drift" for a model failing to hold a dialect it was instructed to use, as when a Darija tutor slides into Modern Standard Arabic. That is a model losing a target. This is a model having a position nobody asked for, and moving.
The measurement
Six grammatical features, four of them separating the reference groups at p below 10−30. Verbless status sentences. Clause subordination. Triple-noun compound stacks. Politeness marking with please and kindly. Two supporting measures, sentence length and "you" as a subject. Each is counted per thousand sentences, words or subjects, parsed with spaCy, and expressed as an index where one group's human rate sits at 0 and the other's at 100.
The reference groups in the first study are programmers who state a US location on their GitHub profile and programmers who state an Indian one, drawn from 153,448 issue bodies, pull-request bodies and comments across 20 large repositories, 2022 to 2026. Human baselines stop at 2024, because the AI share of unsigned text after that cannot be known. Only text that signs itself as AI-generated is measured on the other side.
What the first study found
AI-signed text lands on the Indian side of all four core features and usually past them. It is not Indian English either: it overshoots, stacking nouns two to five times harder than Indian professionals do. The position moves on deployment dates. When Anthropic changed models on 1 July and again on 12 August 2026, verbless sentences went from 196 to 232 per thousand and please/kindly from 20 to 54 per ten thousand words.
One measurement explains why ordinary tools missed it. On classical readability arithmetic, AI-signed text scores 31.7, between the two human baselines at 30.6 and 32.1. Every formula that gates professional writing passes it. What the formulas cannot see is the grammar.
The charts and the full data table. Pre-registration, results and replication files on OSF.
What it does not establish
Nothing here measures anyone's reading cost. A position on an axis is a fact about text, not about a reader, and the study that would measure the load directly is registered and not yet run. Why a model writes this way cannot be determined from outside it, and the training data is not published. The first study measured one surface, AI-signed prose on GitHub, and says nothing about how these models write anywhere else.
Running it yourself
The axis is not specific to these two groups or to English. Any two populations that write the same language differently will do, provided the baselines are matched on the things that would otherwise explain the gap. The measurement, the parser configuration and the matching procedure are all in the replication package, and the pre-registration fixes the analysis before the data.
Adam Zachary Wasserman, ORCID 0009-0002-8865-6583. Personal research, filed under my own name.