Run this on the fleet
The recipe you just previewed in the browser, submitted to the operated fleet. You see the price before you spend it, then the work units as they land.
1. What gets submitted
The same recipe id the browser preview just ran, bound to the parameters carried in this page's URL. A lock replay that changes either binding is refused on binding digest, so these two values are the whole difference between the locked run and an exploration.
- recipe
registry/recipes/landtrendr-change- version
0.2.0- bbox
loading- period
loading- lock sha256
87fb12a17fdfc91238b1ce82439d0bbf30ba8afe54b26caa1b46971f0d16c893- binding digest
48ea45b10f51e9e048b159b40a9e01dcd0834791408663268393d25576bd0033
Gateway
The token is held in memory for this tab and is never written to storage, never put in the URL, and never baked into the build. Close the tab and it is gone. Changing the base clears it: a bearer is scoped to the gateway that issued it.
A ?gateway= link may point this page at localhost, at
folia.sh over https, or at the gateway this build carries — and nothing
else, because whatever base is in effect is where your token gets sent. Any other host
has to be typed into the field above, which is a decision rather than something a link
made for you.
2. The quote, before anything is spent
Bill in parts
| layer | consumer | pool | arrangement | run |
|---|
Tier alternatives
The same store leg priced at every tier the deployment configures, for the arrangement that would actually run. Carry is a monthly figure and is not part of any run total; serving read is advisory — what an out-of-provider reader would pay per GB, against a volume nobody has estimated here — so it is never added in either.
This page declares its own ceiling of
$0.10 on the quote and on the submit, and they
are the same figure by construction. A gateway that charges for remote work refuses
any request that declares none, so the ceiling has to be on the QUOTE for the quote
to be answerable at all; and the ceiling shown above is the one in effect, which is
the lower of this page's and the deployment's own.
3. Confirm, then submit
4. The job
Fan-out
Two channels, one truth. The live one is an authenticated streaming read of
GET /jobs/{id}/events — a fetch rather than an EventSource, because that
route is bearer-gated and an EventSource cannot send the header. It carries liveness
only: the 2.5 second poll of GET /jobs/{id} is what the ledger's locus,
attempts, dispatch provenance and failure reason come from, and it keeps running
whatever the stream does.
Which engine arm ran
Nothing has dispatched yet.
| step | executor | resource | image or version | request |
|---|
Read from steps[].dispatched_to, which the gateway writes at dispatch. A step
the cache probe completed has none, because nothing ran for it. The selected profile is
recorded separately: a profile is what was chosen, not what executed.
Result
Available when the job lands.