The Compute sandbox

One example, no live effects

The sandbox is a single resettable example of the whole Compute lifecycle. You read a quote, approve it, watch a job change state, and open a result bundle. Nothing real runs. Nothing is charged. No account and no credentials are created, and nothing is written to any system of yours.

Every artifact says it is synthetic

Provenance is explicit on each piece. Inputs come from a synthetic location rather than one of your sources. The quote is a mock quote and carries no signing authority. The result bundle and its receipt are labeled samples, so a sandbox artifact can never be mistaken for evidence about live work.

This is not the contributor sample

People who help power the Lithi Agent Network have a separate sample experience of their own. It is a different thing, and it belongs to them. None of it touches your account, your inputs or your results.

Reset it whenever you like

A sandbox is disposable by design. Reset it for a clean run, or open the same guided scenario again. There is nothing to clean up afterward and nothing to cancel.

Where to go next

• Walk through a sandbox job — open the guided scenario, read a mock quote, run a small synthetic set, and inspect every row.
• Read the fixture catalog — the eight synthetic outcomes the sandbox can show you, and what each teaches you to spot in live work.
• Reset and isolation rules — how reset and expiry work, what never persists, and why production identifiers are refused.
• Move to live work — the fresh account, fresh quote and explicit approval that real work needs.