What problem does it solve?
AI agent teams working on isolated statistical software development pipelines lack a standardized, tamper-proof method to share critical updates, user input requests, and interface change notifications across teammates, risking lost messages, broken downstream workflows, and incomplete audit trails.
Core Features & Use Cases
- Append-Only Mailbox Structure: Prevents message deletion, editing, or reordering to maintain a permanent, unaltered audit trail of all cross-teammate communication.
- Standardized Message Types: Supports three distinct message types (INFO, HOLD_REQUEST, INTERFACE_CHANGE) with clear routing rules to ensure the team leader dispatches the correct actions for each update.
- Clear Leader Responsibilities: Defines exact steps for the leader to process mailbox messages, including forwarding hold requests to users and notifying downstream agents of interface changes.
- Use Case: When a builder renames a core function used by the tester and scriber, they send an INTERFACE_CHANGE message to the mailbox; the leader automatically includes this update in the dispatch prompts for both downstream teammates, eliminating broken dependencies.
Quick Start
Use the mailbox protocol to send a HOLD_REQUEST message to the team leader when you need user input to proceed with your assigned development task.