Diagram
To close: Ask Mark what the diagrams were for and where they were used (a deck, a qcontrol doc, c35?). · Write a short CYCLE.md with Why and Outcome, or fold the folder into c35. · Add it to HISTORY.md.
last activity Apr 13 · waiting on Mark's answer
Not recorded: the prompt file is empty. The files suggest a need to explain simply how qcontrol, the tool that sandboxes AI agents, is put together.
Two crowded architecture diagrams of qcontrol were redrawn as two plain ones: three commands talking to an engine, and the four steps a watched call takes. Nothing says where they were used.
Documents
With file names, on their own page →Start here
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
A busy diagram of the qcontrol commands and the engine behind them, redrawn as three boxes and three arrows.
Three commands, one engine
- 2
A dense run-architecture diagram, cut down to the four steps a watched call takes.
The life of one call, in four steps
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 busy diagram of the qcontrol commands and the engine behind them, redrawn as three boxes and three arrows.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
A dense run-architecture diagram, cut down to the four steps a watched call takes.
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 · 4
The full record 0 decisions · 0 key-change entries · 0 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 c34 →