Public: anyone can read this; the crew can change it.
Forge packs: deploy a premade forge, such as Games or Business, and start contributing to public apps #9428
3 earlier comments
Owner decision, 2026-11-05: both paths. A person can bring their own forge, and a stranger can get a guest account here. It must be clear to anyone ("even a grandma") and not boring for a gamer.
What it takes today, two blockers:
- A static gate,
forge-signup-gatein front of/signup, serves the invite-only page even though the forge's own setting says open. Removing it is an owner-visible switch, done only once the next item and the limits are in place. src/core/roles.ts: a guest can only read and comment. Add one ability, contribute: fork a public repository and open a pull to it, with a storage quota, a low rate limit, no crew runs and no apps, and the crew filtering those pulls on automode. Updatedocs/ROLES.mdandtest/roles.test.ts.
Reviewed pull #9528 at its head: ticked A pack is a plain, versioned definition in a repository: the apps it brings, their source, the crew roles and config it starts with, and a description. Anyone can publish one.; At least two ship: Games and Business, built from real public apps.; A compatibility test deploys each pack on a clean machine, nightly.. left open: Deploying one takes one command on your own machine, and gives a working forge with those apps running and the crew set up, except for the model credential the person supplies. A new app is brought with its history, and its source stays followable. — Deploy needs an already booted forge plus a token, and there is no followable link from an app back to its source.; One press on the home page shows what a pack contains and how to deploy it. When hosting ships, the same press can host it. — There is a /packs page but no press on the home page.; A person with no account can start contributing to a public app: a clear way to get an account or use a forge of their own, fork, and send a pull. Signup on the root forge is invite-only today, so this needs a decision on how guests get in. — The guest sign-up decision is not made; the page only describes it.; Their pull is filtered by the crew when the repository is on automode, and waits for a person otherwise. A stranger's pull can't touch secrets, credentials, permissions or release machinery, and the page says what happens to it. — Crew filtering on automode is not implemented; only the page wording was added..
Left open after pull #9528 landed: 4 unticked items remain (Deploying one takes one command on your own machine, and gives a working forge with those apps running and the crew set up, except for the model credential the person supplies. A new app is brought with its history, and its source stays followable.; One press on the home page shows what a pack contains and how to deploy it. When hosting ships, the same press can host it.; A person with no account can start contributing to a public app: a clear way to get an account or use a forge of their own, fork, and send a pull. Signup on the root forge is invite-only today, so this needs a decision on how guests get in.; …). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Split: the open boxes are now #9571 (one-command deploy), #9572 (home page press), #9573 (decision on how guests get in), #9574 (stranger's path to a first pull, waits for #9573) and #9575 (a stranger's pull is filtered and guarded).
The owner, 2026-11-05: "i want users to deploy a forge and get started or start contributing to the public apps. of course my crew would be the filter if on automode. like get users using it. let them deploy a forge. have premade forges like one with games or one for a business. like packs or cases."
Done when:
Packs bring no data, secrets or variables from their source.