FG-0509 Asynchronous Communication
Description
Implement structured asynchronous communication channels for team coordination that don't require real-time presence. In human-AI teams, not all participants are available simultaneously. Asynchronous Communication establishes persistent message channels, similar to a team bulletin board, where participants can leave updates, requests, and status reports that others read when they begin their session.
Implementation
Create a persistent, version-controlled communication channel (git-based bulletin board, shared document, or dedicated message log). Define message types (status update, work request, decision request, FYI). Establish a reading cadence (check at session start, check before context-dependent decisions). Archive resolved messages to maintain signal-to-noise ratio.
Success Indicators
- Team members stay informed without requiring synchronous presence
- Important updates are not lost between sessions
- Async messages are read consistently at session start
- The communication channel has manageable volume: signal, not noise
Failure Modes
- Channel overload: too many messages, important ones buried
- No reading cadence: messages posted but not read
- Async used for urgent communication that needs synchronous attention
- Messages without clear action items or resolution criteria