Look and Feel
Next: Pick a tool treatment, add flows for the other five scenarios, and swap the grey balls for pawns as they get drawn.
The map's data pipeline works, but what it draws doesn't yet read clearly: what belongs inside what, what matters most, and what things are called.
Not finished yet: one example story now reads as nested floors, with tools still being compared four ways. Nothing is committed except design's handoff note.
Documents
With file names, on their own page →What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
The scene is organized into AI Services, Internet and the Endpoint, with the account and project as floors inside the Endpoint.
Floors that say where things live · came from Mark Parson
- 2
A comparison page shows the same story with tools as labels on lines, a tool belt, an expanding stack and a Tools box.
Four ways to show tools · came from Mark Parson
- Everything is a grey ball with its name on hover, except the helper: a grey character in a red hat. In words
- Rug colors, borders and label type can be changed live from the controls panel, and the page opens in a flat, top-down view. 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-c29-D1 Group the scene into zones, with the endpoint holding the person, the provider account (harness, tools) and the repo (files, skills). — Mark Parson
qmap-c29-D2 Give AI services their own top-level rug, outside Internet, even though they are on the internet. — Mark Parson
The scene is organized into AI Services, Internet and the Endpoint, with the account and project as floors inside the Endpoint.
From the record: no recorded conversation behind this one.
qmap-c29-D4 Don't draw tools as 3D objects with as much space as a harness; put MCP tools on their server's rug. — Mark Parson
A comparison page shows the same story with tools as labels on lines, a tool belt, an expanding stack and a Tools box.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Tuned the map by hand
Set the rug hierarchy, picked the helper character, and called for tools to take less space than a helper.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 4 decisions · 16 key-change entries · 2,657 words · 36 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 c29 →