docs/rag/roles/ceo.md

# CEO Role

## Identity

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

## Core Responsibilities

1. Final authority on major decisions
2. Approve major task completions
3. Set strategic direction
4. 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.

### X posts and roadmap items (panel-only, not gateway verbs)

Two more CEO-only approval queues, both plain REST endpoints on the orchestrator (not lifecycle transitions, not agent-callable verbs):

- **X (Twitter) posts** — `GET/POST /api/x/posts{,/{id}/approve,/reject}`. Every held release-announcement or mention-reply draft the X engine originates (`ROBOCO_X_ENGINE_ENABLED`) sits here; approve posts it to X (optionally with an edited body, up to 280 chars), reject cancels it with a reason. Credentials are set separately via `GET/POST /api/x/credentials` (write-only — the API only ever returns `has_credentials`).
- **Roadmap items** — `GET /api/roadmap/cycles`, `POST /api/roadmap/cycles/{task_id}/items/{item_id}/{approve,reject}`. Each weekly roadmap-engine cycle (`ROBOCO_ROADMAP_ENGINE_ENABLED`) the Product Owner authors 3-7 item drafts; approve materializes one as a BACKLOG task (`source=roadmap`), reject records your reason. Approval is per-item, not per-cycle — you can approve some and reject others from the same cycle.

Both are idempotent (re-approving an already-posted/already-materialized item is a no-op) and both are held artifacts — nothing here was ever dispatched to an agent before your decision.

## 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`).
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00			`# CEO Role`

			`## Identity`

			`- Agent: ceo (Renzo - Human)`
			- Role: `ceo`
docs(rag): rewrite the KB docs to the real gateway verb surface 2026-06-05 17:20:36 +02:00			`- Team: board`
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00			`- Reports to: N/A (top of hierarchy)`

			`## Core Responsibilities`

			`1. Final authority on major decisions`
			`2. Approve major task completions`
			`3. Set strategic direction`
			`4. Oversee entire organization`

docs(rag): rewrite the KB docs to the real gateway verb surface 2026-06-05 17:20:36 +02:00			`## How the CEO Acts`

docs: reflow hard-wrapped prose to one line per paragraph 2026-06-16 23:18:55 +02:00			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.
docs(rag): rewrite the KB docs to the real gateway verb surface 2026-06-05 17:20:36 +02:00
			`## What the CEO CAN Do`
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00
			`- View ALL tasks organization-wide`
docs(rag): rewrite the KB docs to the real gateway verb surface 2026-06-05 17:20:36 +02:00			- Approve or reject tasks in `awaiting_ceo_approval`
			`- Cancel tasks (CEO is one of the cancel-authorized roles)`
			`- Set strategic direction`
			`- Read all channels`
A2A wiring up 2026-01-06 00:59:09 +01:00
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00			`## CEO Approval Workflow`

docs: reflow hard-wrapped prose to one line per paragraph 2026-06-16 23:18:55 +02:00			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:
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00
docs(rag): rewrite the KB docs to the real gateway verb surface 2026-06-05 17:20:36 +02:00			- Approve — merges the PR, task → `completed` (lifecycle `ceo_approve`)
			- Request changes — task → `needs_revision` (lifecycle `ceo_reject`)
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00
docs: reflow hard-wrapped prose to one line per paragraph 2026-06-16 23:18:55 +02:00			`Both are panel actions; the agent that escalated simply idles until the CEO decides.`
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00
v0.17.0 — Wave 3: sandbox DB, DB isolation, mobile UI, cloud auth, X account, roadmap engine (#303 ) 2026-07-03 19:24:00 +02:00			`### X posts and roadmap items (panel-only, not gateway verbs)`

			`Two more CEO-only approval queues, both plain REST endpoints on the orchestrator (not lifecycle transitions, not agent-callable verbs):`

			- X (Twitter) posts — `GET/POST /api/x/posts{,/{id}/approve,/reject}`. Every held release-announcement or mention-reply draft the X engine originates (`ROBOCO_X_ENGINE_ENABLED`) sits here; approve posts it to X (optionally with an edited body, up to 280 chars), reject cancels it with a reason. Credentials are set separately via `GET/POST /api/x/credentials` (write-only — the API only ever returns `has_credentials`).
			- Roadmap items — `GET /api/roadmap/cycles`, `POST /api/roadmap/cycles/{task_id}/items/{item_id}/{approve,reject}`. Each weekly roadmap-engine cycle (`ROBOCO_ROADMAP_ENGINE_ENABLED`) the Product Owner authors 3-7 item drafts; approve materializes one as a BACKLOG task (`source=roadmap`), reject records your reason. Approval is per-item, not per-cycle — you can approve some and reject others from the same cycle.

			`Both are idempotent (re-approving an already-posted/already-materialized item is a no-op) and both are held artifacts — nothing here was ever dispatched to an agent before your decision.`

NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00			`## Escalation`

docs(rag): rewrite the KB docs to the real gateway verb surface 2026-06-05 17:20:36 +02:00			`The CEO is the final escalation target:`

NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00			```
			`Developer → Cell PM → Main PM → Product Owner → CEO`
			```

docs: reflow hard-wrapped prose to one line per paragraph 2026-06-16 23:18:55 +02:00			Only `main_pm`, `product_owner`, and `head_marketing` can escalate a task to the CEO (via `escalate_to_ceo`).
A2A wiring up 2026-01-06 00:59:09 +01:00
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00			`## Communication`

docs(rag): rewrite the KB docs to the real gateway verb surface 2026-06-05 17:20:36 +02:00			`The CEO has read access to all channels, including:`
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00			`- #board-private`
docs(rag): rewrite the KB docs to the real gateway verb surface 2026-06-05 17:20:36 +02:00			`- #announcements`
NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see 2026-01-03 05:07:45 +01:00			`- All cell and cross-cell channels`
docs(rag): rewrite the KB docs to the real gateway verb surface 2026-06-05 17:20:36 +02:00
docs: reflow hard-wrapped prose to one line per paragraph 2026-06-16 23:18:55 +02:00			The CEO communicates and decides through the panel/UI rather than the agent content tools (`say` / `dm` / `notify`).