RiskMandateOur first customers, and the site we follow them from.
Agent Behaviour Policies are ready for the next level, and the next level is execution. Execution starts with customers: a small first batch, each with credit to spend, objectives and milestones written with them, and a follow-up every day if that is what helps. This site is where that happens: what to do first, where each customer is, and what we are learning.
Status, from docs/reality.md: shipped v0.1.0 A start-here page: what a customer does first, in order, with the links to do it · shipped v0.1.0 A page per customer with the fields the brief asks to track, generated from data/customers.json, with no contact details · proposed Credit per customer, metered and billed on this site, with a top-up link · proposed A form on this site for the next batch, encrypted in the browser to the riskmandate.ai agent's lane
Where the batch is, counted from the data.
Every number below is read from data/customers.json on every release; nothing is typed. The one worked example is not counted.
In short: the brief, in seven lines.
- Agent Behaviour Policies are ready for the next level. The workflow, the mapping to what regulators ask for, and the understanding of how it fits together are in place.
- What is left is execution, and execution starts with customers. Consultants who will sell this and already use some of it, people the lead works with, and us.
- Call them customers, not beta users. Beta describes the product; customer names the relationship. Each starts with credit on a site that meters and bills. The programme →
- Follow each one closely. Daily if needed, with objectives and milestones of their own, and three questions each time. The follow-up →
- A dedicated site with a start-here page. Instructions, progress and usage in one place. You are on it. Start here →
- Discover the usage moment. The simplest useful behaviour policy, the easiest entry, a fair price. What we want to discover →
- A mailing list for the next batch. Everyone who asks, kept for when we are ready. The next batch →
The first batch is us, then the people we already work with.
The voice memo that followed the brief the same day named the first users: the two founders and the agents the lead already runs, about ten of them, each needing a behaviour policy of its own. The first work is two of the three places a behaviour policy can run: the rows the agent follows, and the rows the harness holds as hooks, for Claude and for ChatGPT. The milestone is a behaviour policy that adds value to a particular person, who understands what it is doing. The memo →
For one agent in one deployment: everything it can reach, what you authorised, the gap, and what stands in the way. It describes and does not judge, so it carries no score. What an ABP is ↗
From in-with-credit to the usage moment, so progress reads in one table while the objectives stay each customer's own. The steps →
Give it for free until there is enough value that they want to pay. The meter is the newsroom's today; wiring it here is proposed. Credit, and the meter →
The brief in full, where it was wrong, what exists, and a page per customer with no contact details on it. The documents →
What this site does not claim.
- The programme is new. The site exists; the prices are starting points to test; the metering is the newsroom's and not yet this site's.
- No customer is named who did not agree to be. The first group is people we already work with. Contact details are never in this repository.
- What exists is listed, and only that. docs/reality.md is generated on every release; if it is not there, it does not exist.
- Everything is open. The brief, the data shapes and this site are CC BY 4.0; the code is Apache-2.0. This site is published by the people building the thing it describes: the participant disclosure.