Trying to help map the cell structure of a reactive runtime. WIP this is overwhelming but it looks pretty. The clumps are modules. The concentrated rainbow arc is pointing at the stdlib. It does communicate the intense collaberation inside a module and the sparse connections between modules though.

If you care to spend time further expanding on this, I need more hand-holding. There are 4 shapes - circles, squares, triangles, plus signs. There are 3 kinds of lines - solid, dashed, fat. There are several colours - orange, blue, green, red. And there's black text. My knee-jerk reaction is that each of these has a separate meaning, which I don't grok yet.

I am so glad you said that! The main point of this visualization is to provoke the reader into noticing a knowledge gap of the programming model. Those cells are clickable, so without that interaction part you can't close that gap autonomously. The interactive notebook is now published here https://observablehq.com/@tomlarkworthy/cell-map Still, it would take a fair amount of detective work to solve it still. The programming model is written here. "Cells can be views" and "Cells can be mutables" are relevant to the symbols. The square ones are imports, you can see the cell colors change when bridging via a square. The circles are simple dataflow cells which is probably the first thing you would implement if designing a dataflow language, they are just functions (actually they can also be generators, probably that should be reflected in the symbology too as they act quite different).