VCS over filesystem editions

Stub. Expand after the connectome-fs editions implementation matures. Canonical design: VCS collapse over editions.

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

  • 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.

Related