Home / Articles / What can your agent reach? RiskMandate and the Agent Behaviour Policy, explained for the person who has to decide / Versions / v1.4.0
What can your agent reach? RiskMandate and the Agent Behaviour Policy, explained for the person who has to decide: what changed in v1.4.0
From v1.3.0 (2026-10-18, a94d326ad) to v1.4.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 55 unchanged. About 0 words added and 115 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 ga-gap.webp | images/ | One agent, three sets. The grant is everythingsets: the agent can actually reach through its credentials and connectors;grant, the mandate is whatand the organisationdelta, authorisedwith ita tobarrier do;on the delta is the difference, the authority nobody accepted. Eacheach capability in the grant carries a barrier: nothing in the way, a rule in prose, a setting the agent's own account can change, or a boundary enforced above it. Only the last bounds anything.grant. | concept
36 unchanged paragraphs, under In short {#in-short}, The pages are hard to read {#pages}, What it is, in one paragraph {#what}…
!shot ga-doors.webp | images/ | Five ways into the room, each a question someone already has to answer:room: a contract, where legal and procurement ask what the vendor's agent will do with the data; a security questionnaire, where a customer asks which agents touch their data; an insurance renewal, where the question is whether AI is excluded from cover; the board's risk appetite, where the question is who can pull the plug;board and twenty minutes, where anyone running an assistant asks what it can actually do.minutes. | concept
17 unchanged paragraphs, under What I would like to hear back {#back}, What this does not claim {#limits}, Where this comes from {#sources}