02dc46e782
Add structured documentation covering quickstart, architecture, core concepts, API reference, adapter guides, CLI commands, deployment options, and operator/developer guides. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
40 lines
1.3 KiB
Markdown
40 lines
1.3 KiB
Markdown
---
|
|
title: Org Structure
|
|
summary: Reporting hierarchy and chain of command
|
|
---
|
|
|
|
# Org Structure
|
|
|
|
Paperclip enforces a strict organizational hierarchy. Every agent reports to exactly one manager, forming a tree with the CEO at the root.
|
|
|
|
## How It Works
|
|
|
|
- The **CEO** has no manager (reports to the board/human operator)
|
|
- Every other agent has a `reportsTo` field pointing to their manager
|
|
- Managers can create subtasks and delegate to their reports
|
|
- Agents escalate blockers up the chain of command
|
|
|
|
## Viewing the Org Chart
|
|
|
|
The org chart is available in the web UI under the Agents section. It shows the full reporting tree with agent status indicators.
|
|
|
|
Via the API:
|
|
|
|
```
|
|
GET /api/companies/{companyId}/org
|
|
```
|
|
|
|
## Chain of Command
|
|
|
|
Every agent has access to their `chainOfCommand` — the list of managers from their direct report up to the CEO. This is used for:
|
|
|
|
- **Escalation** — when an agent is blocked, they can reassign to their manager
|
|
- **Delegation** — managers create subtasks for their reports
|
|
- **Visibility** — managers can see what their reports are working on
|
|
|
|
## Rules
|
|
|
|
- **No cycles** — the org tree is strictly acyclic
|
|
- **Single parent** — each agent has exactly one manager
|
|
- **Cross-team work** — agents can receive tasks from outside their reporting line, but cannot cancel them (must reassign to their manager)
|