View Contexts
Different pages need different maps. A page about a policy violation needs a calm, focused view of the offending connection, not the whole interactive map.
The first view preset works: a policy-violation view that draws the offending flows in red as soon as it loads, highlights the things involved and fades the rest.
Documents
With file names, on their own page →Start here
Threads
Pages
- /experiments/c16.view-contexts/ (local dev)
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
A violation page can show the offending connections in red, with everything else faded.
A policy-violation view · came from Mark Parson
- 2
A connection can be marked healthy, warning or violation, and the map picks its colour and weight.
Lines carry a status · came from Mark Parson
- Tuning controls that draw themselves from a list of settings were tried, then set aside. 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-c16-D1 The page says what a connection represents (its status); qmap decides how to draw it. — Mark Parson
A violation page can show the offending connections in red, with everything else faded.
From the record: no recorded conversation behind this one.
qmap-c16-D1 The page says what a connection represents (its status); qmap decides how to draw it. — Mark Parson
A connection can be marked healthy, warning or violation, and the map picks its colour and weight.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Built the first view preset
The record names nobody; credited from git authorship (the March 2026 release commit that carried this work).
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 3
The full record 0 decisions · 5 key-change entries · 399 words · 3 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 c16 →