Chapter Zero · Beginner FAQ

When an AI Detector Says "This Was Written by AI," Can You Trust It?

You submitted a paper and the school detector flagged it as "AI-generated rate too high." A report you wrote carefully, and a colleague suspects a machine wrote it… How much trust does that score actually deserve? Don't rush to protest — play a short game, and you'll have your answer.

One-sentence answer

Don't trust it — it's closer to mysticism. AI learned by studying good human writing, so polished, fluent human prose often gets falsely accused; no detector today can reliably tell the two apart. The score is a shaky reference at best, and it must never be treated as evidence.

The judgment game · Guess how the detector will call it

Below are six passages — some written by people, some generated by AI. Your job is a little unusual: guess how the detector will call each one. After every passage, we'll reveal the detector's verdict, the real author, and whether it got it wrong.

Note: this game is a simulated demo. The detector results are preset on this page to show typical false-positive patterns. They are not the output of any real detector.
Why it can't be accurate even in principle

The detector's idea is to hunt for an "AI flavor": is the wording too tidy, the sentences too smooth, the structure too neat? Here's the problem: AI learned to write by studying good human essays. Smooth, tidy, clearly structured — that's exactly what careful writers have always been chasing. Asking a detector to find "AI features" is asking it to find "good-student features." Result: people who write carefully all get hit.

The other direction is even more awkward: take AI-generated text, swap a few words, add two typos, mix in some slang, and the score tanks immediately. A tool that falsely accuses good people going forward, and gets fooled going backward — what is it even catching? In the end it only sees surface features. It cannot see the author.

If you've been wrongly accused · A three-piece kit to prove you wrote it

The detector is unreliable, but the trouble of being wrongly accused is real. Instead of arguing after the fact, keep these three things on hand so you can produce them when it matters.

📝

Drafts and revision history

Most online docs come with edit history: which paragraph you wrote when, how many rounds you revised — all timestamped. A piece a real person wrote grows bit by bit. You can't fake that.

🎬

A screen recording of the writing

For important drafts (a thesis, a job-application sample), hit record while you write. It costs a bit of disk space and buys you evidence nobody can talk away. Worth it.

🗂️

Keep the process materials

Outlines, screenshots of sources, chat logs with classmates — these are footprints of the writing path. AI can spit out a draft in a second. It cannot fake a trail this complete.

A word for teachers and HR

If you're the one making a decision with a detector report in hand, remember this: the official docs of the mainstream tools all say the result is for reference only and false positives are possible. If the tool itself won't swear by it, the person using the tool shouldn't let it veto a student or a candidate in one shot.

If you really want to know who wrote something, the method has always been there: look at the writing process, and talk for a few minutes. Ask them to walk through their thinking, why a paragraph is written that way, how they'd change it from another angle. Someone who actually wrote it lights up. Someone who didn't slips in three sentences. That's more reliable than any detector score.

✅ What this page wants to share with you