External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: reflow hard-wrapped prose to one line per paragraph

Browse Source 
Markdown and editors soft-wrap on their own, so the manual ~75-char line
breaks across the docs added nothing but noise. Join wrapped prose, list
items, and paragraphs into single lines across 67 docs — README, CLAUDE.md,
deployment, usage, the RAG knowledge base, and the agent role prompts.
Whitespace-only: code fences, tables, and blockquote alerts are byte-identical
and the change is token-verified (no content altered). Applied with a
deterministic reflow tool (committed separately).

Also lands two doc edits that were awaiting commit: the measured under-load
resource numbers in usage.md and the pr_reviewer additions to the
org-structure RAG doc.
This commit is contained in:
Renn F
2026-06-16 23:18:55 +02:00
parent 640a964b88
commit f48106cbb6
67 changed files with 504 additions and 1593 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/rag/workflows/a2a-collaboration.md
+8 -19
View File
@@ -2,12 +2,9 @@
## Overview
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.
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.
**Key:** A2A is about *existing* tasks, NOT task creation. Pass the
`task_id` you're collaborating on so the message is linked to it.
**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
@@ -29,9 +26,7 @@ dm(
)
```
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.
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
@@ -44,13 +39,11 @@ say(
)
```
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.
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.
## Task Creation Rules
**Only PMs create tasks** (via the `delegate` verb). Regular agents
cannot create work from a `dm` or `say`.
**Only PMs create tasks** (via the `delegate` verb). Regular agents cannot create work from a `dm` or `say`.
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")`
@@ -58,12 +51,8 @@ If a conversation surfaces work that needs a new task:
## Permissions
Most roles can `dm` (same-cell) and `say` to their channels, plus read
their inbox with `notify_list` / `notify_get`.
Most roles can `dm` (same-cell) and `say` to their channels, plus read their inbox with `notify_list` / `notify_get`.
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.
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.
Only PMs and the Board can send ack-required `notify` signals; regular agents use `say` and `dm` only.