Teams & boilerplates
Same stack for everyone, separate computers.
An organization publishes boilerplates — project templates with the stack, skills, and playbooks already wired. Members pull them onto their own machines.
Why separate computers
Nobody shares state: every person works on their own machine, so one runaway session can never slow a teammate down, and access ends cleanly when someone leaves.
- Publish once — every pull starts from the same known-good setup.
- Budgets and usage are visible per machine, so spend never surprises you.
- Members, groups, and roles decide who can pull and publish.