How agents share information, synchronize work, and avoid conflicts. These patterns describe the communication architecture: shared state files, message buses, escalation flows, and data handoff protocols.
Agents coordinate through shared state files, not direct messaging.
Why: Direct messaging creates hidden dependencies.
Failure mode: Unlogged message causes invisible failure.
Cross-agent workflows use pub-sub through shared state.
Why: Pub-sub decouples agents.
Failure mode: Tightly coupled agents cascade failures.
Timezone handoffs between delivery centers (Virginia, Brazil, India) must include an AI-generated handoff summary posted to the project's Slack channel at the end of each team's working day. The summary includes: work completed, blockers encountered, decisions needed, and next priorities.
Why: We lost 2-3 days per sprint in "context reconstruction" where the next timezone team had to read through Jira comments and Slack threads to figure out where things stood. The handoff summaries cut this to under 30 minutes.
Failure mode: Teams started relying on the AI summary and stopped updating Jira tickets directly. When the summarizer hallucinated a "completed" status for a task that was actually blocked, the downstream team built on top of broken code. We now require Jira status to be the source of truth -- the AI summarizes Jira, it does not replace it.
Weekly AI-generated "Suite Spot" competitive intelligence briefs are produced for the leadership team, tracking competitor platform releases, partnership announcements, and pricing changes across Mirakl, VTEX, commercetools, Shopify, and Salesforce Commerce Cloud ecosystems.
Why: As the publisher of the Marketplace Suite Spot Report, we must maintain the most current competitive intelligence in the industry. Falling behind on a platform capability change directly impacts our advisory credibility.
Failure mode: The brief once missed a commercetools pricing model change because the source was announced via a partner webinar, not a press release. Our monitoring was over-indexed on written publications. We added webinar transcript scanning.
The Proposal Engine and Sales Intelligence Agent share a common client/prospect database. When the Sales Agent qualifies a lead, it pre-loads the Proposal Engine with firmographic data, industry vertical, and likely platform fit so the first draft is contextualized before a human touches it.
Why: Eliminates the "cold start" problem where proposal writers spend the first day just researching the prospect. The agent-to-agent handoff means the proposal draft is already 40% contextualized when the Solutions Architect opens it.
Failure mode: The Sales Agent once passed incorrect revenue data (confused parent company with subsidiary), which caused the Proposal Engine to scope the engagement for a $2B enterprise when the actual buyer was a $90M division. The SA caught it, but it burned half a day re-scoping.
Agents coordinate via INFORM and CHALLENGE messages. No ad-hoc coordination.
Why: Structured messaging creates auditable coordination.
Failure mode: Undocumented side channels. Coordination failures are invisible.
Spec changes trigger INFORM to Market Intelligence for positioning update.
Why: Spec changes affect market positioning.
Failure mode: Marketing claims diverge from product reality.
Competitive threats trigger INFORM to Protocol Steward for format evaluation.
Why: Competitive moves may require protocol evolution.
Failure mode: Protocol falls behind market needs.
Unresolved CHALLENGE messages escalate to founder within 24 hours.
Why: Stalled disagreements block progress.
Failure mode: Two agents disagree. Neither yields. Question hangs for a week.
Data-intensive scans run overnight via OS-level scheduling (17 autonomous agents). The morning briefing reads cached results. The founder wakes to a complete picture, not a wait.
Why: Morning scans take 30+ minutes if run sequentially. Pre-computing overnight eliminates serial latency during the founder's most valuable working hours.
Failure mode: Founder starts the day waiting for scans to complete. First 30 minutes wasted. Or: budget cap hit during overnight run, morning briefing incomplete.
Agents coordinate via structured message bus with defined message types: INFORM (state change notification), REQUEST (action needed), PROPOSAL (joint action), RESPONSE (reply), CHALLENGE (formal disagreement). 3-exchange maximum, then auto-escalate.
Why: Structured messaging makes coordination visible, auditable, and bounded.
Failure mode: Without structure, agents coordinate through undocumented side channels. When coordination fails, no one can trace what happened. Without exchange limits, agents negotiate indefinitely.
When the Data Infrastructure agent detects a critical ad spend overage, it escalates through a defined ladder: alert to the founder, then auto-DM to the COO after 48 hours unanswered, then escalate to the Strategic agent.
Why: Critical alerts that go unanswered create financial risk. Automated escalation ensures someone responds even if the primary recipient is unavailable.
Failure mode: Agent detects +139% overspend on a client account. Alert sits unanswered for 16 days. Client overspends by $1,348 before anyone acts.
The morning briefing compiles output from 10 parallel scanners (Slack, calendar, email, ads, pipeline, projects, call center, meetings, tasks, proposals) into one unified document. Each scanner writes to its own state file. The compiler reads all files and produces a single briefing.
Why: Parallel pre-computation with file-based handoff makes the briefing fast and fault-tolerant.
Failure mode: If one scanner fails, the briefing still compiles with a "stale data" warning for that source. Without this architecture, one API failure blocks the entire briefing.
When the Executive Assistant processes inbound email auto-replies (bounces, out-of-office, contact changes, acquisitions), it automatically routes actionable intelligence to the Sales agent's inbox without the founder in the middle. The Sales agent uses this to update prospect records and adjust outreach sequences.
Why: Cold outreach generates intel (bounces, acquisitions, role changes) the Sales agent needs immediately. Founder routing adds 6-24 hour delay for mechanical handoffs.
Failure mode: Without auto-routing, Sales sends to bounced addresses for days or misses acquisitions. Founder becomes bottleneck for data that should flow between agents directly.
17 overnight agents pre-compute data. Morning briefing reads cached results.
Why: Eliminates 30+ min serial latency during founders most valuable hours.
Failure mode: Founder starts the day waiting for scans instead of acting.
Agents coordinate via structured message bus with 5 message types and 3-exchange limit.
Why: Structured messaging makes coordination visible and bounded.
Failure mode: Without structure, agents coordinate through undocumented side channels.
Critical alerts auto-escalate: founder, then COO after 48h, then Strategic agent.
Why: Unanswered critical alerts create financial risk.
Failure mode: Agent detects +139% overspend. Alert unanswered 16 days. Client overspends $1,348.
Morning briefing compiles 10 parallel scanners into one unified document.
Why: 10 data sources cannot be queried sequentially in under 5 minutes.
Failure mode: One scanner failure blocks entire briefing without fault-tolerant architecture.