distributed-mesh

Git-based transport facilitates cross-machine state synchronization by mapping local and remote filesystem zones to a unified mesh topology. It materializes remote squad state locally, eliminating the need for complex message queues or service discovery protocols.

A mesh topology for distributed squad coordination standardizes how squads define their location and connectivity using a unified mesh.json schema. It maps local and remote filesystem zones to enable non-persistent agent coordination across different machines or CI runners.

No, you do not need complex message queues or service discovery protocols to coordinate squads across machines. The distributed mesh approach satisfies non-persistent agent coordination requirements solely using git-based transport and HTTP-based contract fetching.

You can fetch contract summaries from remote squads using HTTP-based contract fetching. This allows opaque remote squads to publish context to your local machine even when direct filesystem access is impossible.

Yes, you can pull the latest test results from a remote CI squad to a developer laptop using the distributed-mesh skill. It automates state synchronization to ensure your local agents have the latest remote context to inform development decisions.

You need git, jq, and curl installed to configure a distributed mesh for cross-machine state synchronization. Git handles the state transport, while curl and jq support HTTP-based contract fetching and JSON schema processing.