App to Stack ownership terms
The Method License
A Stack Person should be able to let an organization benefit from a working capability without surrendering the private stack that makes the capability portable.
01 / the ownership problem
A useful result does not require a total handover.
The app era made the boundary simple: the employer supplied the software, the employee used it, and most of the operational memory stayed inside the company system. The stack era makes that arrangement incomplete.
Stack People increasingly arrive with their own ways of researching, checking, drafting, organizing, and returning to work. Those ways may combine private notes, repeatable prompts, personal standards, small tools, and lessons accumulated across ordinary life. They are not merely a faster route through the employer’s app. They are a capability that can travel.
That is valuable to an organization, but it creates an avoidable mistake. A company can reasonably need the client record, the work product, the decision history, and the institution-specific procedure. It does not automatically need every private habit, reusable template, or general method that helped a person make the work better.
A method license is a limited permission for an organization to benefit from a Stack Person’s working capability without claiming the personal stack that produced it.
This is an argument for clearer terms, not a claim that every method is private or every organization is entitled to nothing beyond a final file. The boundary will vary with role, law, confidentiality, investment, and contract. The point is to name the question before convenience turns into extraction.
02 / a different agreement
From assignment to scope.
These are not legal categories. They are a practical way to notice how quickly “show us how you did it” can become “give us the system that lets you do it everywhere.”
App-era default
The environment is supplied.
- Work happens inside fixed company tools.
- Process knowledge accumulates where the tools live.
- Leaving often means beginning again in a new interface.
- Training is mostly a matter of access and procedure.
Stack-era question
The environment may be partly personal.
- The organization can specify safe inputs, outputs, and review.
- The person can retain a private method that does not expose company facts.
- Reusable capability can leave while institutional records stay put.
- Training becomes a question of stewardship, not just tool access.
A good method license separates three things. First, the organization owns its facts: its customers, confidential materials, decisions, systems of record, and any work specifically commissioned under agreed terms. Second, the person owns a portable practice: general ways of framing problems, checking sources, managing attention, or creating a working sequence. Third, there is a live collaboration zone where the two meet. That zone needs explicit rules about what enters, what leaves, and what may be retained.
Without that separation, both sides lose. Organizations either prohibit personal stacks entirely and force capable people back into slow, generic interfaces, or they accept invisible systems they cannot inspect. Workers either surrender an asset they have compounded over years or conceal the very methods that could make their contribution more reliable.
03 / the working clauses
Make a capable contribution inspectable without making a person’s whole stack corporate property.
01 / boundary
Name the approved material.
Specify which records, tools, models, and destinations may be used. A private method does not authorize a private route around confidentiality or a company policy.
02 / evidence
Ask for grounds, not a handover.
Require the sources, assumptions, version, and human review appropriate to a consequential result. That makes the work accountable without demanding every private intermediate thought.
03 / return
Leave the institution able to continue.
If a role changes hands, preserve the active obligation, the authorized records, and the next decision. Continuity should not require copying a person’s entire personal stack.
Open the practical test
When a team asks someone to “share their AI workflow,” ask two questions first: What institutional outcome must remain usable after this person leaves? And what portable method can remain theirs while that outcome is still delivered safely? If the request cannot answer both, it is not ready to become a policy.