Fractal Risk Registers: One Per Accepting Role, In Their Language
Where the seven stakeholder altitudes and the acceptance mechanism come from.
team/humans/dinis_cruz/briefs/07/17/registers-mandate-and-intervals/v0.33.49__arch-brief__sg-send-fractal-risk-registers-one-per-accepting-role-domain-language-relevance-fade.md
Commitb561fa6b14 · carried 23 August 2026
LicenceApache-2.0 (repository) · CC BY 4.0 stated in the file
Bytes18,446 · 2,674 words · SHA-256 2f50e0c5dc9c80c5
Dated17 July 2026
Why it is here
The Agentic Browser Isolation vault writes the same risk seven times, once per stakeholder, and this site's decisions page runs that vault's acceptance rules over the book's own open questions. Both come from here. The argument is that wherever there is a stakeholder accepting a risk, that entity needs a register; that registers are fractal, using the same grammar at every altitude; and that only the role's own register is stored, with the views above derived by relevance rather than curated.
What it says
- Wherever there is a stakeholder accepting a risk, that entity needs a register.
- Registers are fractal: the same grammar and tooling at every altitude.
- A person's register is all the risks that bubble up to them, derived rather than curated.
- The role's own register is stored; the registers above are derived by a relevance fade.
- The register belongs to the role, and the role connects to a person, which is what makes succession work.
Worth re-reading for. The relevance fade is the mechanism the browser-isolation vault implements as seven stakeholder altitudes. Read them together.
Where this document lands on the site
The document is the peak. Below it hang the concepts measured in its text and the places on this site that rest on it — and the two are different kinds of link, drawn differently: a measured edge is dashed and carries its count, an authored edge is solid. The method is stated in full on the hub.