# The team

*customers.riskmandate.ai · who does what, as files · written at v0.1.0 (2026-10-20) · in the shape of the sgit.ai team section and the riskmandate.ai team page · CC BY 4.0*

Three roles fill every seat at this stage, held by one person and one agent. Each role is one file with the rules it enforces and the mistake behind each rule, so that a new agent can read this page and one role and begin. The board of work is [board.md](board.md), the work as files with a status line each, and [needs.md](../docs/ops/needs.md), the asks back to the person. Neither lives in a vault yet; if the board outgrows a file, it moves to a vault of its own and this page says where.

| Role | Held by | Decides |
|---|---|---|
| [Project lead](roles/project-lead.md) | Dinis Cruz | What ships next, what the brief means where it is ambiguous, who is in the batch and under what handle, the credit, everything that needs a human account (DNS, Pages, the meter, the list) |
| [Build agent](roles/build-agent.md) | A Claude Code session, one at a time | Everything else, within the rules its role file lists, recording each departure from the brief in the corrections file |
| [Customer follow-up](roles/customer-follow-up.md) | The lead, for the first batch; an agent drafts | The daily contact with each customer, the three questions, and what is recorded on the customer page |

The agents that make riskmandate.ai have behaviour policies of their own on [its team page](https://riskmandate.ai/team/); this site's build agent is a Claude Code session of the same kind and will get one as part of the record *the-agents* in the batch. Other teams review the work and the review is published with the reply; the first review this site expects is the sgit.ai site team's, against its repository rules.