distributed-mesh

Git mesh synchronization enables distributed squad coordination by treating git as the transport layer. It generates a mesh.json configuration and bundled sync scripts to share state deterministically across Zone 1 local paths, Zone 2 remote-trusted repos, and Zone 3 remote-opaque contracts.

A git mesh coordinates distributed squads by using git as the transport layer to share state. It organizes machine topology into three zones: local paths, remote-trusted git-backed repos, and remote-opaque published contracts, producing a mesh.json configuration for deterministic state synchronization.

Yes, you need jq, git, and curl installed to execute the bundled sync-mesh.sh and sync-mesh.ps1 scripts. These dependencies are required to parse the mesh.json configuration and interact with remote git repositories during the state synchronization process.

You set up mesh.json for multi-machine squad coordination by answering topology questions during initialization. This generates the configuration file defining your squads, zones, and synchronization targets, copies the sync-mesh scripts to the project root, and records a decision entry in the .squad/decisions inbox.

Yes, you can initialize a Zone 2 shared-state git repo for remote squad synchronization. The initialization workflow optionally sets up this remote-trusted git-backed repository to materialize remote state deterministically and records the setup decision in a mesh inbox.

A limitation of using a git transport mesh for state synchronization is that it requires specific dependencies like jq and curl, and relies on a deterministic workflow. It is designed for specific zone topologies and may not suit scenarios needing real-time centralized state updates.