App Messaging, Overseer and Citizen
When a rule blocks something on your laptop you get no explanation, and the fix could flood you with alerts from every direction.
Every message from head office now has one shape and three sentences, and you decide which kinds reach you and how; the first release carries only the connection receipt.
Documents
With file names, on their own page →What changed
The change that matters most, in plain words. Open any one to see it.
- 1
One picture shows who sends, where a message can land, who receives, and what the person can turn down.
Overseer, ports, citizen · came from Mark Peterson, Mark Parson and othersopen →
- Every message has the same shape and says three things: what happened, why it matters, what to do next. New in this cycle
- You choose how each kind of message reaches you, and the inbox tells you what it held back. New in this cycle
- IT writes a message in three sentences, sees how many machines it reaches, and is warned before it shouts. New in this cycle
- We listed every message anyone had asked for and kept only the ones worth interrupting someone for. 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.
“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.”
market-analyst /calls/1b21a3ce… (local)Use the desktop app itself to drive an OAuth/Slack-style sign-in flow to connect an endpoint to the control plane.
market-analyst /calls/1b21a3ce… (local)c137-D1 The plane holds the record and the operator's view; the native app keeps a local inbox that syncs. In local mode, messages exist on the machine only. — Mark Parson
c137-D2 Messages travel as a resource through the plane source of c131's DataNozzle, fetched or streamed; replies are posted back the same way. — Mark Parson
c137-D3 V1 ships the schema, the inbox store, the OS notification plumbing with per-type controls, the tray count, and the Connect confirmation as the one flowing type. The full type set and the controls are designed here; the plumbing lands with c131 Phase 1. — Mark Parson
c137-D4 Required is the single override: allowed on enforcement notices and censures by default, settable per policy, always counted and visible to the person. — Mark Parson
c137-D7 Overseer and citizen stay internal working words; the product words come from c0. — Mark Parson
One picture shows who sends, where a message can land, who receives, and what the person can turn down.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked for the first message
When qcontrol enforces a policy the person sees a disruption and nothing else; he asked for local feedback with a path to IT. The enforcement notice and Contact IT are that ask, and the problem this cycle cites.
“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
Ruled ports and bones into V1, and the person's control with them
Turned c130 D9 into its own cycle on 2026-11-09, named the two parties overseer and citizen, asked for simplicity and exquisite control over not being bombarded, and confirmed D1–D8 at kick-off.
Set the Connect flow the first message rides on
The app drives an OAuth-style connect to the plane, and once connected no local configuration is possible; the identity confirmation is the receipt of that act and the one message that flows in V1. Which messages flow next is his call at G2.
“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.” internal
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 4
The full record 9 decisions · 6 key-change entries · 1,607 words · 4 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 c137 →