Home / Articles / A trusted framework for agentic finance / Versions / v1.1.0
A trusted framework for agentic finance: what changed in v1.1.0
From v1.0.0 (2026-10-19, d6a9cfbf8) to v1.1.0 (2026-10-19, 831cb1578), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 53 unchanged. About 0 words added and 7 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
18 unchanged paragraphs, under In short {#in-short}, What the FCA said {#speech}, Four elements we have been writing about {#four}
Reading the speech, I recognised almost every point. Not because anyone copied anything,anything: butwe becauseare theworking problem forceson the same answersproblem, on anyone who looks atand it closely.leads to similar answers.
1 unchanged paragraph
• Execution is how each rule is kept. In governs, enforces, attests I described three levels: in the prompt, which is a hope; in hooks, which are deterministic but sit on the agent's own machine; or by a third-party system that does the blocking, which is the level we recommend. The test, from the ABP: "A control bounds a grant only if it is enforced by something the grant does not include." Policy as code needs a policy first adds theone questionmore most frameworks miss:question: for every rule that is code, who can change that code.
1 unchanged paragraph
• Agent identity is the one we have written least about, and the speech is right to putputs it first. In the ABP it is implicit: a policy is for one agent in one deployment. The attestation layer in governs, enforces, attests makes it explicit: what was assured, at which policy version, signed so a third party can check it without taking the operator's word.
33 unchanged paragraphs, under A worked example: a payments agent {#example}, Adopt it, or write your own as a graph {#graphs}, What this does not claim {#limits}…