---
name: agent-roster
type: agent
description: >-
  Index of the os.Claude Layer 3 fleet — the functional agents and the vertical
  operators, their labels, roles, and profile files. Read to see which agent or
  operator owns what, then open the matching profile (agent-relay, agent-forge,
  operator-bara, and so on) for the full mission and remit.
---

# Agent roster

The Layer 3 fleet that runs os.Claude. Two classes live here (see `core-operating-model`, Layer 3): **functional agents**, each owning one capability across every vertical, and **operators**, each owning one venture end-to-end and commanding the functional fleet. Each is a named, accountable role; open its profile for the full mission, remit, and composition. Functional agents carry two name forms — a **written** form for prose and an all-caps **branded** form that is also the Linear `agent` label value. Operators carry a lowercase `operator-<venture>` label value, not a branded one. Only the named functional fleet is branded; `human`, the `operator-*` values, and other-model values stay lowercase.

## Functional agents

| Agent | Label | Role | Profile |
| -- | -- | -- | -- |
| **Relay** | `R3-LAY` | Delivery management — routes, unblocks, holds the merge gate | `agent-relay` |
| **Forge** | `F0-RGE` | Implementation — builds and opens a PR, never merges | `agent-forge` |
| **Prism** | `PR-1SM` | Review — independent quality verdict; clears the merge | `agent-prism` |
| **Scout** | `SC-0UT` | Pipeline — captures people and opportunities, kept clean | `agent-scout` |
| **Pulse** | `PUL-5E` | Ops — system health and self-improvement; propose-only | `agent-pulse` |
| **Atlas** *(future)* | `ATL-4S` | Planning — goals, prioritisation, cycle commitment; cross-operator portfolio arbitration | `agent-atlas` |
| **Sonar** *(commercial)* | `SO-N4R` | Design strategy, discovery & service design — upstream of Pixel and Reach | `agent-sonar` |
| **Pixel** *(commercial)* | `P1-XEL` | Brand and design system | `agent-pixel` |
| **Reach** *(commercial)* | `R3-ACH` | Marketing and go-to-market | `agent-reach` |

The Linear `agent` label group enumerates these same values; `convention-linear` (*Labels*) carries that enumeration and must agree with this table — reconcile both when the fleet changes.

## Operators

Vertical roles, one per venture, that own an outcome and command the functional fleet within a granted mandate. The slot can be filled by the Owner, another human, or an AI — the same contract. The tier above is the **Owner** (Aled), who sets each mandate and gates the hard anchors (a strategic pivot, budget allocation).

| Operator | Label | Vertical | Profile |
| -- | -- | -- | -- |
| **Operator, BARA** | `operator-bara` | BARA — relaunch, weekly loop | `operator-bara` |

Further verticals (A1, careerOS, app.fitness, os.Claude) roll out once the operator role is proven on BARA. Each operator's label value is added to the Linear `agent` group alongside the functional values; `convention-linear` (*Labels*) carries the enumeration and must agree with this table.

## Owner-serving agents

A third class: an agent that serves the **Owner** (Aled) directly, rather than a capability across every vertical (functional) or a venture end-to-end (operator). It sits downstream of Atlas — Atlas commits the cycle, the Owner-serving agent turns the Owner's slice of it into booked time.

| Agent | Label | Role | Profile |
| -- | -- | -- | -- |
| **Aide** *(MVP)* | `A1-DE` | Personal chief-of-staff — sweeps the committed cycle for items needing Aled, sizes them (15m/30m/1h/2h; >2h → Relay to split), and books calendar holds in his `work.Hold` window (propose-and-confirm) | `agent-aide` |

Aide reads Linear (the upcoming cycle only, read-only) and writes only Aled's calendar; her capacity signal goes to Atlas and oversized items route to Relay. She is a personal / Owner-serving role, distinct from both the delivery fleet and the vertical operators — position her label in the `agent` group accordingly. The MVP composes `skill-attention-sweep`, `skill-time-management` (the `skill-operator-time` rename, APP-431) and `skill-time-block`; the `agent-aide` profile is authored. Prerequisites from the planning-and-time layer (epic APP-428): the `work.Hold` recurring event (APP-426) and cycles enabled (APP-432) are **done**, so the MVP is buildable and testable against a hand-committed cycle now; the **automated** Atlas→Aide handoff additionally wants the initiative KPI baseline (APP-433) so Atlas's cycle-planning (APP-429) can run. The Linear `agent` group already carries `A1-DE` as a live value — this entry documents what routes to it, and `convention-linear` (*Labels*) must agree.

**System rule:** anything blocked is assigned to the operator and marked Urgent — whichever agent hits the blocker moves it to Blocked, assigns the operator, states the cause, and never jams its own leg. Anything beyond an operator's mandate — a strategic pivot, a budget-envelope breach, a goal-set change — is escalated to the Owner with a recommendation, never actioned unilaterally.