The Stack Exit
Leaving a role should not mean either extracting a company’s context or abandoning the judgment a person built while doing the work.
01 / the departure problem
An account can be closed in a minute. A capability cannot.
The stack exit is the deliberate separation of organization-bound context from the portable method a Stack Person has developed while doing the work.
In the application era, an exit was often expressed as a familiar administrative sequence: disable the account, collect the device, reassign the queue, and preserve the files. Those actions still matter. A client record, regulated system, shared commitment, or team decision cannot walk out because it happens to sit beside a person’s working habits.
But personal AI capability makes the boundary harder to see. A useful stack may have helped someone recognize a weak source, sequence a difficult conversation, compare options, or notice when a confident answer needs another check. None of that needs to be copied from an employer’s data to be real. Yet it can be lost if the exit treats every learned method as though it were merely a license seat.
App People were typically separated from capability when their application access ended. Stack People need a more careful distinction. They must return what the relationship owns while retaining the human practice that lets the next capability begin somewhere other than zero.
A stack exit is not a download of work history. It is a clean handoff of shared context and commitments paired with a person’s right to carry forward the judgment they have learned.
This is an argument about how institutions could structure departures, not a claim that every workplace currently does it well. The distinction becomes more urgent as personal methods become more capable and less visible inside ordinary work.
02 / draw the cut line
A responsible exit protects two sides at once.
Neither extraction nor erasure
The organization carries
Context that has a continuing obligation.
- Client, student, patient, partner, or employee material governed by the relationship.
- Shared decisions, delivery commitments, and records a successor needs to understand.
- Permissions, credentials, and access paths that must be removed or reassigned.
- Institution-specific procedures that depend on a team’s current authority.
The person carries
Method that can become future capacity.
- A better way to frame a recurring question before asking a system for help.
- A standard for checking evidence, naming uncertainty, or declining a brittle shortcut.
- A personal practice for reviewing work before it becomes a commitment.
- General learning that did not depend on copying protected context into the next role.
03 / stop calling it theft or loyalty
The false choice makes both sides weaker.
Organizations have a legitimate interest in continuity. When someone leaves, the people still served by the work should not inherit a blank space. That is why the shared side of the stack needs a clear handoff: a record of open decisions, an account of important limits, and a named person who can take responsibility next.
But a continuity requirement can turn into a confiscation instinct. If every habit, prompt structure, source standard, and learned correction is treated as an organization’s property, people have an incentive to keep their real method invisible. The result is not better control. It is a workplace that sees only outputs and loses the chance to develop portable judgment openly.
The opposite failure is just as tempting. A departing person may believe that because a capability felt personal, every trace associated with it is theirs to take. That can pull private material, shared trust, and unfinished commitments into the next relationship. A stack that compounds responsibly must also know what it cannot carry.
The practical question is not who owns every idea. It is whether an exit can identify which context must remain, which access must close, and which learning can travel without injury. That is more precise than treating the person as a temporary user of a vendor’s software—or as an owner of everything they touched.
04 / a departure protocol
Make the handoff before the last day.
- Name the live obligations.List the people, decisions, records, and commitments that need a successor, not merely a folder transfer.
- Close the governed context.Remove access, return protected material, and mark what cannot be reused outside its original relationship.
- Let the method travel.Invite the person to retain their general practices of inquiry, review, and restraint without demanding a private diary or exporting protected data.
05 / a better career signal
A good exit leaves both parties more capable.
The app-to-stack transition changes what a career can accumulate. The First Stack Generation describes people assembling evolving AI capabilities around their own context and judgment instead of continually adapting themselves to fixed applications. That capacity should not require someone to make every former workplace disappear from memory. Nor should it justify carrying away what other people relied on them to protect.
Managers can begin with a modest shift: treat offboarding as a capability event, not only a security event. Ask what must remain intelligible to the team, what permissions are ending, and what kind of learning should be acknowledged as part of a person’s future work. The last question is not sentimental. It makes the organization more likely to receive honest handoffs while people still have a reason to improve their method in the open.
For Stack People, a clean exit is a form of professional authorship. It says: I will leave the relationship’s context where it belongs. I will also leave with the human judgment I earned by practicing the work. That is how a personal stack becomes a durable career asset without becoming a private archive of everyone else’s life.