qcontrol File Event Debug
The new map of an agent run showed network activity live, but runs that only touched files never appeared. We needed to know where those events were lost.
Found it: qcontrol wasn't sending file events out at all, so our map code was fine. The map is now described honestly as a network map, with test data for the rest.
Documents
With file names, on their own page →Start here
Documents
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
The missing file events are lost inside qcontrol, before our bridge or map ever sees them.
The events stop at qcontrol
- 2
The runtime map is described as a network and session map; made-up test runs cover the file-heavy cases.
The map promises only what it can show
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.
The missing file events are lost inside qcontrol, before our bridge or map ever sees them.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
The runtime map is described as a network and session map; made-up test runs cover the file-heavy cases.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 2
The full record 0 decisions · 0 key-change entries · 362 words · 0 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 c37 →