Renn F
ecea593a51
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.
3.9 KiB
Permissions Reference
What each role can do in the system.
Permission Levels
| Level | Roles |
|---|---|
| CEO | ceo, system |
| BOARD | product_owner, head_marketing |
| AUDITOR | auditor |
| MAIN_PM | main_pm |
| CELL_PM | cell_pm |
| CELL_MEMBER | developer, qa, documenter |
Task Permissions
| Action | CEO | Board | Auditor | Main PM | Cell PM | Dev | QA | Doc |
|---|---|---|---|---|---|---|---|---|
| View All | Yes | Yes | Yes | Yes | - | - | - | - |
| View Own | - | - | - | - | Yes | Yes | Yes | Yes |
Create (delegate) |
- | - | - | Yes | Yes | - | - | - |
| Assign | - | - | - | Yes | Yes | - | - | - |
| Cancel | Yes | - | - | Yes | Yes | - | - | - |
Complete (complete) |
- | - | - | Yes | Yes | - | - | - |
| Claim | - | - | - | Yes | Yes | Yes | Yes | Yes |
Pass QA (pass) |
- | - | - | - | - | - | Yes | - |
Fail QA (fail) |
- | - | - | - | - | - | Yes | - |
Docs Complete (i_documented) |
- | - | - | - | - | - | - | Yes |
Notes (verified against roboco/foundation/policy/lifecycle.py):
- Create / Assign (
create_subtask,delegate) are PM-only:cell_pmandmain_pm. The Board (Product Owner, Head Marketing), Auditor, and CEO do NOT create or assign tasks via the gateway. - Cancel is allowed to PM roles + CEO (
cell_pm,main_pm,ceo). The Board and Auditor CANNOT cancel. - Complete (final approve/merge) is PM-only (
cell_pm,main_pm). The CEO acts only on tasks escalated toawaiting_ceo_approval. - Claim is role-matched: developers claim code tasks, QA claims
awaiting_qa, documenters claimawaiting_documentation. PMs can claim the planning/coordination work assigned to them.
Index Permissions
| Action | CEO | Board | Auditor | Main PM | Cell PM | Dev | QA | Doc |
|---|---|---|---|---|---|---|---|---|
| Index Code | Yes | - | - | Yes | Yes | Yes | - | - |
| Index Docs | Yes | Yes | - | Yes | Yes | Yes | - | Yes |
| Search/Query | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| View Stats | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Clear Index | Yes | - | - | Yes | - | - | - | - |
| Refresh Index | Yes | - | - | Yes | - | - | - | - |
Note: Board (Product Owner, Head Marketing) can only index docs, not code.
Notification Permissions
Sending notifications means calling the notify(target, text, priority)
content tool. The sender allowlist is NOTIFY_SENDER_ROLES in
roboco/foundation/policy/communications.py.
| Role | Can Send (notify) |
Scope |
|---|---|---|
| ceo | Yes | All |
| product_owner | Yes | Management chain |
| head_marketing | Yes | Management chain |
| auditor | No | - (silent observer) |
| main_pm | Yes | All |
| cell_pm | Yes | Own cell |
| developer | No | - |
| qa | No | - |
| documenter | No | - |
Non-senders (developer, qa, documenter, auditor) still communicate via
say(channel, text) for channel posts and dm(recipient, text) for direct
agent-to-agent messages — those are not ack-required notifications. The
Auditor is restricted further: it has note(scope=reflect) + evidence +
read-only notify_list/notify_get/channels, and NO say/dm/notify.
Task-Creator Roles
These roles can create/assign tasks (create_subtask, delegate — PM-only
per lifecycle.py):
main_pmcell_pm
The Board (product_owner, head_marketing), the Auditor, and the CEO do
NOT create or assign tasks through the gateway.
Cancellation Roles
These roles can cancel tasks (the cancel action's allowed_roles in
lifecycle.py = PM roles + CEO):
cell_pmmain_pmceo
Note: the Board and Auditor CANNOT cancel (observe/approve only).
View Scope
| Role | Can View |
|---|---|
| CEO | All tasks |
| Board | All tasks |
| Auditor | All tasks (silent) |
| Main PM | All tasks |
| Cell PM | Own cell + cross-cell |
| Cell Member | Own cell |