Home / Articles / Ten questions, one graph / Versions / v1.2.0
Ten questions, one graph: what changed in v1.2.0
From v1.1.0 (2026-10-19, 3b0e7fd8c) to v1.2.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 5 changed in place, 40 unchanged. About 0 words added and 176 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 tt-graph-q9.webp | images/ | Question 9 on the Thistlewood twin's graph: who are the humans and agents withhas the largest blast radius?radius, Everythingwith the answer doeseverything not use hasused faded. What is left is the plot: three identity admins and five deploy agents, the secrets store and staff sign-on they can reach, the risks those open, customer personal data exposed among them, and the path up to the board. | screenshot
16 unchanged paragraphs, under In short {#in-short}, Ten questions a tool should answer {#questions}, Every question is a graph question {#graph}
!shot tt-map.webp | images/ | Ten questions, one graph.graph: Eacheach of Phil Venables' questions against the parts of the company it has to traverse: risks and holders, controls and cost, processes, systems, suppliers, channels and sales, humans and agents, incidents and causes, acceptances and events. No question is answered by one part alone; all of them are answered by the whole.traverse. | concept
4 unchanged paragraphs, under Half of this already exists: risk acceptance {#acceptance}
!shot view-role-risk-map.webp | ../demos/vaults/risk-graph-explorer/images/ | The role risk map in the Risk Graph Explorer vault, from that earlier work.work, Everyshowing risk is assigned to somebody, and every risk reaches the board:what each role shows what it holds and what passes through it on the way up.holds. | screenshot
5 unchanged paragraphs, under The twin {#twin}
!shot tt-graph-q7.webp | images/ | Question 7 on the graph: the minimum viable processes,processes and the most severe plausible scenario they cannot withstand. Ransomware in the warehouse system, run by one supplier with no fallback, stops pick, pack and ship. | screenshot
2 unchanged paragraphs, under How our workflow fits {#workflow}
!shot tt-loop.webp | images/ | From a question to a decision the board can see.see: Ask;ask, query the graph; see the plot, with what is not relevant faded;graph, decide, accept for an interval, fund or fix, with one holder; record the decision in a vaultvault, with its evidence and hash; back-test the model against what happened, and recalibrate. Underneath each step, the work it comes from: fractal semantic graphs, the whodunit view, risk acceptance, sgit vaults, measured evidence.back-test. | concept
11 unchanged paragraphs, under What this does not claim {#limits}, Where this comes from {#sources}