There is a new way to lose an argument you were winning. You write something correct, someone ignores the correct part, and tells you a machine wrote it. Discussion over.
That one landed on me last week. A comment with real numbers in it, and the reply did not touch the numbers. It went after where the words came from: this is AI.
They were right. A model smoothed the sentences.
The interesting part is not the accusation. It is that this reply is turning into a default move: a cheap way to judge provenance when checking the claim would cost real work.
The shape is simple. Judging where words came from is cheap. Checking whether they are true is expensive. When verification costs more than dismissal, provenance becomes the argument people reach for. "That's AI" is what an objection looks like when someone could not afford to build a real one.
The argument lands on the wrong layer
kenielzep has a post called "The Art of the Misconception" that names this: the visible layer gets treated as the operating layer. People argue about whether AI wrote the code, whether the screenshot is fake, whether the author holds the right credential. The part that actually decides whether the claim is true sits somewhere else, untouched.
A provenance objection earns its keep only when provenance changes the claim. If the data stands on its own, who polished the sentence does not. So the question to ask of any "it's AI" reply is the boring one: does knowing a model was involved change whether the thing is correct? Usually it does not. Which means the reply was never really about correctness.
The words got cheap, the work did not
Here is what actually changed, and why the reflex feels earned even when it is misused.
AI commoditized expression. Clean prose used to be a weak signal that someone knew their subject. It is not anymore, because a model will produce fluent sentences on demand. The writing is now the cheap layer.
A model can write a confident paragraph about work it never did. What it cannot do is hand you the result of work nobody has published.
My comment had correct data, and that data came from something I ran, not from a public citation chain a model could remix. The critic walked past the part that carried weight and picked a fight with the packaging.
The honest version of the defense is not "style does not matter." Plenty of AI text is fluent and hollow, all wrapper and no receipt. The narrower claim is the true one: judge the data. Yes, a model wrote the words. The words were never the value.
The tell is a map of the training set
There is one more layer, and it hides in plain sight. My comment was in Polish, and in Polish the tell gets louder.
Not because Polish is impossible for AI, but because most general-purpose models still carry an English-first center of gravity. They produce grammatical Polish, but the rhythm often feels borrowed: too smooth, too symmetrical, slightly translated from nowhere.
Bielik is the counterexample that proves the mechanism. It is built Polish-first, trained primarily on Polish data, with newer variants tuned more directly for Polish morphology. Its seams sit in different places.
So "this sounds like AI" is not a verdict on truth. It is a detector for where a model's training distribution runs thin. The reader who caught me did not show that the argument was weak. At most, they detected the wrapper: an English-first model pushed through Polish.
The smell is not magic. It is a map of what the model was fed and what it was not, and that map redraws itself the moment you change the training data.
What survives
Strip away the wrapper and one thing is left standing: the receipt, the result nobody but you could have produced.
So they were right. The words were the model's. The data was mine. They argued the half I would have given away for free.
Yes, AI helped write the comment. So what.
The question was never who smoothed the sentences. The question is who produced the evidence underneath.
Ask that one.
So where do you draw the line: is AI involvement the problem, or is it only a problem when there is no receipt underneath?
Top comments (0)