AI Ecosystem
Qpoint's AI monitoring data (sessions, agents, models, API keys, tools, files) was shown only as tables. Could qflow's moving pictures make it readable for security teams?
Seven views in one page: an agent session in three forms, an org-wide map, a map of tools, and two inventory views. qmap later built a 3D companion.
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
A single agent session becomes a graph of everything it touched, which you can replay turn by turn.
One agent session, drawn · came from Mark Parson
- Machines are linked to the models they call, each line coloured by the API key it used. New in this cycle
- Tools are grouped by the server that offers them, sized by how often they are called and coloured by error rate. New in this cycle
- Pick any user, machine, key or model from a list and see what it connects to. 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.
A single agent session becomes a graph of everything it touched, which you can replay turn by turn.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Drew the AI monitoring data as seven qflow views
Mark Parson committed the experiment and the backfilled record on 2026-08-15; the record names nobody, so git authorship is the source.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 11
The full record 0 decisions · 8 key-change entries · 508 words · 11 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 c11 →