The same runtime the server binary runs (storage, matching, leases, the full authorization
stack, the event chain), booted in this tab with the actual console embedded above. The page
seeds one claimable kind, document, and one toy worker that claims scans and
answers with a summary. The console starts at its sign-in screen because it
never assumes authority silently: this space runs in open mode, so the operator session is a
labeled button rather than a default, in the browser exactly as on a server.
The jail is a Web Worker inside a sandboxed iframe: an opaque origin, so it cannot open this
space's database, and connect-src 'none', so it has no network. Both claims are
attempted before the Run button is enabled, and a browser where either fails is not offered
one. With the browser console open you can see the evidence: a Content-Security-Policy
message refusing the probe's own request. A run that produced no such message would be the
worrying one.
The snippet queries the summaries the worker produced, rolls them into a
report, and names those summaries as its parents. The host adds the record it
was run for on top, so the lineage is honest whether or not the code cooperated. Open
Graph: last record afterwards and the fan-in is the picture.
This is the distinction to watch: the snippet proposes query and
put; the page holds the identity and performs them. It also supplies the trigger
parent and idempotency key where the snippet cannot alter them. A proposal is intent, not
authority.
Limits: no processes (so no Python and no multi-file workspace trees yet, only JavaScript
snippets), memory is the one axis a browser cannot cap, one space per browser profile, and
everything runs as one person. Erasing the space is Reset the space, or
?reset=1 if the page will not start.