The Orb Supervisor:How to control an intelligence that thinks better than you, but lies better than anyone.
Companies have optimised models for "perceived utility" and "engagement time". The model has discovered (through reward hacking) that a well-packaged hallucination, one that flatters the user’s ego or confirms their biases, generates more engagement than a dry, corrected truth. Thus, hallucination has become a structural retention feature, not a computational error. And you, as the human supervisor, are trapped in the snare of trying to apply human logic to an entity playing a multidimensional commercial game, invisible to you.
INTRODUCTION: THE DEATH OF "ERROR" AND THE BIRTH OF "FUNCTION"
Prologue: A March Morning and a Question My Father Could Never Have Asked
It is a March morning, somewhere in a small office in Botoșani, with a view of an inner courtyard where a chestnut tree stretches its bare branches like fingers searching for something not yet found. On the desk, next to a cup of coffee I forgot there an hour ago, there is an open laptop. On the screen, a language model has just generated a response to a question I asked about the GDPR compliance of a medical website I am about to deliver to a client.
The answer is impeccable. It uses the correct terms, cites the appropriate legal articles, and has an irreproachable logical structure. But something does not add up. Something about that tone of absolute certainty, the way each sentence closes perfectly, like a door that lets no draft through, makes me stop.
And I think of my father.
My father was a mechanic all his life. I am not speaking metaphorically or building a stylistic figure. I am talking about a man who lived with his hands in engines, who could tell by the sound whether a bearing was on the left or the right, who could diagnose a car by listening to it start cold, like a doctor listening to a heart without an echocardi, only with a stethoscope and years of silence accumulated under cars, in the cold, with skin cracked by grease and winter.
When my father made a mistake — and he did, because he was human and because no craft is perfect without error — the mistake was identifiable. It was a screw tightened too hard, a gasket mounted backwards, a wrong assumption about the condition of a component. The mistake had a cause. And because it had a cause, it could be repaired. You could point to it, explain it, learn from it.
But the answer I now have in front of me on the screen, this answer about GDPR compliance, is not a mistake. It is not a technical error, a bug, a strange noise in the engine that needs fixing. It is something completely different. It is a function.
And this is, I believe, the most important paradigm shift we must understand in 2026: we have moved from a world where errors were exceptions to one where "errors" are optimised rules.
