03
Engineering control plane
Workspace Ops
An operating model that separates authority, Git state, worktrees, handoffs, lifecycle, and acceptance across sessions and machines.
Operational foundation
- Period
- 2025 — present
- Role
- Systems engineer
Workspace Ops / control flowA state you can resume from
01Authorityscope→
02Statetransition→
03Gitrevision→
04Evidenceacceptance→
Problem
03Across multiple AI sessions and machines, a prompt is not authority and a dirty worktree is not disposable.
Constraints
- Workspace Ops must not take Product or project authority.
- Preserve unknown and dirty work until a human decides.
- Give project, session, machine, revision, and acceptance state distinct owners.
Engineering decisions
- Use typed schemas and durable checkpoints for transitions.
- Limit projections to observers of policy and evidence.
- Fail closed when ownership or provenance is missing.
Implementation
- A Go standard-library control extension in the Workspace repository.
- Session persistence, write-ahead logging, deterministic projections, gates, and fidelity checks.
- Fixture-backed tests for illegal transitions and crash recovery.
Verification / evidence
State modelobserved
The Go extension contains session, gate, projection, repository, and fidelity packages.
Regressionobserved
Tests cover forward lifecycle, prohibited transitions, crash recovery, and deterministic projections.
Authorityreported
Workspace governance is a control-plane surface, not Product ownership.
Result / current state
Workspace Ops turns coordination problems into readable state and explicit gates so complex work can be resumed safely.