← Cycles
design · c36activestarted Apr 16Auto draft — not yet reviewed

qcontrol Integration

Looks done — ready to closeIts plan was carried out in qmap c22 and its open question went to c37, which closed 2026-08-15; it only lacks a record.

To close: Write a CYCLE.md (Why, Outcome) from the four rounds, pointing at qmap c22 and c37. · Add it to HISTORY.md.

last activity Apr 15

Why we did this

qcontrol watches what programs and AI agents do on a machine. We wanted to know whether that stream could feed our map and traffic pictures.

What happened

Four rounds of research found the way in, qcontrol's event stream, and planned a map of one agent run. It was built as a new qmap cycle. One early mistake was caught and corrected.

New in this cycleThe plan was built in qmap as a map of one run: the agent at the root, with the programs it started, files it touched and sites it called.

Start here

At a glance
3
changes
0
conversations
0
decisions
0
outside helpers

What changed

The two changes that matter most, in plain words. Open any one to see it.

  1. 1

    The plan was built in qmap as a map of one run: the agent at the root, with the programs it started, files it touched and sites it called.

    Where it led: a map of one agent run

  2. 2

    The research was saved in four rounds: findings, a correction, a spec for turning events into a map, and a build plan.

    Four rounds, each kept · came from Mark Parson

Also in this cycle
  • The build moved to qmap as its own cycle, and a question about missing file events became the next design cycle, c37. 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.

Someone said

From the record: no recorded conversation behind this one.

We decided

No ruling needed: the work itself is the change.

So now

The plan was built in qmap as a map of one run: the agent at the root, with the programs it started, files it touched and sites it called.

Someone said

From the record: no recorded conversation behind this one.

We decided

No ruling needed: the work itself is the change.

So now

The research was saved in four rounds: findings, a correction, a spec for turning events into a map, and a build plan.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Asked what qcontrol could show us

His prompt asked what qcontrol is, whether its data streams can be tapped, and how qmap or qflow could visualize what it sees, with each research run saved as its own version.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

Where it led: a map of one agent runNew in this cycle

Everything captured · 2

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 c36 →

Qpoint Brand Style Guide