What is the Fluency Trap? The Fluency Trap is this: the more fluent your workaround, the less visible the structural gap underneath it. Your skill at catching bad AI output is not the solution to the inconsistency — it is what makes the inconsistency survivable, and therefore invisible, until it is not.
If you’re a working engineer who uses AI agents and is good enough to catch their mistakes, this article is the diagnosis of a problem your competence is currently hiding from you.
You’ve felt this, you just haven’t named it
You’re reading back a function the agent generated. The tests are green. But your eye stops — you cannot locate which architectural decisions were yours. You approved the output and kept going, and the path back to your own reasoning has closed over. That isn’t a rare edge case. That’s Tuesday.
Why competence makes it worse, not better
In a controlled study at Stanford, developers with an AI assistant wrote less secure code than those without — and were more confident it was secure (Perry et al., ACM CCS 2023, arXiv:2211.03622). The people who trusted the tool less, and reviewed more critically, shipped fewer vulnerabilities. Competence rose; quality fell; nobody felt it.
This matches thirty years of human-factors research: automation complacency appears in experts as readily as novices and “cannot be overcome with simple practice” (Parasuraman & Manzey, Human Factors 2010). The skill that lets you catch the drift is the same skill that lets you stop looking for it.
What’s actually accumulating
Underneath the Fluency Trap is the Borrowed Architecture — architectural decisions in your codebase that are not yours. The agent inferred them; you accepted them; they’re committed now, borrowed from a model that will infer something different tomorrow. It shows up as convention drift, assumption propagation, and gate erosion — each covered in its own article.
The fix is infrastructure, not discipline
The infrastructure gap is not a tool limitation — it is an architectural absence. The fix is three missing pieces you already know how to build: persistent context that survives between sessions, explicit gates that prevent trust from drifting, and an observability layer that makes agent decisions visible before they surface as failures. It’s the same move you made when you stopped eyeballing deploys and built a CI pipeline.
The cheapest first step costs 20 minutes: run the Borrowed-Architecture Audit on one of your own repos and make the invisible visible.
Read the full diagnosis and the frameworks: curiochat.ai/software-engineer