Home / Articles / An analyst's blueprint for RiskMandate / Versions / v1.3.0
An analyst's blueprint for RiskMandate: what changed in v1.3.0
From v1.2.0 (2026-10-21, d9d4562f2) to v1.3.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 5 changed in place, 76 unchanged. About 0 words added and 191 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot wb-landscape.webp | images/ | Who does what, by their own description: Drata, Endor Labs, Socket, Bedrock Data, Sondera, AWS AgentCore Policy, the agent gateways, the testers and the incident responders,description, against the analyst's four layers,layers: discover, evaluate, enforce and prove; and RiskMandate as the policy each layer is configured from.prove. | comparison
33 unchanged paragraphs, under In short {#in-short}, The note {#note}, Where we agree {#agree}…
!shot wb-map.webp | images/ | TheirThe architecture,analyst's four layers, each mapped to our pieces: discoverdiscover, isevaluate, the grant, measured; evaluate is the mandateenforce and the delta; enforce is hooks in the agent's harness and rules compiled to Cedar for gateways; prove is a receipt per decision, a replayable day, and a holder for every gap. And the roadmap adds risk acceptance and insurance.prove. | comparison
7 unchanged paragraphs, under The controls fitted to the context {#fit}
!shot wb-fit.webp | images/ | The controls fitted to the context:context, from a line in the prompt where little is at stake; a hook in the harness where the agent acts alone; a gateway or proxy where it reaches systems that matter;to monitoring and a person where money, customers or regulators are involved. The same behaviour policy feeds all four.person. | concept
10 unchanged paragraphs, under Not another box in the middle {#inline}, Where to start {#start}
!shot wb-start.webp | images/ | Where to start: the analyst's first build list, and our order. Tool-call interception through the hooks and the customer's own gateways; behavioural policies, which we have; cross-step detection in hooks that keep state; allow, block and approve generated from the policy; audit and replay, which we have; and partners for skill and MCP risk scoring. | comparison
4 unchanged paragraphs, under More players is good news {#players}, Who plays open source {#open}
!shot wb-open.webp | images/ | WhoWhich playsof the vendors open source,their code, and what they open: agentgateway, Docker's MCP gateway and Sondera's harness are open; AWS opens its Cedar language, Socket and Endor Labs their agent tooling; no public code was found for Drata's, Bedrock Data's or Ping's agent products. RiskMandate opens the vocabulary, the policies, the engine and the apps.opens. | comparison
20 unchanged paragraphs, under The more mature, the less we are needed? {#maturity}, What we need now {#customers}, What this does not claim {#limits}…