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/workflows/escalation.md
+5 -14
View File
@@ -14,14 +14,9 @@ Developer/QA/Documenter
CEO
```
`escalate_up` walks this chain **one rung at a time** — it auto-routes to
your immediate escalation target; you cannot choose a higher level or skip
a rung.
`escalate_up` walks this chain **one rung at a time** — it auto-routes to your immediate escalation target; you cannot choose a higher level or skip a rung.
The one exception is `escalate_to_ceo`: it is a **separate** verb,
available only to Main PM and the Board (Product Owner / Head of
Marketing), that goes straight to the CEO for final approval of a major
task. It is not part of the `escalate_up` chain.
The one exception is `escalate_to_ceo`: it is a **separate** verb, available only to Main PM and the Board (Product Owner / Head of Marketing), that goes straight to the CEO for final approval of a major task. It is not part of the `escalate_up` chain.
## How to Escalate (up one rung)
@@ -51,9 +46,7 @@ Auto-routes to your escalation target (you cannot choose it).
| **Escalate** | Need a decision / help from above | `escalate_up` |
| **Block** | Can't proceed on an external dependency | `i_am_blocked` |
There is no agent-facing "pause" verb. If you need to step off a task you
claimed but haven't progressed, use `unclaim(task_id)` to return it to
the pool.
There is no agent-facing "pause" verb. If you need to step off a task you claimed but haven't progressed, use `unclaim(task_id)` to return it to the pool.
## Blocking a Task
@@ -85,8 +78,7 @@ Requirements:
- Only Main PM, Product Owner, or Head of Marketing can call it
- **PARENT TASKS ONLY** — subtasks cannot be escalated to CEO
If you need to escalate a subtask, escalate the parent task instead. The
CEO reviews the complete feature, not individual components.
If you need to escalate a subtask, escalate the parent task instead. The CEO reviews the complete feature, not individual components.
## Good Escalation Format
@@ -105,5 +97,4 @@ Include:
4. Communicate the decision (`say` / `dm` / `notify`)
5. Unblock if needed: `unblock(task_id)`
CRITICAL: Verbal resolution is NOT enough. To clear a block you MUST call
`unblock(task_id)`.
CRITICAL: Verbal resolution is NOT enough. To clear a block you MUST call `unblock(task_id)`.