← Sketches · the native app program
The naming map
c02026-11-10Six things to name, from the native app to the SaaS address, against the mental models a customer already holds.
Source: ../qnative/cycles/c0.call-my-name/brief.md (2026-11-09): the things to name, the pieces, the criteria, the candidates and the proposed picks; c130 plan.md D4, D6 and Answer 2; c137 D7; the corpus counts in market-analyst's all-calls.json; www.qpoint.io/products/qplane.
◇deploy qcontrol
The sensor: the thing you deploy (the team's word). Named and shipped; 79 mentions on www.
▣open the app
The native app on the endpoint: the one thing the employee meets. To be named, wherever it shows: the tray tooltip, the window title, the installer, a Jamf admin's list.
◇connect to the plane
The control plane. Qplane is already public on www.qpoint.io (2025 Q3, framed as compliance evidence); the frame widens, the name can hold.
Collisions to avoid
“agent”: the product governs AI agents, and www already calls qtap the agent in places · a second “control”: qcontrol exists · “dash”: dashboards, which the brand disavows · “overseer” and “citizen”: never in a UI.
| Thing to name × mental model | Qpoint's q-family | The customer's MDM / EDR map | The governance job | The neighbours' precedents |
|---|---|---|---|---|
| The native appthe tray tooltip, the window title, the installer, a Jamf admin's list | Qlocal (local ↔ plane; a coined modifier) · Qdash, moved (the c130 prompt and an existing crate, but “dash” says dashboard) · Qdesk, Qstation, Qhere (invented nouns) | “Qpoint on this Mac”, Jamf's descriptive model: zero coining, says the scope; no name for a crate, a bundle id or a tray tooltip | What Qpoint found on this machine and how it is doing; never a dashboard, never “the agent” (doubly loaded: customers run agents everywhere) | Qpoint, the app: Tailscale and 1Password give the client the product's own name; Jamf's Self Service is the plain alternative. Proposed: Qpoint to the employee, qlocal as the crate and binary word |
| The control planewww, the web app's title, “connect to …”, the Docker image | Qplane, the incumbent: the team's word and a public product page since 2025 Q3; pairs with local. Proposed: keep it, and widen the page's frame with c134 | Qpoint Console: what Jamf Pro and Falcon console admins expect; proposed as the common noun only, “the Qplane console”, so the MDM map attaches without a second name | The thing you connect to. “Control plane” in full once per doc, then Qplane; the public frame (backend compliance evidence) widens to endpoints and AI governance | Jamf Pro, the Falcon console, Kolide admin, Tailscale's admin console: the operator side gets “console” or “Pro”. Qhub and Qpoint HQ considered; neither needed while an incumbent exists |
| The third data source--data, --plane-url, the footer, config keys | plane: --data plane, --plane-url https://hq.acme.example, footer “data: plane · hq.acme.example”. Proposed. Fallback if Qplane were dropped: hub, --hub-url | “Point the app at a plane” once Qplane is the name; in the UI “your Qplane”; “plane instance” only in operator docs | The caution: in networking the data plane is the sensor's side and the control plane the controller's; the slip is easy (“their running data plane”) | The nozzle names each source by what it is to the app: synthetic (made up) · local (this machine) · plane (a running Qplane). The neighbours name consoles, not sources |
| The two rolesthe schema's sender and receiver, the settings, the docs | operator / you: the brand already says “operators”, and the UI speaks to the reader (“Your operator asked you to…”). Proposed for the web app and the docs | IT / you: a CISO advisor's “a path to contact IT”; plain, but the overseer may be security, not IT | HQ / you: the c130 prompt; human and memorable. Proposed as the default sender label, a plane-set string, so a customer writes “Security” or “IT” and we only choose the default | admin / user: the industry default; precise and cold, and “user” is the word the brand avoids for people. Overseer and citizen stay internal (c137 D7) |
| The repo and its cratesthe directory, the Cargo workspace, the bundle id, the binary, CI | The crate word of the chosen app name: qlocal, qdash or qpoint-app; bundle id io.qpoint.<word>; binary <word>. Renamed once, at this cycle's Outcome | The bundle id and the installer are what a Jamf admin deploys; crates.io and GitHub availability checked before the word is final | The crates inside keep plain names: app, nozzle, types, fixtures, stories, messages. The display name lives in one constant, so deciding late is cheap and deciding twice is not | tailscaled, the Falcon sensor, the Kolide agent: the binary word is plain and lower-case; ours must not be “agent” |
| The SaaS addressthe address bar, SSO redirect URIs, bookmarks, the Connect flow's default plane | plane.qpoint.io is on the table if the team wants the hostname to teach the name | app.qpoint.io stays: customers bookmark it and SSO redirect URIs point at it; a self-hosted plane has its own hostname anyway (hq.acme.example). Proposed | Addresses are not names. A new word earns a new hostname only if the old one misleads, and “app” does not | 1Password.com and the admin consoles: the operator's address is the product's own domain, not a coined one |
the brief's proposed pickto be namedcollisions to avoidcandidates and notes
The problem
A name is the first explanation a customer hears, and the choice of explanation determines how the problem gets resolved. Six things need a word. The corpus says policy, agents, governance, endpoints and inventory (control plane once, sensor three times), so “agent” is unavailable to anything we install. Qplane is already public, so the control plane starts from that fact.
The core idea
Name the verbs, not the nouns: you deploy qcontrol, you open the app, you connect to the plane; if each verb has exactly one object, the names are right. The brief's pick: the app is Qpoint to the employee (one name for the person, as Tailscale and 1Password do), qlocal where a crate word is needed; Qplane stays; the source is plane; the operator and you, with HQ as the default sender label.
What is open
Everything: the brief proposes, it does not decide. The team does a first pass on the names; the decision is made in the open, in a session with an agent on the date the team sets, with c0's shortlist on G2's agenda. Then the checks: trademark, crates.io and GitHub, the tray tooltip at 12 px, the docker pull test, and the rename of ../qnative, once.