Runtime Session Map
qcontrol, Qpoint's runtime monitor, records every file, process and connection a program makes. We wanted to see one program's session as a map, not a log.
Recorded sessions now draw cleanly with parts qmap already had, through a runtime view with its own defaults and a small bridge that feeds it live. Very file-heavy sessions still need trimming.
Documents
With file names, on their own page →Start here
Pages
- /experiments/c22.runtime-session-map/ (local dev)
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
A program's session draws as the program plus rugs for files, child processes and hosts.
Readable, from small to overloaded · came from Mark Parson
- 2
Runtime maps got their own ready-made view instead of borrowing the AI-session one.
A runtime view of its own · came from Mark Parson
- A small bridge hands the map summarised sessions, so it can follow a running program. In words
- Very file-heavy sessions will need summarising before they reach the map. 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-c22-D2 The root process groups as "Root Process" but keeps its own shape, so the rugs match runtime ideas. — Mark Parson
A program's session draws as the program plus rugs for files, child processes and hosts.
From the record: no recorded conversation behind this one.
qmap-c22-D1 Give runtime maps a dedicated view: they need different defaults and a clearer entry point than the AI-session view. — Mark Parson
Runtime maps got their own ready-made view instead of borrowing the AI-session one.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Mapped a running program's session
The record names nobody; credited from git authorship (the April 2026 batch commit for c18–c22).
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 · 939 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 c22 →