Boundary Morphing
Groups like team or region were fixed into the data. People want to ask one map different questions: by team, by data center, by how critical it is.
Each thing now carries tags, and a menu regroups the map by any tag. Things glide to their new group while the ground tiles fade and redraw. Things missing a tag land in "unknown".
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
Pick a tag from a menu and the map re-sorts itself into new groups.
Regroup the map by any tag · came from Mark Parson
- 2
Keeping the data flat and grouping by tags on the fly turned out more flexible than a fixed hierarchy.
Flat data with tags beats a fixed tree · came from Mark Parson
- Shapes glide to their new spot and the tiles fade and redraw, so you can follow what moved. New in this cycle
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.
Pick a tag from a menu and the map re-sorts itself into new groups.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Keeping the data flat and grouping by tags on the fly turned out more flexible than a fixed hierarchy.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Built tag-based regrouping with animated rugs
The record names no one. The experiment code and this record reached the qmap repo in commits authored by Mark Parson.
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 · 3 key-change entries · 837 words · 9 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 c5 →