A direction for the unavailable self
The Capability Will
When a personal AI stack can carry methods, context, and recurring work, a person needs a way to decide what continues when they cannot govern it themselves.
Record / 01
Continuity is not inheritance.
A capability will is a set of instructions that decides which parts of a personal stack may continue, pass to someone else, or end when its owner cannot govern it.
That question is easy to postpone because digital life has trained us to think in accounts. An account expires, a password is recovered, a subscription is cancelled, and a folder is handed over. But the app-to-stack transition changes the object that may outlast a person’s availability. A stack can hold a working method, a history of corrections, trusted sources, standing permissions, routines for family or clients, and a tone that has learned its owner.
Those things are not all property. Some are intimate. Some are shared. Some should disappear precisely because the person who could revise them is absent. The issue is not only death. Illness, disability, travel, caregiving, and an abrupt change in capacity can all make a person temporarily unable to supervise a system that keeps making suggestions or carrying out a routine.
A Stack Person should not leave a living capability to chance, because continuity without authority can become a quiet form of impersonation.
Three directives, not one transfer.
The continuance register
Directive 01
Continue
Some routines can keep serving a named purpose for a limited period: a household reminder, a bill calendar, a care schedule, an archive of explicit instructions. Continuation needs a named steward, a review date, and a narrow scope.
Directive 02
Transfer
A reusable method may be passed on without transferring every memory that helped form it. A colleague could receive the documented process for a shared project while private notes, unrelated contacts, and personal history remain closed.
Directive 03
End
Some systems should stop immediately. A stack should not keep speaking in an unavailable person’s voice, extending a sensitive permission, or making a consequential recommendation without a current accountable human behind it.
02 / the old default
Accounts were a crude ending.
App People often inherit a familiar mess: logins, device access, documents, subscription charges, and perhaps a social account that needs closing. The applications were designed as containers, so the task is mostly administrative. Find the account. Prove authority. Preserve or delete the files.
Stack People may leave something more active. A research system could continue identifying sources. A care assistant could retain a person’s routine. A client briefing process could know how to assemble a weekly view. A household tool could have access to information that was shared for one purpose and never meant to become family property in general.
None of this requires pretending that a stack is a person. It is not. It does mean that a stack can carry forward enough context to create consequences. The more useful it becomes, the less responsible it is to leave its next action to a platform’s default setting.
03 / the human role
A steward is not a replacement.
The answer is not to give one trusted person unrestricted access to an entire life. That simply recreates the old problem of digital estates at a higher level of intimacy. A capability will should name functions, not hand over a total self: who may keep the family calendar functioning; who may receive a documented project handoff; who may close a particular connection; who may review the system when a condition changes.
This is a useful distinction for organizations too. A worker’s personal stack may contain a general way of planning, checking sources, or recording decisions. The organization is entitled to a lawful handoff of shared work, not to the worker’s private professional memory. Clear continuity instructions make that boundary easier to honor when a person leaves suddenly or cannot participate.
For Stack People, the mature question is not only “What does my system know?” It is “Who is allowed to decide what it does next?” That question puts judgment back where it belongs: with a present human who can understand the stakes and answer for the outcome.
04 / a small practice
Write the stop condition while you can.
A capability will need not be legal paperwork or an elaborate software specification. It can begin as a modest record: the routine; the purpose it serves; the information it uses; the person permitted to review it; the date on which it must stop unless renewed. The point is not to anticipate every catastrophe. It is to make the owner’s intent legible before urgency converts convenience into authority.
Institutions can help by offering humane defaults: exportable instructions, scoped delegation, clear revocation, and workflows that do not require a family or colleague to impersonate the unavailable person. But they should not choose the answer alone. A platform’s incentive is to preserve activity. A person’s instruction may be to preserve care, transfer work, or let a system go quiet.
The stack becomes genuinely personal not when it remembers everything, but when it can honor the limits of the person whose life gave it meaning.