RiskMandatecustomers ↗ riskmandate.ai first batch, being set up v0.1.1
Home / Docs / The brief / The memo of 20 October

Rendered from docs/brief/memo-2026-10-20-user-onboarding-plan.md, which is the source of truth and the markdown twin of this page. Rendered at site v0.1.1.

The memo of 20 October 2026: the first batch of users, and the next phase of RiskMandate

A voice memo from the lead, received the same day as the brief, after the brief. Archived byte for byte and registered by digest, in the riskmandate.ai way: what was said and what we made of it are two objects, and only one of them is allowed to be wrong.

Received2026-10-20, as an otter.ai transcript uploaded by the lead to the build session, titled "Risk Mandate User Onboarding Plan"
The bytesmemos/2026-10-20-user-onboarding-plan.txt, 1,876 bytes, sha256 0a60b38e069682f98c906a36d21dff8665d54a6048cc4f8bd21dca445892e7df; never edited
Statusread into this site at v0.1.0 (2026-10-20); what it changed is listed below and in BRIEF-CORRECTIONS.md
Reads againstthe brief, the newsroom article of the same day

What it adds to the brief

Read against the brief, the memo makes five things concrete. The transcript is the lead's spoken words; the list is the build session's reading of them, and is the part that can be wrong.

  1. The first users are named. The lead, the co-founder ("Nime" in the transcript is Nimay Parekh, the co-founder and chief executive, as on the about page), and the agents the lead already runs: about ten, probably more, which are the ones that need behaviour policies. The brief said "some of it is us"; the memo says it is us first.
  2. The programme is one people propose to join, because capacity is limited. The brief's mailing list for the next batch is the same mechanism seen from the other side.
  3. What the behaviour policies are. Very explicit ones that work with Claude and with ChatGPT, covering two of the three places a behaviour policy can run: the rows the agent follows, and the rows the hooks hold. The third place is left for later. This is the step S5 on the milestone ladder.
  4. The wired-in agent produces the end behaviour policy. The agent that is already wired in gets the responsibility and the requirement to create the end behaviour policy, which means the workflow has to be implemented with it and the KPIs and objectives mapped out. This is the proposed row programme.agent-policies in the reality file.
  5. The milestone. To get a behaviour policy, and to find behaviour policies that add value to these users; and to focus on the onboarding and the experience, as smooth and effective as it can be, to the point where it adds a lot of value and they understand what the behaviour policy is doing. The brief's "usage moment" and "entry point with least friction", in the lead's own words.

The transcript, verbatim

What follows is the file, unchanged, including the transcription's own spellings.

Dinis Cruz  0:00  
To map out the next phase of the risk mandate, which is we now are ready to create our first batch of users, which I already have, and we're delivering them in, and basically we're going to have sort of a programme where people can propose to join me, right? Because again, we have limited capacity, and we're going to be working with to to get to give them the policies right. And these policies are fundamentally going to be around a set of very explicit policies that work with Cloud and ChatGPT, and they basically are all focused on both the policies for the agent to run, and the and policies for the hooks. Right. So remember that we, when you talk about agent behaviour policies. There's three elements where they can run. What we're going to do is we're going to first work with our users to do two. So what we need now is these users. We now need to implement the workflow with the agent behaviour policies, and so with the with the with the agent that we have wired in. So we need to basically give that agent the responsibility and the requirement to basically create the end policy. So we need to basically map out all the KPIs and all the objectives, and we need to basically, like the milestone here is to get a policy and to find policies that add value to these users, right? So the the first, of course, two main users is going to be me. Actually, the main users are going to be me, Nime, and the pile of agents that I already have. So about 10 agents, or probably more, that I already have, that are going to be the ones that need the policies. So we just need to now really focus on the onboarding, focus on the experience, to make it as smooth and as effective, and to get to the point of it adds a lot of value, and they understand what the policy is doing. So that's our next very exciting milestone.

Transcribed by https://otter.ai