message-bus

You coordinate distributed agents using a file-based message bus that applies atomic writes, heartbeat tracking, and event-driven signals to prevent race conditions. This ensures reliable inter-agent communication across a track's lifecycle.

A file-based message bus is an append-only queue system using files like queue.jsonl to enable durable, ordered events. It supports safe, auditable communication across workers and directors using shared state files and event signals.

Yes, you can detect deadlocks during multi-agent orchestration by applying heartbeat tracking and lock state expiry checks. The system monitors worker-status.json and locks.json to identify stalled processes and coordinate decisions safely.

You structure board deliberations using governance artifacts like assessments.json, votes.json, and discussion.jsonl. These files support structured governance rounds by capturing director decisions and preserving an auditable trail of the coordination process.

A file-based queue works for distributed systems orchestration across dozens of agents and governance rounds. It applies an append-only event queue with shared status files and safety checks to handle multi-worker coordination effectively.

File locks for agent coordination require simple expiry and safety checks to function reliably. If cleanup workflows are not properly managed, orphaned locks or stale heartbeats in worker-status.json may stall the coordination pipeline.