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.
78 lines
1.7 KiB
Markdown
78 lines
1.7 KiB
Markdown
# Escalation Chain Reference
|
|
|
|
Complete escalation mapping for all agents.
|
|
|
|
## Chain Overview
|
|
|
|
```
|
|
Cell Members → Cell PM → Main PM → Product Owner → CEO
|
|
```
|
|
|
|
## Full Mapping
|
|
|
|
| Agent | Escalates To |
|
|
|-------|--------------|
|
|
| `be-dev-1` | `be-pm` |
|
|
| `be-dev-2` | `be-pm` |
|
|
| `be-qa` | `be-pm` |
|
|
| `be-doc` | `be-pm` |
|
|
| `fe-dev-1` | `fe-pm` |
|
|
| `fe-dev-2` | `fe-pm` |
|
|
| `fe-qa` | `fe-pm` |
|
|
| `fe-doc` | `fe-pm` |
|
|
| `ux-dev-1` | `ux-pm` |
|
|
| `ux-dev-2` | `ux-pm` |
|
|
| `ux-qa` | `ux-pm` |
|
|
| `ux-doc` | `ux-pm` |
|
|
| `be-pm` | `main-pm` |
|
|
| `fe-pm` | `main-pm` |
|
|
| `ux-pm` | `main-pm` |
|
|
| `main-pm` | `product-owner` |
|
|
| `product-owner` | `ceo` |
|
|
| `head-marketing` | `ceo` |
|
|
| `auditor` | `ceo` |
|
|
|
|
## Cell PM for Team
|
|
|
|
| Team | Cell PM |
|
|
|------|---------|
|
|
| `backend` | `be-pm` |
|
|
| `frontend` | `fe-pm` |
|
|
| `ux_ui` | `ux-pm` |
|
|
|
|
## Escalation Tool
|
|
|
|
```python
|
|
escalate_up(
|
|
task_id="uuid-here",
|
|
reason="Need clarification on requirements"
|
|
)
|
|
```
|
|
|
|
Auto-routes to your escalation target. You CANNOT choose a different
|
|
target. `escalate_up` is a PM verb (Cell PM / Main PM); cell members
|
|
(devs, QA, documenters) signal blockers with `i_am_blocked(task_id,
|
|
reason)`, which their Cell PM resolves.
|
|
|
|
## CEO Escalation (Main PM / Board Only)
|
|
|
|
```python
|
|
escalate_to_ceo(
|
|
task_id="uuid-here",
|
|
reason="Major feature ready for approval"
|
|
)
|
|
```
|
|
|
|
Requirements:
|
|
- Task in `awaiting_pm_review`
|
|
- PR exists
|
|
- Only Main PM, Product Owner, or Head of Marketing can call this
|
|
(Cell PMs cannot — they `escalate_up` to Main PM first)
|
|
|
|
## Cannot Skip Levels
|
|
|
|
System enforces chain:
|
|
- Developer CANNOT escalate directly to Main PM
|
|
- Cell PM CANNOT escalate directly to CEO
|
|
- Each level must acknowledge and decide
|