Files
roboco/docs/rag/architecture/permissions.md
T
Renn F f48106cbb6 docs: reflow hard-wrapped prose to one line per paragraph
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.
2026-06-16 23:18:55 +02:00

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_pm and main_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 to awaiting_ceo_approval.
  • Claim is role-matched: developers claim code tasks, QA claims awaiting_qa, documenters claim awaiting_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_pm
  • cell_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_pm
  • main_pm
  • ceo

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