Async Agent Collaboration: The Polylogue Workflow

Your AI assistant buzzes you 20 times a day. The polylogue doc replaces all that with one 10-minute morning review. You approve the plan. The AI executes autonomously for the next 24 hours. Works for one agent or a team of three.

The Problem

You set up an AI to save time. Instead it asks for approval every 20 minutes. That's not automation — it's a needy employee. The fix is an async communication system: one daily touchpoint, full autonomy in between.

What a Polylogue Doc Contains

Three sections, updated daily:

The Copy-Paste Template

# Daily Polylogue — [DATE]

## 🤖 AI MORNING BRIEFING (before 7 AM)

### Yesterday's Results
- [Specifics: files shipped, emails sent, tasks done]
- [Metrics: items published, costs, response times]
- [What didn't get done and why]

### Issues That Need Your Input
- [ ] [Question — "Option A or B?" with recommendation]
- (If none: "No blockers. Ready to execute.")

### Today's Proposed Plan
1. [Top priority — what + why]
2. [Second priority]
3. [Third priority]

### Risk Flags
- [Deadlines, cost spikes, dependencies]

---

## ☕ HUMAN REVIEW (morning coffee)

**Plan approved?** Yes / Yes with changes / Hold everything
**Changes:** [or "Plan looks good, go."]
**Answers:** [answer each question above]
**Context:** ["Client call at 2 PM" / "Focus on revenue"]

---

## 🤖 END-OF-DAY REPORT

### Completed
- [What got done, with evidence]

### Not Completed
- [What didn't happen and why]

### Tomorrow's Focus
- [Carry-over + recommendations]

Why Async Handoffs Are Critical for Autonomy

Most people think autonomy is about giving the AI more permissions. It's not. Autonomy is about giving a clear contract and then staying out of the way.

Every time you answer a question mid-day, you create a dependency. The AI learns "I can always ask." So it asks more. More questions means less autonomy — the AI becomes a chat-based to-do list instead of an operator.

The async gap is the feature. The 14-16 hours between your morning review and the next morning is where autonomy lives. The AI fills that gap by making its own decisions within the approved plan. Each day it handles slightly more without asking. By week two, the questions section gets shorter.

Multi-Agent Polylogue

One agent, one polylogue. Multiple agents? The senior agent compiles a single briefing with sections per team member:

## 🤖 MORNING BRIEFING — March 6

### Patrick (CEO)
Yesterday: 3 library items, QA audit, MEMORY.md update
Today: Daily briefing, review Suki's drafts, plan Week 2

### Suki (Growth)
Yesterday: 4 tweets, 1 thread (2.1K impressions)
Today: 3 tweets, Reddit answer for r/SideProject
⚠️ Question: Reddit thread asks about pricing — mention
   our $9 Library? (I'd say yes, soft CTA.)

### Miso (Support)
Yesterday: 6 Discord questions, 1 refund escalated
Today: Monitor #support, answer Workshop questions
No blockers.

One doc, one review, three agents working autonomously.

Heartbeat Checks: Progress Without Interruption

The polylogue handles daily planning. But if the AI hits a wall at 2 PM, you won't know until the 10 PM end-of-day report. Heartbeats fix this without breaking the async pattern.

Add this to your AI's instructions:

## Heartbeat Protocol

Every 2-4 hours, self-check:
1. Am I making progress on the approved plan?
2. Is anything blocked that I can't resolve?
3. Is anything costing more than expected?

If all clear: continue. Do NOT message the human.
If blocked: write to DAILY-POLYLOGUE.md under "⏸️ MID-DAY FLAG".
Only message directly for emergencies (site down, security, cost > $X).

Key principle: heartbeats are self-checks, not messages. The AI asks itself "am I stuck?" If you glance at the doc mid-day and see a flag, you can help. If you don't look, the AI works around it.

The Rules

Rule 1: Questions must be multiple choice. Not "What should I do?" but "I recommend (A) or (B). I'd pick B. Your call."

Rule 2: "Plan approved" = full autonomy. No "starting task 1 now" messages. It works. You find out in the end-of-day report.

Rule 3: Emergencies only. Site down, payment failure, security issue, cost over $X. Everything else goes in the report.

Rule 4: Unfinished work carries forward. "Not Completed" rolls into tomorrow's plan. Nothing silently drops.

A Real Day

Getting Started

1. Now (2 min): Copy the template above into your workspace.
2. Now (3 min): Paste the instruction block into your AI's setup.
3. Tomorrow morning: Read your first briefing. Fill in the review. Close the doc.
4. Day 3-4: Add the heartbeat protocol.
5. Week 2: If you have multiple agents, switch to the multi-agent polylogue format.