[deployer] Composable provisioning product: app catalog, saved setups, and organization creation

mik-tf commented

2026-06-15 22:14:48 +00:00

Owner

Today the deployer creates one member instance at a time with a fixed set of apps. This tracks evolving it into a product for standing up a complete Hero platform from reusable parts, so the same tool can create very different kinds of organizations. A Hero platform is one admin instance plus one or many member instances; a named instantiation of it for a real group (a company, a team, a class) is an organization.

The operator should be able to choose, from a catalog where each Hero app appears as a single item, which apps a member gets. A strong default selection is already chosen so the common case needs no decisions and gives a good experience straight away, and the operator can add more apps up to the full set or remove ones they do not want. A chosen selection can be saved as a named setup and reused, and a setup can be applied to many people at once by entering a list of names, which stands up an organization. Each person created this way becomes a real account on forge.ourworld.tf with its own email and password, and we recommend they turn on Forge two factor sign in.

The result is that one deployer can stand up, for example, a mathematics class for one teacher and twenty five students, or a software team, just by choosing apps and entering names. Every member instance created this way keeps the same reliability and login guarantees as a single one, so creating a larger organization never trades safety for speed.

The naming convention (Hero platform, organization, admin instance, member instance) and the architecture are documented in docs/hero_os/hero-platform.md. Phase 1 (the first shippable product) is done when, from a freshly deployed deployer, an operator can choose apps from the catalog with a strong default, save them as a setup, enter a list of names, and get that many real forge.ourworld.tf accounts, each reachable only behind a login. Phase 1 is home#253 (login floor) plus the catalog (home#286), saved setups (home#287), and organization creation (home#288).

Signed-by: mik-tf mik-tf@noreply.invalid

Today the deployer creates one member instance at a time with a fixed set of apps. This tracks evolving it into a product for standing up a complete Hero platform from reusable parts, so the same tool can create very different kinds of organizations. A Hero platform is one admin instance plus one or many member instances; a named instantiation of it for a real group (a company, a team, a class) is an organization. The operator should be able to choose, from a catalog where each Hero app appears as a single item, which apps a member gets. A strong default selection is already chosen so the common case needs no decisions and gives a good experience straight away, and the operator can add more apps up to the full set or remove ones they do not want. A chosen selection can be saved as a named setup and reused, and a setup can be applied to many people at once by entering a list of names, which stands up an organization. Each person created this way becomes a real account on forge.ourworld.tf with its own email and password, and we recommend they turn on Forge two factor sign in. The result is that one deployer can stand up, for example, a mathematics class for one teacher and twenty five students, or a software team, just by choosing apps and entering names. Every member instance created this way keeps the same reliability and login guarantees as a single one, so creating a larger organization never trades safety for speed. The naming convention (Hero platform, organization, admin instance, member instance) and the architecture are documented in docs/hero_os/hero-platform.md. Phase 1 (the first shippable product) is done when, from a freshly deployed deployer, an operator can choose apps from the catalog with a strong default, save them as a setup, enter a list of names, and get that many real forge.ourworld.tf accounts, each reachable only behind a login. Phase 1 is home#253 (login floor) plus the catalog (home#286), saved setups (home#287), and organization creation (home#288). Signed-by: mik-tf <mik-tf@noreply.invalid>

mik-tf added the

platform

label

2026-06-15 22:14:49 +00:00

mik-tf referenced this issue

2026-06-15 22:15:13 +00:00

[deployer] Show each Hero app as one catalog item with a strong default the operator can extend or trim #286

mik-tf referenced this issue

2026-06-15 22:15:20 +00:00

[deployer] Save a chosen app selection as a named, reusable setup #287

~~mik-tf referenced this issue 2026-06-15 22:15:25 +00:00~~

[deployer] Create many member instances at once from a saved setup and a list of names #288

mik-tf referenced this issue

2026-06-15 22:37:43 +00:00

[deployer] Pre-warm a pool of tester VMs so onboarding is fast and reliable #266

~~mik-tf referenced this issue 2026-06-15 22:53:17 +00:00~~

[deployer] Organizations: manage an organization (its admin instance and member instances) as one unit #289

mik-tf changed title from ~~[deployer] Composable provisioning product: app catalog, saved setups, and group creation~~ to [deployer] Composable provisioning product: app catalog, saved setups, and organization creation

2026-06-16 00:22:31 +00:00

mik-tf referenced this issue from a commit

2026-06-16 00:26:52 +00:00

docs: name the Hero platform model (platform / organization / admin instance / member instance)

mik-tf referenced this issue from a commit

2026-06-16 00:27:58 +00:00

docs(admin): name the operating model (admin instance / member instance / organization)

mik-tf referenced this issue from a commit

2026-06-16 00:28:08 +00:00

docs(manual): name the member instance + polish the manual index

mik-tf referenced this issue from a commit

2026-06-16 00:36:15 +00:00