Dataflow Arrows
To close: Add it to qmap's HISTORY.md (it is in neither CYCLES.md nor HISTORY.md). · Recapture the strategy frames: six of the nine show only the two end points.
last activity Aug 15
A dashed line only hints at which way data flows, and the hint gets lost when lines cross or the camera turns. Arrows make direction obvious.
Four arrow styles were compared and two decorations joined the library: cone arrows, spread along the line or sliding with a trail, and a travelling glow. Both are optional and tunable.
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
Cone arrows now ride the curve, so direction reads at a glance.
Arrows on the line · came from Mark Parson
- A band of light can sweep along a line to show it is active. In words
- Arrows and the glow are switched on per map and tuned from the control panel. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
qmap-c20-D1 Arrows and pulse are optional decorations attached to the existing line, not new kinds of line. — Mark Parson
Cone arrows now ride the curve, so direction reads at a glance.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Compared arrow styles and kept two
The record names nobody; credited from git authorship (the April 2026 batch commit for c18–c22).
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 10
The full record 0 decisions · 5 key-change entries · 352 words · 10 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c20 →