pki.sgit.ai / documents / grant-tree

The End-To-End Flow Is The August Worked Example With An Agent Installation As The Twin

TypeArchitecture brief Versionv0.33.61 Date20 August 2026 AuthorDinis Cruz (project lead) and collaborators LicenceCC BY 4.0 Sourceraw markdown · view on GitHub

Summary

The flow from what an agent can reach to somebody accepting a risk does not need designing — it is the 2 August worked example with an agent installation as the twin, and excess authority plays the role a regulatory provision played there, which is what makes the finding computed rather than asserted. Four corrections follow. A grant is a tree of subgrants, so blast radius is a path through it; and the load-bearing part is the label on each node, because a control bounds a grant only when it is enforced by something the grant does not include — giving boundary, setting and expectation, and placing most current containment in the middle tier. The two scenarios are the two populations and neither dominates: locally the containment is available and unused, hosted it may be excellent and is unverifiable. Grants and mandates are artefacts, so they get signed rather than keyed. And counting acceptances is the one metric that inverts, because it is maximised by making risks easy to accept.

Key concepts

Key ideas

On this site

Became document 12 of the registry MVP pack, and gives the grant the structure the excess-authority finding had been assuming since C1.

Read the document

📄 Original document · v0.33.61 · 20 August 2026 · rendered from the raw markdown (the source of truth)