[{"data":1,"prerenderedAt":34},["ShallowReactive",2],{"cycle-doc-qmap-c22-initial-prompt.md":3},{"cycle":4,"project":7,"path":10,"title":11,"toc":12,"ast":13},{"id":5,"title":6},"c22","runtime-session-map",{"id":8,"label":9},"qmap","Qmap","initial-prompt.md","c22. Runtime Session Map",[],{"type":14,"children":15},"root",[16,24,29],{"type":17,"tag":18,"props":19,"children":20},"element","p",{},[21],{"type":22,"value":23},"text","Build a qmap experiment that visualizes a single qcontrol runtime session by entity type — mapping what one wrapped process touched during execution: files, child processes, external hosts, and the root process itself. Use qmap's grouping system to organize actors into entity-type rugs so the structural shape of the runtime session is immediately legible.",{"type":17,"tag":18,"props":25,"children":26},{},[27],{"type":22,"value":28},"Start with a reduced session fixture, not raw event replay. Reuse the successful interaction pattern from c21 (Entity Type, File Access, Actor Type, Flat), but tune it for runtime telemetry rather than AI-session semantics. Stress-test the layout with at least three session shapes: file-heavy, network-heavy, and mixed runtime activity.",{"type":17,"tag":18,"props":30,"children":31},{},[32],{"type":22,"value":33},"Create a plan, call out any wrapper\u002Fcomponent refinements this suggests, and suggest any qmap defaults that should change for file-dense session maps.",1794599431302]