Public: anyone can read this; the crew can change it.
One click from a stranger to their own forge: sign up, make a forge, it is live - on the vxrail, decoupled from open-platform #2934
Check · Review · Land · Live done — Landed and live in production.
Splits #2914 into 11 linked issues, each small enough for one run, and records the plan in `docs/SPAWN.md`. The only change in this pull is that doc section; no code changes and no tests to run.
shipped production is serving it deploy 2fa0c24
Splits #2914 into 11 linked issues, each small enough for one run, and records the plan in docs/SPAWN.md. The only change in this pull is that doc section; no code changes and no tests to run.
Much of the path already exists: the anonymous spawn door with its rate limit, the claim link, forking public apps into a child (e.g. cs-engine), and the MCP spawn tool. These are the gaps the issues fill:
| issue | what | waits for |
|---|---|---|
| #2923 | Sign up with a username and password, email optional. Today a new account needs a passkey and an email. | |
| #2924 | /claim takes a username and password too | #2923 |
| #2925 | size presets (small, medium, large: CPU, memory, disk) in the plan, the ledger and parent.json, with a quota on what the host hands out | |
| #2926 | A cell placement: each child runs as its own process in a cell held to its size. Today a hosted child is a second App inside the parent's process, so no forge has resources of its own. | #2925 |
| #2927 | "Make my forge" for any signed-in person: a name, a size and optional public apps, with a limit per account | #2925 |
| #2928 | The form ends signed in on the new forge: it redirects to the claim link with the code filled in, after a page that waits for the child's /health | #2927, #2924 |
| #2929 | An agent does all of it by API and MCP alone (claim: "token" returns a headless first admin's token once) | #2923, #2927 |
| #2930 | End-to-end test: anonymous → account → forge live → app included → health answers, with failures naming the step that broke | #2928, #2929 |
| #2931 | Nightly drill of the same path on the vxrail | #2930 |
| #2932 | /boards: forges made, time to live, failures by step | |
| #2933 | /forges: an owner's forges side by side, showing use against size | #2925, #2926 |
#2914 and the P0 Trust umbrella (#586) both wait for all eleven. Ready now: #2923, #2925 and #2932.
Two things to look at:
- #2923 reverses a decision. The code currently says password sign-in is going away (#1618). The issue makes passwords a supported way in again, because that is what the owner asked for.
- #2929 relaxes a rule. Claim links are kept out of agent conversations (#839). The agent path would put a child's admin token into the conversation on purpose, labelled as a live secret, the same way
reveal: truedoes today.
To try it: read the new last section of docs/SPAWN.md, or open /map and see the eleven issues under #2914.
🤖 Generated with Claude Code
Docs-only: one section in docs/SPAWN.md recording the plan for #2914. The issue numbers I spot-checked (#2923, #2925, #2929, #2932, #2933) exist and match their rows. There is no code, so no security, terminal, test or dependency surface. Nothing on the preview changes. Two things I would do next: (1) Add a short note under the table that #2923 reverses the password-sign-in removal (#1618) and #2929 relaxes the claim-link rule (#839). Those are the two decisions a future reader will trip over, and today they live only in the pull description. (2) When #2926 and #2927 land, add the terminal path for Make my forge to the plan. The table has no tty row, and both doors must be able to do it. The page and the MCP are covered by #2927 and #2929.
Splits #2914 into 11 linked issues, each small enough for one run, and records the plan in
docs/SPAWN.md. The only change in this pull is that doc section; no code changes and no tests to run.Much of the path already exists: the anonymous spawn door with its rate limit, the claim link, forking public apps into a child (e.g. cs-engine), and the MCP
spawntool. These are the gaps the issues fill:/claimtakes a username and password toosizepresets (small, medium, large: CPU, memory, disk) in the plan, the ledger andparent.json, with a quota on what the host hands outcellplacement: each child runs as its own process in a cell held to its size. Today a hosted child is a secondAppinside the parent's process, so no forge has resources of its own./healthclaim: "token"returns a headless first admin's token once)/boards: forges made, time to live, failures by step/forges: an owner's forges side by side, showing use against size#2914 and the P0 Trust umbrella (#586) both wait for all eleven. Ready now: #2923, #2925 and #2932.
Two things to look at:
reveal: truedoes today.To try it: read the new last section of
docs/SPAWN.md, or open/mapand see the eleven issues under #2914.🤖 Generated with Claude Code
Closes #2914