RiskMandateThe lead's agents (about ten, as one customer)
Agents the lead already runs, which need behaviour policies of their own. Status: starting, started; before the first behaviour policy.
What the brief asks us to track
- Started
- 2026-10-20
- The agent
- About ten agents the lead already runs: the site publishers across the sgit.ai network, the newsroom writer, the inbox agent, the Claude Code sessions. Each needs a behaviour policy of its own; two already have one on riskmandate.ai/team/.
- First behaviour policy
- not yet
- Milestone steps done
- 1 of 7
- Credit
- none (the agents spend nothing; the measure for them is a behaviour policy each)
- Follow-ups recorded
- 1
Objectives agreed with them
- A behaviour policy for every agent the lead runs, in the same grammar as the two on riskmandate.ai/team/.
- The agent that is wired in takes on the responsibility of producing the end behaviour policy for each of the others.
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 | in-progress |
| 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 | Counted: two of about ten agents have a behaviour policy (the publisher and the design studio, on riskmandate.ai/team/). | No list of the ten yet, with the shape each is nearest to. | List the agents, one line each, with the published shape it is nearest to. |
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.