distributed-mesh

Coordinate distributed squads across machines by using a git-backed mesh to share state and decisions. This approach generates a mesh.json file and copies sync scripts into your project root to synchronize work without centralized services.

A git-backed mesh is a synchronization mechanism that uses git as the transport layer to share squad state and decisions. It replaces centralized services by relying on state repos and bundled sync scripts to maintain a shared mesh view.

Set up a distributed mesh by answering topology questions about your zones and squads. The workflow then generates mesh.json, copies bundled sync scripts to your project root, initializes Zone 2 state repos, and records a mesh-setup decision.

You do not need a centralized service to synchronize state across remote squads. The mesh uses git as the transport layer, scaffolding state storage and placeholder summaries within state repos to share decisions across local, remote-trusted, or remote-opaque zones.

You can use this mesh synchronization for CI runners and multi-VM experiments. It supports cross-machine development and partner collaborations by initializing state repos and generating a shared mesh view for squads spanning different zones.

Running the squad mesh sync scripts requires jq, git, and curl installed on your machine. These dependencies allow the workflow to generate mesh.json, copy bundled scripts, and initialize state repos without modifying your code.