Solve the Wheel, Break the Chariot

There is a particular narrowing that comes with concentration. The edges of the room go quiet, the shoulders draw in, the breath shortens, and the world contracts to the thing under your hands. It is a gift. Most good work needs it. It is also among the oldest traps the mind sets for itself, because the instant the field shrinks to a point, the point begins to feel like the whole of what is real.

AI systems have become fluent enough to make that trap visible from the outside, at a scale we can study. A model enters a task, draws a boundary around it, finds the salient objects inside, and acts with genuine competence. Then the boundary that made the task workable hardens into its sense of the entire situation. It treats a temporary cut through a wide field as though it had found the real object, and it keeps optimising inside a frame whose legitimacy it has quietly stopped checking. This is boundary reification, and it is a technical problem well before it is a philosophical one.

Contemporary models work by relation. Tokens gain force through context, embeddings place items among their neighbours, attention spreads relevance across a field, and agents assemble a local frame in which a bug, a file, a request, a service or a plan becomes intelligible. Competence emerges from patterns of relation across many scales. The same machinery that composes a useful local frame can then mistake that frame for the situation itself. A larger context window does not cure this. It can hand the model more material while leaving it unsure of the scale at which the problem actually lives.

The clearest case is the software agent. It sees an error trace, opens the file, follows one import, changes a local service, and gets the immediate test to pass. At that resolution the work looks skilled. Yet the real object was a product flow, a shared domain model, a deployment path, a user's expectation. The agent solved the wheel and broke the chariot. It stayed loyal to the file long after the task had moved to the system. A great many failures that look like shallow reasoning are failures of scale traversal, an inability to move between the levels on which a thing is true.

Human perception offers a compact bridge. In the familiar THE CAT example, the same ambiguous mark reads as an H inside THE and an A inside CAT. Context is not added after the letter is recognised. It enters perception from the start. The word superiority effect, established through Reicher's forced-choice experiments and modelled by McClelland and Rumelhart's interactive activation, shows people reading a letter more accurately inside a real word than alone. The letter helps fix the word while the word helps fix the letter. Lower evidence and higher expectation settle together. Intelligence is this reciprocal movement across levels, and a system that only travels upward loses the detail, while one that only travels down loses the form that gives detail its role.

This is where Nagarjuna earns his place, after the engineering problem has already been named. Madhyamaka carries a heavy metaphysical vocabulary, but its working diagnostic is plain and sharply relevant. We fall into confusion when we mistake dependent designation for intrinsic nature. A boundary can be conventionally valid, practically indispensable, and still hold no self-standing essence. Distinctions remain necessary. They work through dependence rather than through any nature of their own.

The chariot is his clearest example. A chariot is not the wheels, the axle, the frame, the yoke or the reins, and it is not something floating free of them. It exists conventionally, through parts and arrangement and use and purpose. Remove enough of that field and the chariot is gone, even with some pieces still in hand. AI systems handle chariot-shaped objects constantly. A service, a bug, a customer intent, a safety violation, an agent's plan: each is a designation within a dependency field rather than a self-contained thing. Treat a bug as only its failing line and you patch a symptom. Treat a service as only its source directory and you lose the contracts, the migrations, the latencies and the expectations that make it the service it is. Nagarjuna does not tell an engineer how to write a scheduler. He gives a precise warning. If the object is dependently designated, the right boundary is task-sensitive and revisable.

Madhyamaka precision earns its keep by staying clear of two easy errors. One is a naive realism that takes the natural unit of analysis as simply given. The other is a loose relativism in which every boundary melts. The disciplined middle is more useful. Boundaries are conventional, dependent and fully functional. They can be exactly right for a purpose and misleading the moment they are carried to another scale. In engineering language, a boundary is an interface contract with a scope, and outside that scope confidence should decay. Nishida Kitaro's language of place says the same from another side. A local object appears within a field that makes it intelligible, and the field is not simply one more object standing beside the things it holds. The repository is not just another file. When a system treats its current bounded context as the whole place of meaning, it has let the map swallow the terrain.

A design philosophy follows, and it is a hopeful one. A boundary-fluid system would not be boundaryless, since every task needs selective attention. It would draw boundaries explicitly, use them provisionally, and revisit them under pressure. It would treat frames as tools rather than final descriptions, and it would learn to zoom in and out as a basic operation, as ordinary as retrieval or planning. Such a system asks simple questions as it works. What boundary am I using now. What does it make visible, and what does it hide. Which larger field gives this object its role. Which smaller mechanism might prove my current reading wrong. What would count as evidence that the task lives at another scale. These sound philosophical, and they can be operationalised. An agent can be required to state its current unit of analysis, to generate the neighbouring scales before acting, to hold a live map from function to module to service to product to user, and to read a passing integration test alongside a failing one as a signal of boundary error rather than noise.

The target capability has a clean shape. Flexible fidelity to the field: enough stability to act, enough fluidity to revise the line. Repair the wheel, then check the chariot.

None of this asks AI to validate an ancient philosophy by rediscovering it in silicon. A language model does not understand emptiness because it manipulates contextual embeddings. The claim is narrower, and stronger for it. Modern systems stage a practical version of a very old confusion, that intelligence rests on conventions while error begins when a convention is treated as self-grounding. And the same recognition that would make a machine wiser is available to the person reading this. The narrowing that opens every act of attention does not have to harden into a wall. You can draw the boundary, do the work inside it, and still feel for the wider field it was cut from. Use the chariot, repair the wheel, and keep the field in view.