RiskMandateThe lead (Dinis Cruz, co-founder)
One of the people building RiskMandate, using the programme on their own agents first. Status: starting, started; before the first behaviour policy.
What the brief asks us to track
- Started
- 2026-10-20
- The agent
- Claude Code, on a laptop and on the web, with the connectors the sessions hold; nearest published shape: Claude Code on the web.
- First behaviour policy
- not yet
- Milestone steps done
- 2 of 7
- Credit
- £0 used of £5 granted; not topped up (credit is a starting point; the meter is the newsroom's, not yet this site's)
- Follow-ups recorded
- 1
Objectives agreed with them
- Prove the workflow on the agents we run before asking anyone else to.
- Find the simplest behaviour policy that is useful on a Claude Code session.
The steps
The shared ladder is on the milestones page; the state of each step for this customer is here.
| Step | Milestone | State |
|---|---|---|
| S0 | In, with credit | done 2026-10-20 |
| S1 | One agent named | done 2026-10-20 |
| S2 | The grant, measured or documented | open |
| S3 | The mandate, in the customer's words | open |
| S4 | The delta, and the first finding | open |
| S5 | The hooks half: what the harness holds | open |
| S6 | The usage moment | open |
The follow-up log
Each follow-up asks three things: what they did, what got in the way, and what is next. Newest first. The record here is the summary; anything private stays with the lead.
| Date | What they did | What got in the way | What is next |
|---|---|---|---|
| 2026-10-20 | Set the programme up: the brief, the memo, this site. | The meter and the credit are not wired to this site yet. | Measure the grant of one Claude Code session with MAP-A-GRANT.md. |
What is not on this page. No contact details, no private notes, nothing the customer did not agree to show. The source is data/customers.json; a change to it is a release, so the history of this page is the history of the repository.