Workspaces and snapshots
Understand canonical project state, attempt-local changes, and immutable workspace versions.
A workspace scopes tenant-owned state. A project scopes research objects inside that workspace. Every project-owned relation includes both identities so a privileged process cannot accidentally connect a child to another workspace's parent.
Immutable handoff
The target runtime materializes an accepted immutable workspace snapshot into an isolated attempt. Agent writes remain local to that attempt until it publishes a reviewed patch manifest against the pinned base digest. Accepting the patch creates a new ordinary workspace artifact; concurrent attempts never write a canonical shared checkout directly.
Current checkpoint
Slice 0 proves workspace and project identity plus immutable result artifacts. Workspace snapshot and patch lifecycles activate with the runtime slice and are not yet a user-facing file editing promise.
Why this matters
Parallel experiments can start from the same accepted inputs and merge through explicit change sets. Provider disks, volumes, Git metadata, and runtime sessions remain reproducibility inputs or diagnostics—not the product database.