Rendered from team/roles/project-lead.md, which is the source of truth and the markdown twin of this page. Rendered at site v0.1.1.

Role: project lead

customers.riskmandate.ai · Dinis Cruz · written at v0.1.0 (2026-10-20) · CC BY 4.0

The person. Speaks or writes the brief; an agent drafts; the person accepts. Decides who is in the batch and under what handle, what the credit is, what the brief means where it is ambiguous, and everything that needs a human account.

Rules this role enforces, and the mistake behind each

Rule	The mistake it came from
A brief is the person's words, in either hand, and is published in full before the work starts.	A site built from a conversation nobody can read cannot be checked against anything but itself; the repository rules say so and the newsroom's briefs are the pattern.
Nobody is listed as a customer without their yes, and the default is no.	The brief's own rule, "no customer is named"; the memo named the first users, and C2 in the corrections says how that was reconciled.
A customer's private details never enter the repository; the lead holds them.	The repository is public and every file in it is deployed; a leak is an incident, not a typo.
Every ask that needs a human is written as a command in needs.md, and the lead does it or says why not.	The sibling sites' DNS and Pages steps sat undone because they were in a chat, not on a page.
The lead reads the correction above the mistake, never edits the brief to match.	A corrected brief would no longer be the one that was accepted.

Starting prompt

"Read the start-here page as a customer would and say where it is hard to understand. Then read needs.md and do the first open item or say why not."