Native App (program)
Next: Phase 2, the shape (shape.md), fed by the primer and the spike; then the pitch for Tyler's requirements session and c0's naming walk.
The dashboard lived inside the sensor and made it heavier than the sensor's promise; the team decided to split them.
A program with a researched primer, a measured spike, and seven cycles each with a plan, so the native app and the control plane can be built in parallel without losing the thread.
Documents
With file names, on their own page →What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
There are now three pieces: a watcher and a small app on each laptop, and a server they connect to.
The three apps and the plane · came from Tyler Flint and Mark Parsonopen →
- 2
The work is cut into eight smaller jobs, and each knows what it waits for.
Eight cycles and four gates · came from Mark Parsonopen →
- We read up on the new toolkit so builders and designers start from the same facts. In words
- A first version runs and is small; the numbers are real, not quoted. In words
- The open questions were answered in one sitting, and two new cycles came out of it. 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.
“we move the entire. UI that you have been working on out of Qcontrol... the control plane is something you connect to, Qcontrol is the thing you deploy.”
market-analyst /calls/1b21a3ce… (local)“if they have the config file, they can do anything. They can add their own syncs. They can add their own capabilities... Once you connect to the control plane, no local config is possible.”
market-analyst /calls/1b21a3ce… (local)c130-D2 GPUI Kit, the styled gpui-component layer. "Native" means a native binary with the OS window, menus, tray and dialogs; GPUI draws its own controls on the GPU. — Tyler Flint
c130-D4 The native app lives in a new sibling repo, a Cargo workspace, created the same day at ../qnative under a provisional name; Tyler decides at G2 whether it moves into qcontrol's workspace. — Mark Parson
c130-D6 Three data sources behind one switch: synthetic, local and plane, from V1. The plane takes a base URL and a standardised credential. Mechanic access becomes its own cycle, c136; the names go to c0. — Mark Parson
There are now three pieces: a watcher and a small app on each laptop, and a server they connect to.
“we're not holding up... rolling things out for, like, a production ready Saas... anyone kinda starting with on prem while we... make Saas bulletproof.”
market-analyst /calls/1b21a3ce… (local)“Even the MCP server skills. Things like that. It might be good to just list them up.”
market-analyst /calls/1b21a3ce… (local)c130-D1 c130 holds the primer and the shape; c131 is the build. One program cycle, seven children, each agent with a clean context. — Mark Parson
The work is cut into eight smaller jobs, and each knows what it waits for.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked that the person at the keyboard be told
Local feedback when qcontrol enforces a policy, with a path to IT: the seed of c133 and c137, and the promoted problem enforcement-without-local-context.
“If the local queue control can give end user feedback about. So, like, when policies are enforced, so it's just not, like, such a complete whiplash in vacuum of information, that. I think that would be actually really useful.” first-hand
Took the UI out of the sensor and chose the framework
Proposed decoupling the control-plane UI from qcontrol, a native desktop app on GPUI Kit with the tray as the first release, and the control plane as SaaS and self-hosted on Pulse with a new data model.
“bundling in the web project increases the memory usage... for for to just to run a web stuff, like, to run web stuff, and it's already kind of, like, weird.” internal
Kept the first release honest
SaaS readiness does not block adoption; start with what we know well, the inventory; surface MCP servers and skills in the desktop app.
Ran it as a program
Split the prompt into cycles so each agent keeps a clean context, ruled the ten decisions in one walk, and asked that every structure be drawn for the team.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 2
The full record 10 decisions · 3 key-change entries · 2,300 words · 2 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 c130 →