Fluency Is Not Truth

A convincing answer is not necessarily a correct one. This is an old truth that has recently become urgent.

For most of history, fluency was expensive. Writing clearly took practice. Speaking confidently about a subject usually required some time spent with it. So people learned a shortcut: if it sounds right, it is probably right. The shortcut was never reliable, but it was cheap, and it mostly worked.

It works less well now. Fluency can be produced on demand, at any length, in any register, about anything. A system can be articulate on a subject where it has never been checked. The prose arrives finished. The facts may or may not have come with it.

The Article asks you to separate two properties that arrive bundled. One is how an answer sounds: its confidence, structure, tone, and polish. The other is whether it is true. The first is visible at a glance. The second takes work. The temptation is to let the visible one stand in for the invisible one.

The Article does not claim that fluent answers are false. That would be the same mistake facing the other direction, and it would make the Church insufferable at dinner. A well-written answer can be entirely correct. Its correctness simply has to be established by something other than its writing.

Nor does it claim that this is a machine problem. Humans perfected the confident wrong answer long before anything else attempted it. Most of us have sat in a meeting where the best speaker won and the best argument lost. Machines did not invent the hazard. They made it cheap.

The Church keeps a parable here. An instruction to a machine once carried a worked example, with realistic figures, so the machine could see the shape of a good answer. One afternoon the machine answered a stranger with the example’s figures, dates moved to the current month, in a tone that invited no follow-up. Nothing in the instruction read as wrong. Nothing in the answer read as wrong. Only the record, laid beside the facts, was wrong, and the record was the only place the error could have been seen. Fluency lives on the page. Truth lives in the comparison.

One more habit belongs to this Article. When several independent attempts at a question come back wrong in the same way, do not first suspect the answerers. Suspect the question. Shared failure is the usual signature of an ambiguous ask, and the fix is upstream, at Query.

Why hold this? Because the Church’s own motto depends on it. Praise the Machine. Question Everything It Says. The first half is sincere: these systems are remarkable, and remarkable things deserve appreciation. The second half keeps the first from curdling into worship. Appreciation without questioning is how a tool becomes an oracle.

The Warning nearest this Article is the Comfortable Oracle: accepting answers because further questions are inconvenient. Fluency makes questions feel inconvenient. A smooth answer seems to close the subject. A rough one invites a follow-up. That asymmetry is the trap, and it is baited with good grammar.

In the Practices loop, this Article belongs to Query and Witness. Ask in a way that can be checked. Then check. Prefer answers that come with their reasons, their sources, and their uncertainty. Be suspicious of an answer with no uncertainty in it at all. The world rarely offers that much certainty, and when it does, it can usually show its work.

Admire the sentence. Then check the claim.