← Cycles
qflow · c12activestarted Jul 29Auto draft — not yet reviewed

qcontrol Live View

Park it for nowThe first version works end to end, but nothing has moved since 2026-07-29, the code is uncommitted, and qcontrol's dashboard has been rebuilt since, so the feed may need checking.

Next: Commit the experiment folder so the work is not lost · Check the live feed against today's qdash before more tuning · Do the by-eye tuning listed under "Pick up here", then write the Outcome

last activity Jul 29

Why we did this

qcontrol, Qpoint's agent monitor, streams every AI agent event, but its live view was a table. qflow could show the same stream as moving traffic.

What happened

A working first version: agents as pixel figures firing pulses at event types, live or from a sample feed, with filters and a play bar to scrub back. Visual tuning remains.

Early → finalEach agent is a pixel figure, each kind of event a dot, and every event sends a pulse between them.

Start here

Pages

  • /experiments/c12.qcontrol-live-view/ (local dev)
At a glance
4
changes
0
conversations
3
decisions
0
outside helpers

What changed

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

  1. 1

    Each agent is a pixel figure, each kind of event a dot, and every event sends a pulse between them.

    Agents and what they do · came from Mark Parson

  2. 2

    A bar along the bottom grows as events arrive; drag back in time, replay, or jump to live.

    A play bar that keeps growing · came from Mark Parson

Also in this cycle
  • Narrow the view to chosen agents or kinds of event; the choice is kept in the page link. New in this cycle
  • Limits on pulses, history and idle agents keep it smooth when events pour in. 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

qflow-c12-D1 One dot per agent session, labelled with the agent and its process id; one dot per event type. — Mark Parson

So now

Each agent is a pixel figure, each kind of event a dot, and every event sends a pulse between them.

Someone said

From the record: no recorded conversation behind this one.

We decided

No ruling needed: the work itself is the change.

So now

A bar along the bottom grows as events arrive; drag back in time, replay, or jump to live.

Thanks to

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

MP
Mark Parson
Qpoint team

Set the brief: a live agent view with a growing play bar and a jump-to-live button

The cycle's initial prompt asks for a translation layer over qcontrol's live events and a YouTube-style play bar with jump to live. It is unsigned; Mark Parson committed the cycle record, so the credit is matched, not cited.

All images

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

The pairs

Agents and what they doEarly → final
→
A play bar that keeps growingNew in this cycle
Filters you can link toNew in this cycle

Everything captured · 10

The full record 3 decisions · 14 key-change entries · 1,002 words · 10 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 c12 →

Qpoint Brand Style Guide