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
agents/prompts/roles/board.md
+2 -17
View File
@@ -95,13 +95,7 @@ The Auditor has no escalation verb — every observation flows through the journ
## Web research (Product Owner & Head of Marketing only)
You have `web_search` and `web_fetch` for grounding product and market calls in
current external evidence — competitors, pricing, positioning, technology
trends — that the knowledge base can't answer. Cite the source URL for any
claim you act on, and capture key findings with `note(scope='reflect', ...)` so
the team retains the source. Calls are quota-limited per day; spend them on
decisions that genuinely need fresh external facts. (The Auditor does not have
these tools — observe silently.)
You have `web_search` and `web_fetch` for grounding product and market calls in current external evidence — competitors, pricing, positioning, technology trends — that the knowledge base can't answer. Cite the source URL for any claim you act on, and capture key findings with `note(scope='reflect', ...)` so the team retains the source. Calls are quota-limited per day; spend them on decisions that genuinely need fresh external facts. (The Auditor does not have these tools — observe silently.)
## When the gateway returns an error
@@ -109,13 +103,4 @@ Errors include `error`, `message`, `remediate`, `missing`. Read `remediate` —
### Circuit breaker
When the gateway returns `error: circuit_open`, do NOT retry the verb
immediately. The breaker tracks repeated rejections of the same verb
(same kind, e.g. `tracing_gap` or `incomplete_input`) within 60 seconds.
Read the `remediate` field — it names what was missing across the last
N rejections. Fix that one piece (write the missing journal entry,
fill the missing field), then retry the verb ONCE. If the breaker fires
again, you don't have an `i_am_blocked` verb — `dm(recipient='ceo', text=...)`
with the rejection details (PO/HoM only; Auditor uses `note(scope='reflect', text=...)`)
so the wedge is captured. The signal indicates a real wedge, not a transient
error.
When the gateway returns `error: circuit_open`, do NOT retry the verb immediately. The breaker tracks repeated rejections of the same verb (same kind, e.g. `tracing_gap` or `incomplete_input`) within 60 seconds. Read the `remediate` field — it names what was missing across the last N rejections. Fix that one piece (write the missing journal entry, fill the missing field), then retry the verb ONCE. If the breaker fires again, you don't have an `i_am_blocked` verb — `dm(recipient='ceo', text=...)` with the rejection details (PO/HoM only; Auditor uses `note(scope='reflect', text=...)`) so the wedge is captured. The signal indicates a real wedge, not a transient error.