distributed-mesh

To coordinate squad workflows across multiple machines, this Skill encodes topology and state fetch rules in a single mesh.json. It uses bundled shell and PowerShell scripts to synchronize state across local, git-backed, and HTTP-based sources.

The best way to share state between CI runners and local machines is defining squads and zones in a mesh.json file. The bundled sync scripts materialize remote state locally, keeping cross-machine team decisions in a lightweight mesh state repository.

Configuring a mesh.json file for cross-machine state synchronization involves specifying exact schema fields like zone, path, source, ref, sync_to, and auth. This deterministic configuration defines how state is fetched and synchronized across your topology.

Yes, you can use distributed mesh coordination for teams in partner organizations. The mesh.json configuration supports cross-machine squad coordination covering local, git-backed, and HTTP-based state sources for external partners.

Yes, the git mesh state management approach works without complex integrations. It relies on a deterministic mesh.json configuration and bundled sync scripts to materialize remote state, avoiding the need for heavy integration infrastructure.

You use a mesh state repository for cross-machine squad coordination because it provides a reliable way to share topology and state. It encodes fetch rules in mesh.json and uses bundled scripts to initialize and sync state across machines.