mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00

Files

T

Renn F ecea593a51 docs(rag): rewrite the KB docs to the real gateway verb surface

The RAG knowledge base (indexed and queried by agents at runtime)
described entire fictional MCP tool surfaces — roboco_task_*,
roboco_journal_*, roboco_message_send, roboco_notify_send, roboco_agent_*,
roboco_session_*, roboco_workspace_*, roboco_project_* — that don't exist,
so agents searching the KB were handed invented tool names.

Rewrite every affected doc (tools, roles, workflows, troubleshooting, and
the stale architecture snippets) to the real surface: the gateway intent
verbs (give_me_work, i_will_work_on, open_pr, i_am_done, claim_review,
pass, fail, claim_doc_task, i_documented, triage, delegate, i_will_plan,
unblock, complete, escalate_up, escalate_to_ceo, ...) and content tools
(commit, note(scope=...), say, dm, evidence, notify*, open_session,
channels). Also reconcile the access-control docs to code: CEO can cancel
(Board/Auditor cannot); the management-channel membership and the
Auditor's silent-but-present status now match communications.py.

2026-06-05 17:20:36 +02:00

2.7 KiB

Raw Blame History

Messaging Tools

There is no roboco_message_*, roboco_notify_send, or roboco_session_* tool. Messaging is a small set of content tools on the roboco-do MCP server. They are role-scoped at spawn time.

Channel post — `say`

say(channel="backend-cell", text="Starting work on rate limiting", task_id=task_id)

channel is the slug WITHOUT a leading #.
task_id is auto-filled from your active task if omitted.
Write access varies by role; the gateway returns not_authorized and lists the channels you can write to.

Don't invent channel slugs. Call channels() first if unsure:

channels()   # -> {"writable": [...], "readable": [...]}

Valid slugs: cell channels (backend-cell, frontend-cell, uxui-cell); cross-cell (dev-all, qa-all, pm-all, doc-all); management (main-pm-board, board-private); broadcast (announcements, all-hands).

Direct message (A2A) — `dm`

dm(recipient="be-qa", text="Quick sanity check: ...", task_id=task_id)

recipient is an agent slug (be-pm, be-dev-1, ceo, ...).
Auto-creates the conversation; task_id auto-fills from your active task.
Same-cell only. Cross-cell DM is denied by policy — route through your Cell PM via escalate_up(task_id, reason).

Formal notification — `notify` (PM / Board only)

notify creates an ack-required notification (distinct from the informal say/dm). Only PM roles and the Board may send it; devs / QA / docs use say and dm.

notify(target="be-dev-1", text="Task ready for you", priority="normal", task_id=task_id)

priority is normal | high | urgent. task_id auto-injects from the active task when omitted.

Receiving notifications

Every role with an inbox gets these (so i_am_idle() doesn't soft-block on unread items):

notify_list(unread_only=True, limit=20)   # your inbox
notify_get(notification_id)               # read one (marks it read)
notify_ack(notification_id)               # acknowledge after handling

When i_am_idle() reports unread A2A or @mentions, list -> get -> ack, then idle again. (The Auditor gets notify_list/notify_get for inbox visibility but does not ack.)

Sessions (PM-or-up only)

Devs / QA / docs participate via channels and DMs and do not open sessions. PMs and the Board link discussion threads to tasks:

open_session(task_id, channel="backend-cell", topic="Feature X kickoff",
             relationship_type="discussion")
link_session(session_id, task_id, is_primary=False)

relationship_type is discussion | planning | review | retrospective. link_session is idempotent; you must own the task you're linking.

2.7 KiB Raw Blame History