# Reading a walk

> A walk lays every meaningful syntax node of a file on a hexagonal grid in the order the parser met them, so a file is a path the eye can follow, going down when…

Page: Anatomy · Reading
Canonical: https://banes-lab.com/anatomy#reading-a-walk

A walk lays every meaningful syntax node of a file on a hexagonal grid in the order the parser met them, so a file is a path the eye can follow, going down when the code nests, up when it returns and sideways when it continues. The states are shown in [E1·a the legend](https://banes-lab.com/anatomy#reading-a-walk-panel-a), which marks what declares, what calls, what writes, what reads, what branches and what merely holds structure.

### States, arrows and cells

The arrows mark the direction every few steps, and a flagged cell carries the severity of the finding that flagged it. Every cell is a reference into the data the walk ships beside it, so the vector stays a shape and the text lives in a file the page reads by reference, the same way a code panel is cited from the prose.

A walk pans by dragging and zooms by scrolling, and selecting a cell shows its file and line, its syntax kind and its text. A folder's walk is its files in order, and a file's walk is that file alone, so the tree can be read at either scale. A walk shows syntax and never semantics. What a call resolves to comes from the call graph, which the definitions beside each file show.

E1·a the legend

```text
declare: declare
call: call
write: write
read: read
control: control
structure: structure
```