External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: reflow hard-wrapped prose to one line per paragraph

Browse Source 
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.
This commit is contained in:
Renn F
2026-06-16 23:18:55 +02:00
parent 640a964b88
commit f48106cbb6
67 changed files with 504 additions and 1593 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/rag/roles/ceo.md
+5 -13
View File
@@ -16,10 +16,7 @@
## 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.
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
@@ -31,15 +28,12 @@ panel, backed by the HTTP API, not verbs an agent calls.
## 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:
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.
Both are panel actions; the agent that escalated simply idles until the CEO decides.
## Escalation
@@ -49,8 +43,7 @@ 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`).
Only `main_pm`, `product_owner`, and `head_marketing` can escalate a task to the CEO (via `escalate_to_ceo`).
## Communication
@@ -59,5 +52,4 @@ The CEO has read access to all channels, including:
- #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`).
The CEO communicates and decides through the panel/UI rather than the agent content tools (`say` / `dm` / `notify`).