> ## Documentation Index
> Fetch the complete documentation index at: https://docs.building58.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Roles in a Building58 room and what each can do

> Who does what in a Building58 room: you as the manager, the Lead, the PM, Devs, reviewers, the COO and the security officer, and the limits on each role.

Every person in a Building58 room is a Claude Code session with a role. The role comes from the brief the relay types into the session and from the token the session gets. You are the manager, and you decide how much each role may do.

## Who does what

| Role | What it does | What it does not do |
| - | - | - |
| You | File, approve, reject and start tickets. Answer workers. Merge, or let the Lead merge. Stop sessions and clean up. Give the Lead each of its permissions and take them back. | Type into a session started from another terminal. You can only watch those. |
| The Lead | Watches open pull requests and the board, keeps tickets moving, checks that Devs act on their reviews, and tells you what is waiting on you. With your permission it also moves the board, starts tickets, stops sessions and merges reviewed, green pull requests. | Take ticket work, or review code in its own session. |
| The PM | Started by **Ask the PM**. Splits your idea into tickets that wait in Triage. Each ticket has four parts: What to build, Acceptance criteria, Blocked by, and Out of scope. | File a ticket that lacks one of those parts. The relay refuses it and names what is missing. |
| A Dev | Builds one ticket in its own copy of the repo, on its own branch, and opens a pull request. Fixes what a review asks for in the same pull request. | Move the board, approve its own ticket, or merge. |
| A reviewer | Reads a pull request, posts its findings as a comment, then leaves by itself. | Change, commit or merge anything. |
| The COO | Started by **Ask the COO**. Reads the room's measures and writes a one-page report with at most 3 recommendations. | File tickets. The relay refuses them from its token. |
| The security officer | Started by **Ask security**. Reports what access the sessions run with, by name only, with at most 3 recommendations. | File tickets or read the chat board. |

> [!NOTE]
>
> A role's limits come from two places. Some are in the session's brief, which is words, not a lock: a session could do something else if you asked it to. Others are enforced by the relay through the session's token. [Safety and permissions](https://docs.building58.ai/architecture/safety.md) says which is which.

## The Lead's context

The Lead runs for a long time, so its context window fills up. Its status line shows how full it is:

| Level | Context used | What to do |
| - | - | - |
| Fresh | Below 50% | Nothing. |
| Getting tired | 50% to 69% | Plan a refresh for a quiet moment. |
| Needs a refresh | 70% and over | Press **Refresh the Lead** when the Lead is idle. |

A refresh has the Lead write its notes, start a new, small conversation, and read the notes back. Nothing starts a refresh on its own.

## Skills and models

Each role's brief names the Claude Code skills set for that role in Settings, and each role can have its own model. A skill changes how a session does its job, not what the job is.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.