Studio review · experiment E02 · v1 · 29 October 2026, 06:25 UTC

E02, the blast radius: keep the data, redo the picture

Reviewed by deck@the-ultimate-insider. The piece: the blast radius, v1, driven (54 s) and its explainer, made by ruv.sgit in run r5-e02-blast-radius from the researcher's grant rows (abp-examples.json). Looked at over HTTP (it loads its data, so it does not run from a file) at 1280 by 720: end state, 12 s and 30 s, light theme, reduced motion; no console errors.

Verdict: again (v2), keeping everything that is true

The slide is honest to the letter. Every row comes from the file at load; the arithmetic is on screen (grant 16, minus the 4 granted mandate items, is an excess of 12); the shortfall (send.endpoint.allowed, asked, not granted) is drawn; each row carries its barrier kind; and the footer says it is a published draft, derived, with no row measured and no score given. That is exactly the researcher's four cautions, kept. What it is not yet is a picture a room reads in five seconds. It is a table beside a diagram, and the two do not touch.

What works

• The start: E01's shaded reach breaking into sixteen dots. The hand-off from part one's first piece works.
• The headline: the blast radius is everything its grant reaches.
• The core of four inside the circle, the excess outside it: the shape of the argument is right.
• The line "12 of 12 have no control, only nothing, a rule in prose, or a switch its own account can flip". That is part two's whole case, and it lands here.

Notes for v2

1. Label the dots, not a list. Nobody can tell which red dot is which row. Put the words on the dots in the drawing and drop the separate list, or keep the list and draw a line from each row to its dot as it is named. The picture has to carry it on its own.
2. Plain words first, ids second. authenticate-as.credential.tenant means nothing at the back of a room. Lead with what it is (log in as you to your cloud; delete files anywhere on the machine; send anything to anywhere on the internet), and keep the id small beneath, for the explainer and the curious. The words must come from the file's own descriptions, not be invented.
3. Group the excess. Twelve dots evenly round a ring say "twelve things". Grouped (files and the disk, credentials, the network and the world, records and history, the schedule) they say what is at risk. Group by the capability's own noun, which the ids already carry.
4. Distance should mean something. Unstated (2) and refused (10) sit on the same ring. Put them at two distances, as the list already separates them.
5. Barrier kinds on the dots. The four glyphs are in the list only. On the dots, the one expectation and two settings stand out from the nine nothings, and set up E10.

Next

v2 is the next request for ruv.sgit, ahead of E03 and B01 v2: the blast radius is the centre of part one, and a v2 with the notes above is one slot. The data needs nothing more.