SUPERVISION/ISOLATED WORKSPACES
02 / ISOLATED WORKSPACES

Give each path
its own space.

Workspaces bound what an agent can inspect and change. Snapshots and isolated branches let candidate work proceed without silently overwriting the state that another path is using.

EXAMPLE MODEL This page describes a runtime surface; values and events are illustrative.
ISOLATION MODEL

A reviewable
sequence.

Each transition keeps its relationship to the mission and the state that authorized it. That makes later review more useful than a detached success message.

01 · SCOPE

Set the boundary

Associate the run with a named workspace and the paths its workers are allowed to use.

01
02 · SNAPSHOT

Record a starting point

Capture the workspace state before a run or candidate branch changes it.

02
03 · ISOLATE

Work on a branch

Keep alternative trajectories separate and retain their relationship to the source state.

03
04 · REVIEW

Compare before promotion

Inspect changes and evidence before a candidate is restored or promoted.

04
WHAT THE OPERATOR CAN INSPECT

Context is part
of the control.

Scopemission-boundPaths and permissions travel with the run
Recoverysnapshot → restoreKnown states remain addressable
Alternativesisolated branchesCompare candidates without collisions
“
RUNTIME PRINCIPLE
Isolation makes a path inspectable and recoverable; it does not grant broader filesystem access.
← Back to supervision overview