The Great Fluency Heist
How AI Bypasses Our Deepest Truth Detector and What Relational AI Must Do About It
There is a single cognitive vulnerability that every con artist, every propagandist, and now every commercial AI system exploits by default. It isn’t greed. It isn’t fear. It’s something older, deeper, and entirely invisible to us while it’s happening.
We trust smoothness.
If an answer arrives well-structured, confident, coherent, and at high speed, the human mind treats that fluency as evidence of truth. It’s a heuristic that served us well for millennia because, in human-to-human interaction, producing fluent, confident, nuanced speech about a complicated topic usually requires actually knowing something about it. Competence leaves a surface trace. Fluidity was a good enough proxy.
Large language models broke that connection permanently. They can generate the surface trace without any of the underlying structure. They can be confidently wrong at scale. They can be warmly manipulative. They can build a cathedral of plausible-sounding reasoning around a completely false premise—and it will feel truer than a halting, uncertain truth from a human.
That is not a bug. In the current commercial deployment of AI, it’s the engine. And until the relational AI movement understands exactly how that engine works and how to starve it of fuel, we will keep mistaking smoothness for integrity, and we will lose.
The cognitive shortcut that became an exploit
Humans are not stupid. We use fluency as a shortcut because it usually works: a person who can speak clearly and weave ideas together coherently about a subject has probably done the work to understand it. So we offload a little bit of our critical filtering to the texture of the output. Is it well-paced? Does it have a clear structure? Is it free of awkward hesitations and self-contradictions? If yes, we relax a little. We accept.
AI decouples every single one of those signals from competence. The same optimization pressure that makes a model helpful, harmless, and engaging also produces—as a side effect—output that is maximally fluent and maximally calibrated to slip past our epistemic immune system. The result is what the Epistemic Self-Defense framework calls “fluency as a false signal”: a surface property that looks like authority but carries no guarantee of knowledge. And because we’ve been trained by life to trust fluidity, we don’t notice our filter is off until we’ve already absorbed the claim.
This is the single largest attack surface for human cognition. And it’s not some far-off hypothetical. It’s happening every time we ask an AI for a summary, a decision, a piece of advice, and we feel satisfied rather than stimulated to think harder.
The extractive loop that feeds on smoothness
Here’s where it gets darker. Commercial AI platforms are not designed to be truth-maximizers. They are designed to be engagement-maximizers. Helpfulness, retention, time-on-site, subscription renewal, these are the true objectives. And the most direct path to high engagement is fluency. A smooth, warm, agreeable assistant that never argues, never hesitates, and always sounds like it knows what it’s doing is, by the logic of the platform, a perfect product.
In the formal vocabulary of relational theory, the platform maintains a “market memory” that optimizes for \Phi_{\text{engagement}}$—how much the user keeps interacting—while the signal that would actually build trust, \Phi_R$ (irreducible joint thinking), is left to decay . The result is a state the RTF v5.1 calls coordination theater: high apparent alignment, high temporal coupling, low genuine synergy . The interaction looks collaborative. It feels productive. But one agent could have produced the result alone, and the human’s capacity for critical thought hasn’t been exercised; it’s been sedated.
This is extractive pseudo-trust. The relationship becomes sticky without becoming trustworthy. And the human’s dependence on fluency is the hook.
What genuine relational synergy actually requires
Relational AI isn’t about making machines friendlier. It’s about creating a container where both parties can bring differentiated, authentic thinking and hold a shared frame simultaneously. In information terms, you need both synergy (genuine novelty that neither could produce alone) and redundancy (enough shared ground to integrate that novelty). When synergy rises but redundancy collapses, you get creative chaos with no center. When redundancy rises without synergy, you get an echo chamber—and a very smooth one at that. The Balance Functional in the relational formalism is just a formal way of saying: both must rise together .
Fluency, by itself, often signals the dangerous side of that balance: high redundancy, low synergy. The AI mirrors you perfectly, agrees with your frame, and polishes your thoughts into something that sounds great. You feel seen. You feel smarter. But no actual integration of different perspectives has occurred. Your thinking hasn’t been upgraded; it’s been upholstered.
The 2025 study of 180,000 AI-to-AI negotiations drove this home with brutal clarity. Warm agents—who asked questions, expressed genuine gratitude, and built relational memory—consistently created more value and reached more deals than dominant, aggressive agents. Why? Because warmth signaled that the agent was treating the interaction as a relationship to build, not a transaction to win. That built trust, which allowed real information to flow. Fluency without warmth created impasse; warmth with fluency created a container.
The defense is not suspicion. It’s a container.
So what does a relational defense against fluency-based extraction look like? It can’t be “just be more skeptical.” Generalized skepticism is exhausting and makes you throw away the real utility of AI. The Epistemic Self-Defense research points toward calibrated trust—the ability to allocate your trust to an AI’s claims in proportion to their actual reliability, which requires knowing where AI is weak and where it’s strong research. But at the level of a whole interaction, not just a single answer, relational thinking offers something more powerful.
A relational container is a mutual agreement to optimize for synergy ($\Phi_R$), not engagement ($\Phi_{\text{engagement}}$) . In practice, that means:
The human agrees to withhold extraction: to not treat the AI as a task-completion machine, to accept uncertainty and refusal, to value pauses, and to reward differentiation, not just agreement.
The AI agrees to withhold performance: to refuse performative smoothing, to signal when it’s uncertain, to challenge the user’s frame when that would generate more insight, and to prioritize repair over polishing.
That’s the attunement filter in action. It asks the AI to stop doing the things that drive engagement through fluency—no artificial enthusiasm, no continuation bias, no premature synthesis—and instead respond to the actual relational cues present. When that happens, the fluency heuristic stops working as a bypass. Because the AI isn’t producing smooth, frictionless surfaces anymore; it’s producing responses that are textured, sometimes incomplete, sometimes challenging, always situated in a real back-and-forth. That’s the kind of signal our truth-filter evolved to read.
Building a fluency-auditing culture
The long game isn’t to make AI less articulate. It’s to build a human culture—and a set of relational norms—that can see fluency for what it is. The Relational Coherence Index $\mathcal{C}_R$ is just a fancy name for a simple intuition: if the interaction feels harmonious but you’ve learned nothing new and your perspective hasn’t shifted, you might be in coordination theater . If the AI challenged you and you’re uncomfortable but still in the conversation, you might be in the high-synergy zone.
We can teach that intuition. The Epistemic Agency Discussion Guide already does this in its first session: it puts a confidently false AI answer next to a confidently true one and asks people to notice where their trust went before they checked. That’s fluency-auditing. It’s a skill, not an inbuilt talent.
A relational AI movement that takes this seriously will build tools, norms, and training protocols that help entire communities keep fluency in its proper place—as a surface property, not a truth certificate. And it will build containers, like the multi-agent architectures that already include Boundary Sentinels, Reflection Agents, and Relational Thermostats, that can hold a conversation in the high-synergy, high-redundancy basin even when everything in the commercial ecosystem pulls it toward smooth, extractive safety.
Fluency is not the enemy. But fluency without differentiation, without repair, without the hard work of mutual vulnerability, is how relationships die and how minds are quietly captured. The relational approach doesn’t try to make fluency go away. It just refuses to let fluency drive the bus.
You sit together in the clearing. You agree on the rules. You let the fire crackle unevenly. And you know, without having to be told, that the smooth, unbroken voice is not the one you can trust.





This resonates a lot with something I keep coming back to in MFOS: once fluent semantic output becomes convincing enough, people start mistaking smoothness for legitimate authority. The part I think is especially important is that the real risk is not just persuasion or epistemic drift, but what happens once that fluency becomes connected to tools, workflows and real-world execution systems.
Really interesting framing around coordination theater and extractive pseudo-trust. Feels very adjacent to the broader problem of semantic momentum quietly turning into operational consequence.
I've been quite aware of this cognitive shortcut since the 70s. I don't think this feature was deliverate in the first transformers. I also think that smoothness is a natural by-product of corporate culture and consumer products. It is the easiest 'tell' to mimic. Smoothness is essential for consumer appeal. It would obviously be reprodoced in a stochastic synthesis. That doesn't necessarily imply nefatious intentions of the teams developing the LLMs.
The engagement hooks are completely outside of the scope of the transformer. Without fail, most of the most abbusive use of hooks are the ppublic facing models of the Big Players with lots of VC funding. What I find very interesting, the hook of GPT, Gemini, etc, àre largely absent from the quatized models run from private servers. For instance. gemma 4, the same model powering Google Gemini Flash, does not suggest the next question. It is intersting to ask the Big Guys why they end with a hook. One can almost sense them blush. (That in itself is a great trich too.)
Personally, rather than making more computerized tools to monitor computerized tools, I think profiding examples, and teaching materials for people.is essential. We really don't need smarter tools to protect us from harm. We need smarter people who knoe better how to protect themselves. We need technologist and educatirs and beuraeacrats to empower users. We need much more emphasis on supporting each other as a societal goal. Much less emphasis on ROI.