# A proposed roadmap for RiskMandate: what changed in v1.4.0, sgit.ai > The changes to the article "A proposed roadmap for RiskMandate" in v1.4.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [A proposed roadmap for RiskMandate](../../the-riskmandate-roadmap.md) / [Versions](../the-riskmandate-roadmap.md) / v1.4.0 # A proposed roadmap for RiskMandate: what changed in v1.4.0 From v1.3.0 (2026-10-21, `631e216b9`) to v1.4.0 (2026-10-21, `bffac8774`), paragraph by paragraph. 1 paragraph added, 0 removed, 9 changed in place, 34 unchanged. About 68 words added and 2 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [← v1.3.0](v1.3.0.md) · [all versions](../the-riskmandate-roadmap.md) # TheARiskMandateproposedroadmap:roadmap for RiskMandate: policies, understand, risk acceptance, contain, manage and insure, a spectrum of trust we would walk with each customer Summary: This is thea proposed strategy for RiskMandate as a company, and the path we willwould walk with each customer. It is still being discussed between RiskMandate's founders, so read it as a proposal, not a decision. The question behind it is how we start engaging with a customer, how we earn their trust, and how we become a player: running our code and our vaults, and being there with them. So think of the roadmap as a spectrum of trust, where each stage answers the next question a customer asks once the last one is answered. Policies first, because we can create them today and they are a microcosm of what we do: the grant, the gap, the hooks, a first picture. Then understand: help us get a grip, what is our exposure, where are our agents and what can they reach. Then risk acceptance: which of these risks do we carry, and who decides. Then contain: make the blast radius smaller. Then manage: run the agents as a fleet. And then insure: by then the evidence an insurer needs exists, and insurance is the end game that gives the whole path its arc, so we want to start talking to insurers now. Acceleration is not a stage; it is what every stage gives the business. At every stage there are other companies that should be the big players, and where they do not move fast enough, there is an opportunity for us. We are in the first stage, with our first customers. !shot rr-roadmap.webp | images/ | The proposed RiskMandate roadmap as a spectrum of trust: six stages, policies, understand, risk acceptance, contain, manage and insure, each answering the customer's next question. Acceleration runs through all of them. We are in the first stage. | concept 1 unchanged paragraph, under In short {#in-short} • **This is RiskMandate'sastrategy,proposedandstrategytheforpathRiskMandate.** weStillwalkbeingwithdiscussed; each customer.** Each stage earns more trust. 8 unchanged paragraphs, under A spectrum of trust {#strategy} What weIaream describing here is thea proposed strategy for RiskMandate as a company, and the path we are going towould walk with each customer. It is a proposal: my business partner and I have talked about it, and it is still being discussed, so none of it is decided yet. The question behind it is simple to ask and harder to answer: how do we start engaging with a customer? How do we earn their trust? How do we become a player, running our code and our vaults, and being there with them? So the way I propose to think about the roadmap is as a spectrum of trust. Each stage answers a different question the customer has, and each one is only asked once the one before it has been answered. The further along we are with a customer, the deeper the relationship, and the more we are helping them in the way they work. The stages are a sequence of events, not always a straight line: with some customers two will overlap, and with others one will come early. But the order is the one we can operate in. 10 unchanged paragraphs, under The six stages {#roadmap}, Accelerate, all the way through {#accelerate}, Insurance is the end game {#insurance} Insurance is what gives the whole path its arc. Every stage before it produces evidence: the policies, the exposure, the decisions, the containment, the managed fleet. Insurance is where that evidence is worth the most, to the company and to the people who would cover it. That is whywhy, in this proposal, insurers are part of the play from the start, and why we want to start talking to them now, with this roadmap in front of them: it shows them how a company gets from its first agent policy to agents they can cover. 1 unchanged paragraph, under The players at every stage {#players} Each stage has other companies that should be the big players in it: in discovering agents, in risk management, in enforcement, in fleet management, and in insurance. Many of them we willwould work with. Where they do not move fast enough, there is a business opportunity for us to get into that space, because we will already be there with the customer. 5 unchanged paragraphs, under Where we are: the policies {#now}, A side note: the policy and its home {#home} One operational note, which does not change the proposed strategy. The Agent Behaviour Policy started inside RiskMandate, and its stewardship is moving to the Open Security Summit, as [its first hosted project](../../agent-behaviour-policies-move-to-the-open-security-summit.md), so that it is governed by more people than us. RiskMandate is still the one operating it with customers. 2 unchanged paragraphs, under What this does not claim {#limits} • **It is a proposal.** Still being discussed between RiskMandate's founders, not the agreed strategy. 7 unchanged paragraphs, under Where this comes from {#sources} [← v1.3.0](v1.3.0.md) · [all versions](../the-riskmandate-roadmap.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/the-riskmandate-roadmap/v1.4.0.html)*