There’s a story about Claude that’s been everywhere this week: it identified a writer from 125 unpublished words. It’s been read as a privacy story. For people who write, the more useful read is that it’s a craft story.
Earlier this week, journalist Kelsey Piper, writing for The Argument, pasted 125 words of an unpublished political column into Claude Opus 4.7 and got her own name back. She’d logged out, tested via the API, run it again on a friend’s laptop. She varied the genre too: a school progress report about her child’s Pokémon essays, an unpublished review of a 1942 wartime comedy. Claude named her every time. ChatGPT and Gemini failed the same task. (Read her full account.)
Privacy is the frame the news has settled on. There’s a different frame to read it through if you write.
What the Piper experiment rules out
What I like about her experiment is how carefully she closed the exits. Logging out and going incognito killed the obvious “Claude knows me from my account” answer. Switching to the raw API ruled out browser fingerprinting. A friend’s laptop ruled out her IP address. By the end, the only channel left through which the model could know her was the prose itself.
Then she varied the genre. A political column might overlap with her public work. A school progress report about a child’s Pokémon essays does not. A review of a 1942 wartime comedy is not in her published register at all. The model still returned her name. That is the detail that does the work. Claude was not matching topics. It was reading the way her sentences are built.
Which is stylometry, and stylometry is now something frontier models do on their own, whether anyone intended it or not. ChatGPT and Gemini guessed wrong on the same task, so the ability is uneven. One model having it already changes the question for writers.
What does the privacy framing of this story miss?
The privacy reading is real and I am not waving it away. Models can identify writers from short, unpublished, off-genre prose, and the threshold will only drop as models improve. Fair concern. Useful coverage.
But the privacy reading treats the writer as the subject of surveillance. For working writers, that’s the secondary problem. The primary problem is what the experiment proves about prose itself.
Voice is real. Not in the way we wave at it when we talk about craft over a drink. In the boring measurable way. You can be identified from a few hundred words of your own writing. So can I. So can the writer you most admire.
Which I think most working writers already suspected. But it’s one thing to suspect and another to see Claude do it.
If voice is measurable, voice is preservable. And if voice is preservable, keeping it stops being a matter of taste and becomes a matter of craft. That’s the story that matters if you’re drafting fiction or long-form non-fiction with AI. Privacy is a perimeter problem. Voice is a craft problem, and it is the one nobody else in this discourse is writing about.
Why is voice a fingerprint, not an aesthetic?
Most AI writing tools treat voice as an aesthetic variable. You pick formal or casual, literary or commercial, sparse or maximalist. The dropdown is the voice. That framing has been quietly wrong for a while. The Piper experiment makes it provably wrong.
Voice is a fingerprint with dozens of axes. Word choice, sentence shape, the ratio of declaratives to dependent clauses, how paragraphs open and close, the rhythm of how sentences shorten or lengthen under emotional pressure, your relationship to abstraction versus concrete imagery, where you put the asides. Claude can read enough of those from 125 words to narrow a public corpus down to one person.
Treat that as the design brief it is. If voice is measurable, it’s preservable. And once it is measurable, the tools that handle it well will separate hard from the tools that pretend it is a setting.
This is the same fingerprint I wrote about in how to find your writing voice. The Piper experiment is the proof that it is real and measurable, not just a convenient way of talking.
What happens when AI writes “in your voice”?
I tried Piper’s experiment on a passage from my own novel a couple of nights ago. I asked Claude to describe the voice in 200 words I’d written. The description was startlingly specific. It told me my prose has an instinct for off-key similes that collapse mid-air, and quoted one back at me: a character’s hand gesture indicating “either a volcano or aggressive udder milking.” I had not noticed that about my own writing.
Then I asked it to generate a new scene in that voice. The result was technically competent and not mine. The shortening was gone. Adverbs were back. A kind of generic literary cadence had moved into the middle of the prose like a stranger.
Which is, I suspect, what most writers mean when they say AI drafts don’t sound like them. The feeling isn’t imaginary. The fingerprint is gone, and now we have a way to see it going.
How should writers think about this going forward?
Two things change.
First, voice is no longer something you have to argue for. When a tool sands the voice out of your draft, you can show it, and you should expect the tools you use to take that seriously.
Second, “how do I stop AI flattening my voice” stops being a vibes argument and becomes a craft problem, which means it is solvable. The tools that will matter are the ones that measure your voice from your own pages and then check the draft against it, rather than the ones that ask you to describe yourself in a settings box and hope the model remembers. A description gets forgotten by the third paragraph. A check runs on every chapter. That distinction is the whole reason I built bookmoth.
Privacy is a real concern in the Piper story. Voice as a measurable craft constraint is the bigger one for anyone making things from prose. The next year of AI writing tools will be sorted along that axis, whether the tools know it or not. Writers will sort them.
Related: which AI writing tools actually preserve your voice, and what measuring and checking voice looks like across a whole novel.