Reading diagrams / Topic 42 of 42
Visible state: what changed between two runs
The rule
A data app computes outputs from inputs a reader can change. The visible state view compares two runs of one compiled app: a kept run, and the current run after an input changed. These runs were recorded: in the event budget, Guests went from 40 to 50 and nothing else changed. The line above the graph names the selected output and its two values: “Amount left over · kept 200 → current 400 · difference +200”.
The graph draws one card per binding: an input, a program binding, or the selected output, each with a reference such as B1. A card reads kept → current, then the difference, as in “1,000 → 1,250 (+250)”. One value with “same” means both runs agree. Changed cards are drawn heavier, so the path the change took reads first. When the graph is wider than the page, it opens on the selected output; scroll it sideways to reach the inputs.
An arrow runs from a dependency to its reader: from each binding a formula refers to, into the binding it defines. So the arrows into a card are what its formula reads. They are static: the formula refers to that binding whether or not the run's branch used it. A card no arrow runs into reads no other binding: it is an input, or its formula names none, as with seawater_density in the hull app. Press a card's name to read its formula, with each run's values put in.
Card names come from the data app. A configured label, such as Ticket income, is the app author's; other cards show the program's binding name, such as guest_cost. Equal labels or values do not make two cards one binding. The reading guide under the graph is agent-authored and marked so.
Two runs show what happened in those two runs. A card that stayed the same does not mean the input cannot change it, and the graph does not say what a third run would give.
- A card's values confirm what each recorded run computed; “same” means the two runs agree.
- An arrow into a card confirms its formula reads that binding; no arrow rules it out.
- What another run would give, or which values a run's branch used: the graph can't tell.
The event budget: ticket income and costs for an event, run with 40 guests and then 50.
Hull scaling: a boat hull’s displacement, run with a 10 m hull and then a 12.5 m one.
How to read this: what each mark in these pictures means
Loading the worked examples and practice.