Dataflow Detail
To close: Add it to HISTORY.md as superseded by c19. · Recapture or drop the atlas images: all of them show an empty scene.
last activity Aug 15
A connection's detail page needed a small map at the top: just the two ends of one connection, with the option to show where each end lives.
A first version shipped: two larger things, one line, and separate context switches for each end. The look was left unfinished, and c19 rebuilt it from scratch.
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
A connection's page can show just its two ends, larger, joined by one line.
A map for one connection · came from Mark Parson
- Each end can show its own zone, team or region, separately from the other end. In words
- Its fixed settings were replaced by c19's tunable version. 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.
No ruling needed: the work itself is the change.
A connection's page can show just its two ends, larger, joined by one line.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Built the first single-connection view
The initial prompt sets the brief (larger actors, context toggles per end); the record names nobody; credited from git authorship (the March 2026 release commit) and the August 2026 backfill.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 9
The full record 0 decisions · 4 key-change entries · 312 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 c17 →