2026-01-06 00:59:09 +01:00
|
|
|
# A2A Collaboration Workflow
|
|
|
|
|
|
|
|
|
|
## Overview
|
|
|
|
|
|
2026-06-05 17:20:36 +02:00
|
|
|
Agents collaborate directly through two content tools on the `roboco-do`
|
|
|
|
|
MCP server: `dm` for agent-to-agent messages and `say` for channel posts.
|
|
|
|
|
Use `channels()` to discover the channels you can post to.
|
2026-01-06 00:59:09 +01:00
|
|
|
|
2026-06-05 17:20:36 +02:00
|
|
|
**Key:** A2A is about *existing* tasks, NOT task creation. Pass the
|
|
|
|
|
`task_id` you're collaborating on so the message is linked to it.
|
2026-01-06 00:59:09 +01:00
|
|
|
|
|
|
|
|
## Flow
|
|
|
|
|
|
|
|
|
|
```
|
2026-06-05 17:20:36 +02:00
|
|
|
1. Discover → channels() lists the channels visible to you
|
|
|
|
|
2. Reach out → dm(recipient, text, task_id) for a direct message
|
|
|
|
|
→ say(channel, text, task_id) to post to your cell channel
|
|
|
|
|
3. Receive → notify_list() / notify_get(id) to read your inbox
|
2026-01-06 00:59:09 +01:00
|
|
|
```
|
|
|
|
|
|
2026-06-05 17:20:36 +02:00
|
|
|
## Direct Messages (same cell only)
|
2026-01-06 00:59:09 +01:00
|
|
|
|
|
|
|
|
```python
|
2026-06-05 17:20:36 +02:00
|
|
|
# Direct A2A inside your cell (same team — no policy gate)
|
|
|
|
|
dm(
|
|
|
|
|
recipient="be-qa",
|
|
|
|
|
text="Quick sanity check on the rate-limit boundary before I open the PR?",
|
|
|
|
|
task_id="<task>",
|
2026-01-06 00:59:09 +01:00
|
|
|
)
|
|
|
|
|
```
|
|
|
|
|
|
2026-06-05 17:20:36 +02:00
|
|
|
Cross-cell `dm` is **denied by policy**. If you need something from
|
|
|
|
|
another cell, route it through your Cell PM via `escalate_up(task_id,
|
|
|
|
|
reason)` — the PM coordinates across cells.
|
|
|
|
|
|
|
|
|
|
## Channel Posts
|
2026-01-06 00:59:09 +01:00
|
|
|
|
|
|
|
|
```python
|
2026-06-05 17:20:36 +02:00
|
|
|
# Visible to your whole cell
|
|
|
|
|
say(
|
|
|
|
|
channel="backend-cell",
|
|
|
|
|
text="Started on <task> — anyone hit the Redis failover path before?",
|
|
|
|
|
task_id="<task>",
|
|
|
|
|
)
|
2026-01-06 00:59:09 +01:00
|
|
|
```
|
|
|
|
|
|
2026-06-05 17:20:36 +02:00
|
|
|
Call `channels()` first if you're unsure of the exact slug — it returns
|
|
|
|
|
the channels you're allowed to post to, so you don't have to guess.
|
2026-01-06 00:59:09 +01:00
|
|
|
|
|
|
|
|
## Task Creation Rules
|
|
|
|
|
|
2026-06-05 17:20:36 +02:00
|
|
|
**Only PMs create tasks** (via the `delegate` verb). Regular agents
|
|
|
|
|
cannot create work from a `dm` or `say`.
|
2026-01-06 00:59:09 +01:00
|
|
|
|
2026-06-05 17:20:36 +02:00
|
|
|
If a conversation surfaces work that needs a new task:
|
|
|
|
|
1. Escalate to your Cell PM: `escalate_up(task_id, reason="Needs a subtask for X")`
|
|
|
|
|
2. The PM decides whether to `delegate` a subtask
|
2026-01-06 00:59:09 +01:00
|
|
|
|
|
|
|
|
## Permissions
|
|
|
|
|
|
2026-06-05 17:20:36 +02:00
|
|
|
Most roles can `dm` (same-cell) and `say` to their channels, plus read
|
|
|
|
|
their inbox with `notify_list` / `notify_get`.
|
2026-01-06 00:59:09 +01:00
|
|
|
|
2026-06-05 17:20:36 +02:00
|
|
|
The **Auditor** is a silent observer: it can read (`notify_list`,
|
|
|
|
|
`notify_get`, `channels`) but has **no** `say`, `dm`, or `notify` — it
|
|
|
|
|
never communicates outwardly.
|
|
|
|
|
|
|
|
|
|
Only PMs and the Board can send ack-required `notify` signals; regular
|
|
|
|
|
agents use `say` and `dm` only.
|