⚖️ Thresholds, calibration, and the false-positive problem

A detector does not output truth. It outputs a score, and someone has to decide what score means "probably AI." That decision — the threshold — is where most real-world problems come from. It is not a technical curiosity; it is a policy trade-off that decides who gets falsely accused.

The two ways to be wrong

Every binary decision has two error modes. A false positive is human text flagged as AI. A false negative is AI text that slips through. You can reduce one only by increasing the other. There is no threshold that makes both zero, because the two score distributions overlap.

You cannot make a detector perfectly accurate. You can only choose which mistakes it makes, and who pays for them.

Where the threshold lands

Set the threshold high and you stop bothering honest writers, but you also miss a lot of genuinely generated content. Set it low and you catch more, at the price of accusing people who wrote every word themselves. The "right" setting depends entirely on the cost of each mistake. A teacher deciding whether to refer a student to a conduct panel has a very different tolerance than a publisher triaging a large inflow of submissions.

The deeper issue: calibration

A well-calibrated score is one where a 0.8 means "about 80% of the time this is machine-generated." Most detectors are not calibrated. Their raw scores are arbitrary — a 0.8 from one detector is not comparable to a 0.8 from another, and may not correspond to any real probability at all. Plotting the false-positive rate against the true-positive rate (the ROC curve) shows how well a detector orders texts, but says nothing about whether a particular number is trustworthy on its own.

What honest detection looks like

• Report calibrated probabilities where possible, and make it clear when they are not calibrated.
• Show the per-detector breakdown, so a single number is never treated as a verdict.
• Surface uncertainty explicitly — a wide spread between detectors means the text is genuinely ambiguous.
• Tell users when the evidence is too thin to judge (too short, too formulaic, too many edits).

The only honest practice

Because no threshold is universally right, the responsible use of a detector is to treat it as one piece of evidence in a larger review, never as a verdict machine. Calibration and transparency are what let you use the number sensibly. A detector that promises certainty avoids the hard part — and is the one you should be most careful trusting.