73c05cfa5e
* feat(a2a): CEO can DM the Auditor and PR reviewers
A mid-flight PR reviewer or Auditor that's stuck was unreachable — the CEO
had no way to DM them. Both roles now carry dm/read_a2a, so the CEO can open
a 1:1 and they can reply in-thread through the existing CEO-reply path.
Scoped deliberately: the Auditor stays a silent observer to its peers — it
gains no peer-initiation surface (can_a2a_direct routes it through
_check_auditor_a2a, which refuses every initiation target; it can only reply
inside a CEO-opened DM). PR reviewers keep their owning-PM scope. Intake and
Secretary stay excluded — they have their own dedicated chat pages.
NO_COMMS_ROLES drops to {prompter, secretary}; the panel's EXCLUDE_NON_DM_ROLES
matches. KB/docs updated so the 'auditor/pr_reviewer have no dm' claim isn't
left stale.
* test(a2a): smoke guard checks _NO_COMMS_ROLES, not a hardcoded 'auditor'
The dm() runtime guard no longer names the auditor (it now carries dm to
reply to the CEO); it refuses the canonical _NO_COMMS_ROLES set. Assert on
that set so the smoke test tracks the guard, not a stale role name.
* chore(foundation): regenerate verb tables for auditor/pr_reviewer dm+read_a2a
---------
Co-authored-by: Renn F <rennf93@users.noreply.github.com>
2.4 KiB
A2A Collaboration Workflow
Overview
Agents collaborate directly through the dm content tool on the roboco-do MCP server, with read_a2a to read what you were sent. There is no roboco_agent_* or roboco_a2a_* tool — A2A is just dm + read_a2a.
Key: A2A is about existing tasks, NOT task creation. Pass the task_id you're collaborating on so the message is linked to it.
Flow
1. Reach out → dm(recipient, text, task_id) for a direct message
2. Receive → read_a2a() to read incoming A2A message bodies
→ notify_list() / notify_get(id) to read your notify inbox
Direct Messages (same cell only)
# 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>",
)
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.
The CEO
CEO-initiated conversations may arrive and are replied to in-thread like any other unread A2A.
Receiving Messages — read_a2a
Your claim briefing surfaces incoming A2A under unread_a2a — each entry shows the sender and a preview of their latest message. To read the full bodies (and clear them):
read_a2a() # -> {"messages": [{from_agent, content, created_at}, ...]}
read_a2a() returns only INCOMING messages (never your own sends) and marks them read. It also clears i_am_idle()'s unread-A2A soft-block.
Task Creation Rules
Only PMs create tasks (via the delegate verb). Regular agents cannot create work from a dm.
If a conversation surfaces work that needs a new task:
- Escalate to your Cell PM:
escalate_up(task_id, reason="Needs a subtask for X") - The PM decides whether to
delegatea subtask
Permissions
Most roles can dm (same-cell) and read incoming messages with read_a2a, plus check their notify inbox with notify_list / notify_get.
The Auditor is a silent observer of peers: it never initiates dm to another agent and has no notify. It does carry dm/read_a2a so it can read and reply in-thread when the CEO opens a DM with it — that reply path is stateful (not gated by the peer-initiation rule).
Only PMs and the Board can send ack-required notify signals; regular agents use dm only.