Call My Name
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.
New in this cycle: The naming cycle's field of candidates
Why
A name is the first explanation a customer hears, and the choice of explanation determines the nature of the resolution (design's methodology, after Rittel and Webber). The roadmap adds a thing the employee opens and a thing the operator connects to; what they are called decides whether customers file them under MDM, under dashboards, under "another agent", or under the governance job they are actually doing. The corpus says customers think in policy, agents, governance, endpoints and inventory and almost never say "control plane" or "sensor"; "agent" is already taken twice. Qplane is already public. These facts, not taste, are the ground the session stands on.
Objective
Done means: names (or a shortlist with owners for the checks) for the five things in the brief, decided in the session and recorded in Outcome; the trademark, crates.io and bundle-id checks run for the chosen words; this directory renamed; design's CLAUDE.md, c130 Key Changes, c131 D1 and c137 D7 updated in the same change.
Scope
- Here:
cycles/c0.call-my-name/(brief.md, the session notes, Outcome), the directory name,Cargo.tomlcomments,README.md,CLAUDE.md - Design: the records named under Lineage
- www: a note only (the Qplane page's frame is c134's)
- Out: the backend's name (Pulse; engineering's), pricing names (go-to-market's), qcontrol's name (stays)
Key Changes
- kick-off (2026-11-09): created in design's c130 walk as this repo's first cycle.
brief.mdwritten: the five things to name, what exists (the q-family, Qplane's public page, the team's deploy/connect sentence, the c130 prompt's prompt, the corpus word counts across 205 first-hand and relayed items, six vendors' naming of the operator/endpoint/employee pieces), seven criteria from the brand, candidates per thing placed by the model each attaches to, the agent's proposal (the app is "Qpoint" to the employee withqlocalas the crate word; Qplane stays;planeas the third source; operator/HQ and you as the role words), a 60-minute session agenda, the checks, and patterns. Committed the same day (the repo's initial commit); no remote. - 2026-11-09, later: the team does a first pass on the names, and the decision is made out in the open in the session; the date is the team's to set, the walk is prepared, not scheduled. Added thing 6 to the brief: whether app.qpoint.io's successor keeps the hostname (proposal: the product is Qplane, the address stays).
Outcome
Decided in the team session.
Documents
The brief · the prompt, on the design site's cycle atlas.
Visual record
2 captures — heroes, page slices, and full-page renders. Click to view.
