Visualise a blast area

A blast map is a decision surface written down. Drawing it is not decoration: a set of surfaces, states and edges that reads as a table of facts reads as a shape the moment it is laid out, and the shape is what a reviewer actually argues with.

The risk of drawing it is that a diagram looks finished. Whatever the map could not see disappears when it becomes a picture, because absence has no glyph. An inferred edge and a compiler-resolved one arrive at the reader as the same arrow. A node reached by three paths picks up three colours and gets reconciled in someone's head, differently each time.

So this skill renders under a contract: blind spots occupy space on the page, changed and affected are visually distinct, every edge carries the confidence it was born with, and the layout is fixed so that two renders of the same repository can be put side by side.

It draws. It does not decide — blast-area produced the envelope and this skill does not get a vote in what went into it.

What a rendered map must not lose