mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00

Files

T

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

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.

2026-06-16 23:18:55 +02:00

1.7 KiB

Raw Blame History

CEO Role

Identity

Agent: ceo (Renzo - Human)
Role: ceo
Team: board
Reports to: N/A (top of hierarchy)

Core Responsibilities

Final authority on major decisions
Approve major task completions
Set strategic direction
Oversee entire organization

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.

What the CEO CAN Do

View ALL tasks organization-wide
Approve or reject tasks in awaiting_ceo_approval
Cancel tasks (CEO is one of the cancel-authorized roles)
Set strategic direction
Read all channels

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:

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.

Escalation

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).

Communication

The CEO has read access to all channels, including:

#board-private
#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).

1.7 KiB Raw Blame History