Roles
The three long-lived roles you talk to, what a role's screen shows, the supervised CLI behind the Advanced tab, and calling a role on demand.
The fleet has three long-lived roles you talk to:
| role | what it does |
|---|---|
| Advisor | thinks with you, designs, measures, writes orders |
| Master | runs a train: dispatches legs, reviews, lands wagons |
| Scribe | writes into the record: commits with your authorship, documents, relays |
About the pictures on this page. They are rendered from the built console over a demonstration data set, not from a live fleet — a screenshot of somebody's real record would publish their work. What the pictures are evidence of is the layout, the chips and the acts; every number in them is sample data.
A role runs as a session of a CLI on a machine of the fleet — one of the supported backends
(claude-code, codex, qwen-code).
Every session is a row; every turn is in the transcript.
A role's screen
Three columns.
Left — the role's sessions: the live one first, then closed ones newest first, with cost and
turns. New session starts a fresh one, and search filters. The column collapses to a rail
with « or [, and remembers its state.
Middle and right — the head with the role's facts as chips (workspace live-read, tools live, transcript file, context use, rotation advice), the Rotate act, and two tabs: Conversation and Advanced.
Conversation
Above it a single wire line (Advanced): live state, turns, model, delivery, since when.
- Your turns show delivery state — delivered, sending…, not delivered.
- The role's turns show its thinking rail, the tools it ran and for how long, its answer, and a cost line with the transcript.
- A relay card appears when a role wants to hand something on: the text, with Forward → Scribe (an act into the record) or Copy.
- A rotation bar appears when the fleet advises rotating the role: why, with Handoff and call the next session and Show the signals.
Composer. Write; the button sends; Enter is a newline. You do not choose a model here —
the model is a fact of the session, set in the configuration. The exits of a conversation are
always the same and are listed under the composer in Advanced: forward to a role, copy, and the
transcript file.
What the console does not do here
It does not run anything on your behalf, and it does not retry silently. A turn that did not reach the role says so. A gap in the stream is marked as a gap. A session closed by the role or by the machine is marked closed.
Advanced — the role's CLI, supervised
The Advanced tab shows the same session as a terminal: the role's CLI, live, on the machine you picked from the fleet. You pick the machine and Start, or Detach, which leaves the process running.
The chip supervised · slash commands off · safe mode is the supervision profile: the CLI
is started with the flags that keep it inside the session, and there is one profile per supported
CLI.
⛔ A role can be started only on a machine of the fleet's registry, and the CLI's location
comes from that machine's admission record — never from a guess about PATH. A CLI with no
supervision profile is refused by name.
Scribe — relays land in the record
The Scribe's conversation is where relays arrive: a record-order block forwarded by the Advisor,
marked as forwarded, role to role, with the owner act and its batch. The Scribe books it — commit
authored by the owner, no AI attribution — and answers with the commit. The Scribe writes only
into the record; pushing is your hand.
Call a role
Three cards:
- Reviewer — reads a round, writes findings, never lands.
- Harvester — files measured defects at no model cost, repairs mechanisms.
- Custom… — name · handoff document · CLI · machine.
Calling a role reads the workspace's handoff document for that role and starts its first session
on a machine of the fleet. It is an act into the record.
