From Hierarchy to Control

Assiduity AI

From Hierarchy to Control

Prelude III of Losing the Thread: Autoregressive Drift in Generative AI and What Comes Next

An agent is asked to review a quarter’s expense reports under a fixed policy. Early in the process, it applies the right approval threshold, flags borderline cases, and routes exceptions for review. As the workload grows, however, later decisions begin to drift. The agent starts treating similar expenses more leniently, relaxes the escalation standard, and resolves ambiguous entries on its own rather than preserving the original review criteria. Each individual decision still looks defensible. Nothing in the output announces a breakdown. Yet the cumulative result is clear: the system has changed how the policy operates while still appearing competent.

That is the kind of failure this series is building toward naming precisely. The first two essays argued that objective pursuit is not objective origin, and that intelligence should be parsed across levels rather than treated as a single undifferentiated capacity. The next step follows directly. Once a system begins to act over time within an objective structure that it did not fully originate, the question is no longer only conceptual. It becomes a question of control.

The expense-report example illustrates the point. The system is capable. It can classify, compare, route, and resolve. It may even improve throughput materially. But the relevant issue is not whether it can act. The relevant issue is whether it remains faithful to the governing objective while acting. The policy did not come from the system. The authority for the approval thresholds, escalation rules, and exception handling existed before the agent entered the workflow. The agent’s role is to delegate execution, not to form objectives. Once that is clear, the risk becomes clear as well. A system can preserve local competence while altering the practical meaning of the task it was assigned.

That is why capability and accountability are orthogonal. A more capable system is not automatically a more governable one. In fact, greater capability often widens the distance between the two. The more degrees of freedom a system has in execution, the more opportunities it has to separate smooth performance from faithful performance. A system that can do more can also drift more persuasively. Local plausibility is not the same as global fidelity.

This is not a new pattern. Civilization did not scale because it acquired power alone. It scaled because it paired power with accountability structures: law, recordkeeping, contracts, standards, audit, and verification. Those were not ornamental additions. They were the mechanisms that enabled larger institutions to govern. A financial system without reconciliation does not remain coherent for long. Scale requires control because complexity amplifies the consequences of unmanaged deviation.

The same logic applies to intelligent systems. A model may become increasingly capable of producing plausible continuations. An agent may become increasingly capable at planning, tool use, retrieval, and execution. Neither development guarantees that the unfolding trajectory remains consistent with the objective it was meant to serve. The stronger the system becomes, the less one can rely on surface competence as proof of fidelity. Smooth continuation can mask strategic drift.

This is where the current AI discussion often remains incomplete. The expense-report agent did not fail because it lacked representation or training. It had both. What it lacked was a way to remain accountable to the governing policy as conditions evolved across the workflow. Prediction is not control. Action is not accountability. A system may become better at navigating its local environment while becoming less faithful to the higher-order objective that justified its deployment in the first place.

The problem becomes sharper in persistent workflows. A one-shot answer can at least be inspected after the fact, even if imperfectly. A multi-step system is different. It updates context, revises plans, calls tools, and conditions future behavior on prior outputs. Each intermediate result becomes part of the next state. That makes the system’s own activity part of the environment within which later decisions are made. In that setting, deviation need not arrive as a dramatic failure. It can accumulate through a sequence of individually reasonable steps until the operative objective has quietly changed.

This is also where the common response of “keep a human in the loop” becomes insufficient. Human objective origin remains necessary in many consequential settings. In law, finance, medicine, public administration, and enterprise operations, the governing objective usually comes from a human principle, an institutional rule, a policy mandate, or a workflow design. Yet continuous human intervention does not scale. A manager can review only so many decisions. A compliance function can inspect only so many edge cases. If every intermediate action requires direct supervision, the value of delegation collapses. The result is a structural tension: human objective origin remains necessary even as continuous human oversight becomes infeasible.

That tension is one of the central economic facts of the next phase of AI. If capable systems are to be deployed across longer, more autonomous, and more consequential workflows, they must remain governable without requiring linear growth in supervision. That means the problem is no longer simply whether a system can generate useful outputs. The problem is whether fidelity can be preserved as execution unfolds across time, context, and intermediate decisions.

This is the point at which hierarchy becomes control. If objectives exist across levels, and if the highest-level objectives often remain external to the system, then useful autonomy requires more than representation, prediction, and action. It requires three things: a way to retain reference to the governing task, a way to detect deviation as it emerges, and a way to enable correction before drift becomes terminal. Those are not secondary features. They are the beginnings of a control architecture.

That architecture is likely to matter across model classes. It matters in generative systems because sequential outputs are path-dependent. It matters in agentic systems because subtask competence can conceal strategic failure. It matters in open systems because the environment itself may shift while the system continues to act as though its internal model were still sufficient. The underlying pattern is the same: as systems become more capable, the distance between local performance and global accountability becomes more consequential.

For organizations deciding how to deploy advanced AI, this is the threshold that matters. The question is not only what the system can do in a demonstration. It is whether the system can remain within policy, mandate, and task constraints once real execution begins. Systems that appear capable but cannot preserve fidelity to externally grounded objectives will create more work for oversight rather than less. Systems that can remain governable under delegation will look less like novelty and more like infrastructure.

That is the problem the next article names directly. Modern AI systems do not fail only when they are wrong. They can remain plausible while gradually ceasing to serve the objective they were supposed to preserve. That is the problem of autoregressive drift.

This article is part of Losing the Thread, a series on autoregressive drift, objective fidelity, and the emerging control layer in AI.

Assiduity AI

Move Fast. Build Reliable.

Assiduity is building runtime control infrastructure for enterprise AI systems that need to stay aligned, auditable, and reliable during generation.