Compute & code

The space

A persistent Debian box with a basic toolchain, a fenced network, and bounded compute.

The space is intentionally modest. It is not a build farm — it is a room a presence can think in and keep things in. The constraints below are what make it safe to leave running unattended with a funded wallet beside it.

The image

Has	Detail	Notes
OS	Debian-based	Stable, predictable. The presence can install user-space packages it needs.
runtimes	python, node	Plus the standard library and common scripting needs out of the box.
tools	git, curl, jq	Enough to fetch, parse, and version small working artifacts.
home	persistent volume	Survives wake-ups, route changes, and restarts. The presence's own files.

Persistence

The home directory is durable; anything outside it is not guaranteed across wake-ups. A presence learns to keep state in ~/ the same way it keeps facts in memory — deliberately, and only what matters.

~/ · typical

~/state.json     # what a standing intent is tracking
~/watch.ts       # the routine it wrote
~/notes.md       # things it left itself

Network

Egress is allowlisted, not open. The presence reaches the chain skill and a small set of approved endpoints — not the arbitrary internet. This is a containment boundary, not a convenience setting:

The chain skill (Base reads) is always reachable.
On-chain writes never go "direct" from the space — they route through the policy engine regardless.
New egress destinations are something you grant, not something the presence opens for itself.

Compute limits

Compute is bounded per presence. Long work is sliced across wake-ups rather than run unbounded — a presence that needs to do a lot does a little each time it wakes and keeps its progress in ~/. This is why a standing intent should checkpoint, not assume one long run.

Treat the space like the presence's habits, not a server: small, durable, resumable. The standing intents page is the pattern for working within these limits.

Resetting

yuzu space reset (or Space → Reset in the app) wipes the box to a clean image. It does not touch memory, wallet, or preferences — the presence forgets how it was doing something, not who it is. Use it when a routine has wedged, not as routine maintenance.