Qnative (provisional)

The native app's **Safety & Security → Findings · Settings** in place of c4's Messages section: this machine's findings, in the person's words, on the same record the company's plane keeps (one finding, append-only events, three writers). c4's notification plumbing, tray, quiet hours and Focus stay and announce findings.

Small, ad-hoc changes to the native app and its component library (QGUIkit, `crates/qguikit`), and to the web layer (`q-nuxt-layer`) when an item reaches it.

The Config page under This machine, and the guide's config tools. An agent reads, checks and proposes the person's `config.yaml`; only the person applies it.

the guide walk's report (`cycles/notes/2026-11-13-guide-agent-walk.md`): what an evaluator's agent driving the guide MCP server needs, in the report's order.

design c133's remediation trainings taken in the native app, launched from the inbox's training assignments.

design c140's code rulings, in Mark's order (D14):

The native app's left rail replicates the web app's: section headers as small uppercase labels, entries as plain text with no icons, the active entry marked the way the web app marks it, a gap between sections. Nothing else in the window changes.

Two toggles in the open info panel, settable while it is open: **Help Mode** (on / off) and **Dev Mode** (on / off). Dev Mode is developer mode's own switch, the one the tray menu carries, in a second seat. Help Mode is the guide layer staying on as the person moves. Opening the panel switches nothing on.

The Status page, the app's first page and the tray's long form: is qcontrol on, what is it reading, what has it found. Built from design c132's Phase 4 brief and mock (the worked example of the loop for native screens) as the loop's push: the page on our layer, a story per state, the state read from the source and the data and never from a flag in the page, captured per world into both atlases, the budget read with strobe.

The V1 slice of the message channel between the control plane and the person at this machine (design c137, Phase 3): the bones as types, the inbox store, the four ports as far as the endpoint owns them (inbox, tray, OS notification; the web app is c134's), the person's controls over delivery, and the one message that flows in V1, the identity confirmation on Connect. The enforcement notice is drawn from the fixture and flows only in synthetic worlds until qcontrol sends it.

The app's developer mode, and the Events page above it. Live (qdash's live viewer, replicated on the sensor's current event schema and improved), Monitor (Kamal's monitor TUI, replicated), Sensor (the data switch as a working control), Config (three modes), Guide (how to hook a live sensor). Developer mode is an extension behind one Cargo feature, so a build can carry none of it; where it is allowed, the person can still turn it off. Events, the curated layer of meaning over the same stream, is an ordinary page.

c131 Phase 2. The whole qdash Inventory section in this app: seven listings, nine detail pages and the landing, in the Qpoint skin, on the data the web pages show, cut to one machine. We build our components in Rust (`crates/layer`, with the web layer's names) on top of the kit, and record per component how close it came and what it cost. Stretch: the Tour guide, with Info View and the `qpoint-guide` MCP driving the app. Extra stretch: the table with an expand row at full fidelity.

c131 Phase 0: a hello app on GPUI Kit 0.9.1 that answers the platform questions before anything is promised. One window with a sidebar and a data table bound to a JSON inventory; a tray icon beside GPUI's event loop; the `DataNozzle` with its three transports (`synthetic`, `local`, `plane`) behind one process-wide switch; the footprint measured with strobe; Windows and Linux builds attempted in CI; the findings written back to design's primer.

The names, before the code: the native desktop app (and whether "Qdash" moves to it), the control plane (publicly "Qplane" since 2025 Q3), the third data source and the thing a base URL points at, the two roles (working words: overseer and citizen), and this repository. Grounded in the customer's own words from the market-analyst corpus, the brand's writing rules and the neighbours' precedents; decided in a shared team session with an agent.