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/architecture/company-layer.md
+8 -27
View File
@@ -1,9 +1,6 @@
# Company Layer (Goals, Pitches, Strategy)
The **company layer** sits above day-to-day delivery: the CEO's charter, the
pitch pipeline, and a background strategy watcher. The charter is always
available (empty until set); the research, provisioning, and strategy-engine
pieces are **opt-in and default-off** — the org runs fine without any of them.
The **company layer** sits above day-to-day delivery: the CEO's charter, the pitch pipeline, and a background strategy watcher. The charter is always available (empty until set); the research, provisioning, and strategy-engine pieces are **opt-in and default-off** — the org runs fine without any of them.
## The Charter (Company Goals)
@@ -16,14 +13,12 @@ A single, CEO-owned charter is the company's north star. It has four parts:
| `constraints` | Hard limits the company must respect |
| `operating_policy` | Operating rules (e.g. a monthly budget cap) |
The charter is a **singleton**, and it is injected — compactly — into **every
agent's briefing**, so all work is goal-aware without anyone fetching it.
The charter is a **singleton**, and it is injected — compactly — into **every agent's briefing**, so all work is goal-aware without anyone fetching it.
- `GET /api/company-goals` — read (any agent)
- `PUT /api/company-goals` — write (CEO only)
It is empty until the CEO sets it; an empty charter simply contributes nothing
to briefings.
It is empty until the CEO sets it; an empty charter simply contributes nothing to briefings.
## Pitches
@@ -35,30 +30,17 @@ A **pitch** is a proposal for new product work. Its lifecycle is small:
| `provisioned` | Approved — turned into a product / project(s) |
| `rejected` | Declined |
When a pitch is approved and **provisioning is enabled**
(`ROBOCO_PROVISIONING_ENABLED` plus a GitHub token and org), it can auto-create
the product and its repositories (recorded in `provisioned_product_id` /
`provisioned_project_ids`). With provisioning off, approval just records the
decision.
When a pitch is approved and **provisioning is enabled** (`ROBOCO_PROVISIONING_ENABLED` plus a GitHub token and org), it can auto-create the product and its repositories (recorded in `provisioned_product_id` / `provisioned_project_ids`). With provisioning off, approval just records the decision.
## Strategy Engine
The Strategy Engine is a **notify-only** background watcher
(`ROBOCO_STRATEGY_ENGINE_ENABLED`, default off). Each cycle it `assess()`es the
company against its standing goals and emits `StrategyObservation`s — each a
`kind`, a `summary`, and a `detail` — for example `idle` (capacity sitting
unused) or `stranded_blocked` (work stuck in `blocked`). It only **observes and
surfaces**; it never acts on its own.
The Strategy Engine is a **notify-only** background watcher (`ROBOCO_STRATEGY_ENGINE_ENABLED`, default off). Each cycle it `assess()`es the company against its standing goals and emits `StrategyObservation`s — each a `kind`, a `summary`, and a `detail` — for example `idle` (capacity sitting unused) or `stranded_blocked` (work stuck in `blocked`). It only **observes and surfaces**; it never acts on its own.
Those observations are the "needs your attention" signals shown on the
Dashboard, served by `GET /api/cockpit/signals`.
Those observations are the "needs your attention" signals shown on the Dashboard, served by `GET /api/cockpit/signals`.
## The Secretary
The CEO's chief-of-staff reads this layer (`read_company_state` returns the
charter, task counts, pending pitches, and any directives awaiting
confirmation) and acts on it via gated directives. See
`docs/rag/roles/secretary.md`.
The CEO's chief-of-staff reads this layer (`read_company_state` returns the charter, task counts, pending pitches, and any directives awaiting confirmation) and acts on it via gated directives. See `docs/rag/roles/secretary.md`.
## Feature Toggles
@@ -68,5 +50,4 @@ confirmation) and acts on it via gated directives. See
| `ROBOCO_STRATEGY_ENGINE_ENABLED` | off | The strategy watcher loop |
| `ROBOCO_PROVISIONING_ENABLED` | off | Pitch → auto-provisioned repos |
All are additive: with every toggle off, the company layer is just the charter
plus the pitch record.
All are additive: with every toggle off, the company layer is just the charter plus the pitch record.