VCS over FS editions

Stub. Expand after the connectome-fs editions implementation matures. Canonical design: VCS collapse over editions. Semantic units (features/dependencies, not only paths): Semantic change units.

Abstract

When the filesystem provides editions (process-scoped fork bindings over CoW storage), version-control products stop owning:

  • Working-tree checkouts and path juggling

  • Duplicate blob stores for the live tree

  • Destructive “switch branch” as the primary concurrency mechanism

They keep:

  • Remote sync and collaboration policy

  • Semantic / AST-aware merge (and syntax-aware auto-forward for boring patches)

  • Signed history, code review, and release metadata

  • Graph orchestration over edition ids (tags, named lines of work)

Practitioner takeaway (interim)

Until Phase B ships, use the Phase A bridge described in Git concurrency enshittification and the near-term how-to Concurrent agent workspaces. For why path-shaped commits hurt even in one tree, see Git’s file-shaped change model.

Related