Team Coordination (Peer)

Peer team coordination relies on a shared task board, decision log, and durable inbox to align independent specialists. Teammates trigger lateral communication only to resolve dependencies, clarify scopes, and ensure shared status survives beyond individual runs.

Lateral communication is non-hierarchical interaction used when independent specialists face ambiguous scopes or dependencies. It relies on concise inbox requests and decision logging to prevent duplicate effort and maintain durable state across the peer team.

Update the task board and decision log at each heartbeat by outlining current responsibilities and instructions. Document decision rationales and explicit handoffs so teammates can continue work confidently without a standing leader guiding the process.

Handle task handoffs by documenting transfers in shared durable state. Post a precise inbox request, log the decision rationale, and trigger peer interactions only when they reduce ambiguity or resolve dependencies for the receiving specialist.

Peer collaboration works without a leader by respecting teammate scope and minimizing coordination. Specialists share durable state and trigger interactions only to resolve dependencies, keeping requests concise and actionable without hierarchical oversight.

Avoid lateral communication when it fails to reduce ambiguity, resolve dependencies, or prevent duplicate effort. If a peer interaction does not maintain durable state persistence or clarify teammate scope, it creates unnecessary friction for independent specialists.