inter-squad-signals

You can coordinate cross-squad communication by using a file-based signaling protocol that stores JSON messages in local inbox and outbox directories. This enables reliable directive and report exchange without any network dependencies.

File-based signaling is a coordination mechanism that uses JSON files stored on disk to orchestrate directives, questions, and reports. It eliminates the need for shared memory or network calls while keeping signals auditable and version-controlled.

You can track signal status and acknowledgments using a status.json file combined with structured SignalMessage interfaces. These synchronize processing between meta-squads and domain squads within each worktree's signals directory.

Yes, file-based JSON signals are designed specifically for offline operation and auditability. Storing structured messages in local directories enables version-controlled tracking of cross-squad directives and reports without requiring network services.

You set up signal exchange by initializing a domain worktree and creating inbox and outbox directories under the .squad/signals path. Domain squads then write structured JSON messages to these directories to respond to directives.

Yes, the protocol supports optional telemetry integration for observability and rigorous state lifecycle definitions through archetype plugins. These features provide monitoring capabilities and processing guardrails for signal messages.