A profession can support a person without becoming their platform
The Stack Guild
When work travels with the person, collective power must travel with them too.
01 / the missing institution
A personal stack can make a worker more independent and more alone.
App People could join a workplace already organized around the same systems, rules, and managers. The company owned the applications, distributed the logins, set the workflow, and usually decided what good work looked like. That arrangement limited autonomy, but it also concentrated responsibility. A person could point to an employer, a manager, a human-resources policy, or a professional body when the terms of work became unfair or unsafe.
Stack People arrive differently. They bring evolving AI capabilities, personal methods, and accumulated context into many relationships. That can make a person more capable without waiting for an institution to choose the software. It can also make the person look like a tiny independent business expected to negotiate every term alone: what evidence counts, who owns a reusable method, how an automated error is handled, and what happens when a client asks for access to the private system behind the work.
A stack guild is a voluntary association that helps people set and defend shared terms for stack-enabled work while leaving their private capability under their own control. It is not a new platform, a prompt library that owns its members, or an employer in disguise. It is a way to make independence less isolating.
- 01 / terms
Make the exchange legible.
Members can agree on clear language for scope, review, confidentiality, correction, and authorized action before a customer or employer turns a vague request into invisible risk.
- 02 / review
Give judgment a peer.
A person can ask for a second look at a method or boundary without surrendering the private history that made their stack useful in the first place.
- 03 / leverage
Negotiate without starting from zero.
Shared standards give an individual a credible starting point when a larger institution wants the result of a stack but refuses the obligations around it.
02 / not another account
The guild must not become the new landlord.
There is an obvious failure mode. A service could call itself a guild, collect every member’s context, standardize every method, and use the resulting archive to sell access back to the people who created it. That would reproduce the App People bargain under friendlier language: join our system, adapt to our fields, and leave your accumulated capability behind when the relationship ends.
A real stack guild should be narrower and more demanding. It can publish a model engagement rule, teach how to document a decision, provide peer review, maintain a dispute process, or negotiate useful defaults with institutions. It does not need a copy of each member’s private memory, client records, or internal workflow to do those jobs. Its value is in shared terms and shared standing, not in centralized possession of personal context.
This distinction matters because the app-to-stack transition described in The First Stack Generation changes what a person carries into work. The useful thing to protect is not a particular interface. It is the person’s growing ability to direct tools, keep a method, recognize a limit, and choose what should remain private.
03 / the new negotiation
A buyer may want the outcome, not the whole workshop.
Imagine a small firm asking an independent analyst for a fast recommendation. The analyst’s stack can prepare research, compare the supplied documents, surface contradictions, and preserve a careful review routine. The firm is entitled to the agreed recommendation, its evidence, and a clear account of its limits. It is not automatically entitled to the analyst’s private notes, the unrelated context that improved their questioning, or an unrestricted copy of the method they have spent years refining.
The point is not secrecy for its own sake. A stack guild can help members distinguish a legitimate handoff from a demand for extraction. It can also make the analyst’s obligations clearer: name the sources, disclose the role of automation when it matters, correct a material error, and never use a private capability as an excuse for an unaccountable result.
04 / organization after the app
The individual stack needs a collective edge.
The first response to personal AI capability will often be individual: learn faster, automate more, assemble a better private system. That response is understandable, but it is incomplete. Work still involves unequal bargaining power, shared professional standards, disputed mistakes, and institutions large enough to set terms by default.
Stack People should not have to choose between becoming a dependent user inside one vendor’s environment and becoming a solitary contractor responsible for everything. The stack guild names a third possibility: people keep their own evolving capability while building enough collective structure to make its use fair, inspectable, and durable.
The line a useful guild should hold
It should make a member more able to refuse an unreasonable term, explain a responsible boundary, and carry lawful learning into the next relationship. If it requires permanent access to the person’s private stack in return, it has crossed from association into ownership.
The app-to-stack transition does not eliminate institutions. It asks which institutions help a person become more capable without demanding that capability as rent.