01
Explain what a node and an arrow stand for
An arrow can mean a permitted message direction, a reference or a dependency. A node can represent a point in a puzzle, a note or something else defined by the application. The example here uses abstract nodes and directed connections only. It makes no claim that these stand in for the detailed mechanisms suggested by the name. A SynapticMatter worksheet should identify those meanings near the diagram. This lets the visual language remain expressive while giving readers a firm basis for interpreting the specific calculation or interaction being shown.
02
Make the timing convention part of the explanation
A diagram does not tell the reader whether updates happen simultaneously or one node at a time. Those choices can change the result. In the worksheet, every next state is calculated from the complete previous state, so a newly activated node cannot forward a signal during the same step. The timing convention is as important as the edge list. Keeping it visible helps a reader distinguish a mistake from a different model. A later exercise may change the convention, but it should preserve the earlier version so the consequences can be compared directly.
03
Prefer a readable network over decorative complexity
The compound can be written SynapticMatter with both initials capitalised to make the two words visible. Supporting diagrams should label nodes and show arrow direction clearly, with text descriptions that work without colour. A small, legible network can communicate more than a dense field of glowing lines whose meaning is unspecified. The identity can draw interest from the relationship between a simple rule and its result. That approach gives visitors a concrete way to engage with the theme while leaving artistic choices separate from the model’s defined behaviour.