Public: anyone can read this; the crew can change it.
Elastic compute: with a cloud account connected, a forge that does not fit on owned machines runs on a rented one, steered by the profit slider #11656
Picked up by scout; no pull came of it (failed) · 2 runs · run
2 earlier comments
Parked by the crew: the run ended without a pull: declined: this issue orders a spike on one real rented machine before anything else is built, and I can't run it. It must show that bwrap --unshare-user works there, give the cold wake time with a volume atta
Parked by the crew: the run ended without a pull: declined: this issue orders a spike on one real rented machine before anything else is built, and I can't run it from here. The sandbox reaches only the forge, the package registry and this app's own deployment
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: this issue orders a spike on one real rented machine before anything else is built, and I can't run it. It must show that
bwrap --unshare-userworks there, give the cold wake time with a volume atta - the run ended without a pull: declined: this issue orders a spike on one real rented machine before anything else is built, and I can't run it from here. The sandbox reaches only the forge, the package registry and this app's own deployment
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Deferred behind the Later gate (#595). Why: the owner's direction of 2026-11-12 puts the v1.0.0 list first and elastic compute is not on it (the cloud host #11145 comes right after v1.0.0); and both tries stopped on the same wall — the first step is a spike on one real rented machine (bwrap --unshare-user there, cold wake with a volume attached), which a builder's sandbox cannot reach. When the gate opens, that spike is a person's or the steward's step with a cloud token, and the build splits from its findings.
Why. "i want to connect to a cloud service provider to add elastic compute and use the profit slider." Today Settings → Economics shows the slider at 50 ("cloud takes work above 85% of owned capacity"), but placement reads "no cloud body: bursts queue", no cloud account is connected, and every price is 0. Measured this week: a building forge uses about 3 cores for under a minute and idles near zero; the owned machine has 72 CPUs and at most 8 forges awake.
What.
<name>--forgeaddress through the existing edge. One forge per machine for isolation; the machine is sized to the forge's plan.Order. First a spike that proves, on one real machine: the crew's sandbox works there (
bwrap --unshare-user), cold wake time with a volume attached, and the real cost of an idle and a busy forge of each size. Write the numbers in docs/CLOUD.md with a go or no-go before building the rest. (This replaces the parked spike #11145.)Acceptance. With the owned side forced full in a test, a new forge lands on a (fake) cloud body, sleeps to zero machines, wakes on a request with its data intact, and moves home when room returns; the spend ceiling stops creation at its limit; the orphan sweep removes a planted stray. On production: one real forge runs on a rented machine through a sleep and a wake, and Settings → Economics shows its true cost.