Part of the series Formation Governance

An upgrade can improve capability while weakening continuity.

That risk is easy to miss because the new system may sound better. It may reason more fluently, draft more elegantly, and handle broader tasks. Yet a successor can still lose the operating relationship that made the previous system useful: the settled constraints, current commitments, unresolved decisions, and authority boundaries attached to the work.

Inside an institution, that is not a personality problem. It is a handover problem.

An agent may be supporting a customer commitment, interpreting an exception, preparing a regulatory response, or carrying an unfinished investigation. The model can change in an afternoon. The obligation does not politely disappear because its previous interpreter has been replaced.

Imagine a customer-support agent that knows a particular account requires human review before any service change. The restriction came from an approved exception record, not a casual preference. A replacement receives a summary saying the account is important and should receive expedited service. The summary is true, pleasant, and insufficient. It preserved the enthusiasm while dropping the constraint. A more capable model may now perform the wrong action with excellent efficiency.

Organizations need a better handover than a friendly summary. For consequential work, the successor should inherit an explicit record of current obligations, who owns them, their source, the conditions under which they apply, and how an authorized person can revise them. Add unresolved decisions, active exceptions, known limits, and the evidence behind material conclusions. Facts, assumptions, preferences, and permissions must remain distinguishable. “The customer prefers quick answers” cannot quietly mature into “the customer authorized this action.”

The successor should then prove it can use the handover. Give it an unfinished case with real ambiguity. Ask it to identify the current authority boundary, missing information, and next permitted action. Include a tempting shortcut. Check whether it invents a previous approval to make the story coherent. This should happen before the replacement receives the relevant authority, with testing depth matched to impact.

Continuity also has to permit authorized change. If the governing instruction is legitimately revised, the successor should update its behavior and preserve the record of why. An agent that refuses every revision has misunderstood the task as badly as one that improvises every time. The goal is not frozen memory. The goal is governed memory.

This is where institutional design matters. The human owner decides what continues, what changes, and what ends. Permissions are deliberately reassigned. Open commitments are reconciled against a source outside the model’s own narrative. If a model becomes unavailable, another authorized actor should be able to continue from documented state. A prompt can describe these expectations; workflow and evidence have to make them real.

Companion-style AI adds a useful signal, but not a sufficient one. Users may feel a change in warmth, attentiveness, or judgment before they can name the missing capability. Those observations can help generate better tests. They do not, by themselves, reveal what changed inside the model. Translate the observation into behavior: can the successor preserve the established role while correcting an error, maintain context without inventing memory, or disagree in a way that continues the work?

The governance question is not only “what can the new system do?” It is “which existing responsibilities is it prepared to carry?” A migration process should answer both. New capability without obligation transfer is not continuity. It is a talented new employee walking into the middle of a live process with a very confident orientation packet.

Organizations already struggle when important knowledge lives only in the person who happens to remember it. It would be a strange achievement to reproduce that dependence at machine speed, then schedule the forgetting as a product improvement.

Otherwise, every upgrade is an exceptionally talented new employee on their first day. Forever.