Durable filesystem per service

Drives & files

Each Service has a durable drive — the working filesystem that outlives every sandbox. Compute is ephemeral; storage is the identity.

Layout (conventional)

  • /processes/<slug>/ — team homes, SOP working copies, app source
  • /engagements/<id>/ — per-rendering files
  • /shared/ — service-wide reference

Access honesty

Mounts are coarse (volume RW/RO). Path-level rules for humans and plugins are enforced at the workspace FS broker. An agent has raw access to whatever is mounted — finer agent scoping means finer drives, not theater ACLs.

Artifacts that must survive as system of record are also stored in object storage; structured truth lives in the tenant database.

See also: Workspaces overview, Security overview.