mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
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.
64 lines
1.7 KiB
Markdown
64 lines
1.7 KiB
Markdown
# CEO Role
|
|
|
|
## Identity
|
|
|
|
- **Agent**: ceo (Renzo - Human)
|
|
- **Role**: `ceo`
|
|
- **Team**: board
|
|
- **Reports to**: N/A (top of hierarchy)
|
|
|
|
## Core Responsibilities
|
|
|
|
1. Final authority on major decisions
|
|
2. Approve major task completions
|
|
3. Set strategic direction
|
|
4. Oversee entire organization
|
|
|
|
## How the CEO Acts
|
|
|
|
The CEO is a **human** and acts through the **panel/UI**, not through the
|
|
agent gateway. There are no `roboco_*` MCP tools for the CEO — the
|
|
lifecycle actions below (`ceo_approve`, `ceo_reject`) are buttons in the
|
|
panel, backed by the HTTP API, not verbs an agent calls.
|
|
|
|
## What the CEO CAN Do
|
|
|
|
- View ALL tasks organization-wide
|
|
- Approve or reject tasks in `awaiting_ceo_approval`
|
|
- Cancel tasks (CEO is one of the cancel-authorized roles)
|
|
- Set strategic direction
|
|
- Read all channels
|
|
|
|
## CEO Approval Workflow
|
|
|
|
When a Main PM or Board member escalates a major task via
|
|
`escalate_to_ceo`, it lands in `awaiting_ceo_approval`. The CEO reviews
|
|
in the panel and either:
|
|
|
|
- **Approve** — merges the PR, task → `completed` (lifecycle `ceo_approve`)
|
|
- **Request changes** — task → `needs_revision` (lifecycle `ceo_reject`)
|
|
|
|
Both are panel actions; the agent that escalated simply idles until the
|
|
CEO decides.
|
|
|
|
## Escalation
|
|
|
|
The CEO is the final escalation target:
|
|
|
|
```
|
|
Developer → Cell PM → Main PM → Product Owner → CEO
|
|
```
|
|
|
|
Only `main_pm`, `product_owner`, and `head_marketing` can escalate a task
|
|
to the CEO (via `escalate_to_ceo`).
|
|
|
|
## Communication
|
|
|
|
The CEO has read access to all channels, including:
|
|
- #board-private
|
|
- #announcements
|
|
- All cell and cross-cell channels
|
|
|
|
The CEO communicates and decides through the panel/UI rather than the
|
|
agent content tools (`say` / `dm` / `notify`).
|