Skip to main content
Use a named snapshot as a stable input and give each job its own branch. The compute environment can disappear without taking the branch data with it. This workflow assumes corpus contains the shared input data.
1

Save the input state

2

Create a branch for the job

Use a unique branch name for each run:
Run the mount as a long-lived process in the sandbox or job environment.
3

Point the job at the mount

From another process in the same environment:
Replace ./run-job with your workload command. The program does not need an Amulet-specific storage adapter; it reads and writes the mounted paths.
4

Save and unmount the result

Wait for the mount process to exit before terminating the environment.

​
Inspect the result later

Mount the saved result from another machine:
The snapshot is read-only. Mount corpus@run-001 without --snapshot if the next job must continue writing to the branch.
Do not send multiple independent jobs to the same writable branch. Give each job a branch and preserve selected results as snapshots.