← Sketches · the native app program

The common tongue

c1472026-11-13

One finding, minted where the activity happened; the machine, the person and the plane each append their own events to it, and the record never changes.

Source: c147 initial-prompt.md (Mark, 2026-11-13: findings bubble up, trainings bubble down, one shape on both sides) and plan.md R1–R7, Q1–Q7; finding-shape.md §1–§8; the lab's model in governance-fixture.ts (c114, c121 D16); c133 event-shape.md; session f8d58bc9 (2026-11-12).

This machine · the endpoint and the person at it
◇qcontrol on this machine

The sensor. It sees the activity, and a policy's mode decides whether it stops it. It mints the finding and writes detect, prevented and recurred. On a standalone machine, who raises findings is Tyler's question.

●The person at the keyboard

Drives. Writes their own events: asked IT, asked for access, acknowledged, training completed. Their events are proof and conversation; they never move the finding's status.

▣Safety & Security → Findings · Settings

This machine's findings, copied from the lab's S2 and S1 first, then made the person's (Phase 3). The OS notification announces a finding as loudly as the person chose: Quietly, When it matters, Teach me.

up: the finding, whole, with every endpoint and person event

down: the plane's events on this machine's findings

⬚One finding

Immutable once detected. Everything after is an event; the status is a fold over them. The same id on both sides.

id F-<fingerprint>: policy · resource · person · device
policy_id and the Policy Config version live at detection
outcome enforced · observed, stamped once (c121 D16)
subject user · team · device · agent · account
resource mcpServer · account · provider · path · dataClass
observed_at and the session
severity at generation: critical … informational
evidence one line, the sensor's words
⬓Its events, append-only

Each says who wrote it (from: endpoint · person · plane). No side edits another's.

endpoint detect · prevented · recurred
person asked-it · asked-access · acknowledged · training-completed
plane training-assigned · follow-up · resolve · reevaluate · reopen

up: arrives as the same finding, never a copy

down: trainings, follow-ups, resolutions

The company's plane · the design prototype today (Q6)
●The operator

Security or IT. Reads S2 (Open by default; prevented findings in a quiet group, Q4) and S1 (what happened, the history). Resolves with a reason; never edits a finding.

◇Policies and trainings

A policy's mode stops or records; a policy or an operator assigns a training (c133), which travels down as training-assigned. HQ's follow-up travels down in HQ's words.

▭Reports and the audit log

Prevented counted as the policy working, never against a person (c128). An auditor reads: something went wrong, and it was corrected.

Observed: Gene's personal account (f8d58bc9)
1detect

endpoint · Observed: a session ran under a personal account. Open.

2training-assigned

plane · the policy assigns T-ACCT-1; it travels down onto the same finding.

3training-completed

person · the record goes up; the status does not move (c133 D9).

4resolve

plane · Resolved, with the record as the reason. Something went wrong, and it was corrected.

Enforced: an agent blocked a thousand times (R4, prevented is softest)
1detect

endpoint · Enforced: a connection to an MCP server not on the list was blocked.

2prevented

endpoint · in the same moment: born Resolved: prevented. Nothing to fix.

3recurred × 999

endpoint · the same policy, server and person that day: one finding, a count.

4counted

plane · Reports count it as the policy working; it never counts against the person.

Where c137's fifteen message types went
The finding itself

enforcement-notice, from the plane and from qcontrol locally: detect, plus prevented when the activity was blocked.

An event on the finding

training-assignment → training-assigned · censure → follow-up · contact-it → asked-it · acknowledgement → acknowledged · training-completed, unchanged.

Status

identity-confirmation: standalone or connected (f8d58bc9) · sensor-state: Status and the tray icon (c131).

Shelved with c137

hq-notice · responsibility · diagnostics-request · diagnostics-sent · reply · connect-request · grant-notice. HQ uses email and Slack.

the shape: one finding and its eventsnew in c147: the native Findings, the person's eventsexists today (qcontrol, the lab's plane prototype, c133)peopleshelved with c137
The problem
When qcontrol stops or records something on a laptop, the person sees a disruption and nothing else. c137 answered with a message channel and an inbox; the 2026-11-12 Product session found the inbox "another thing to check" against the promise of no changes for end users. The notion it was reaching for already existed: the finding.
The core idea
A finding is the one shape a policy moment takes on both sides. It is minted on the machine, travels up whole, and gathers events from three writers; nothing is edited, so the two sides never disagree about what happened, only about what has arrived. Prevented is the softest case: born resolved, counted as the policy working. The person's words soften; the record does not.
What stays open
Five calls in finding-shape.md §10 for review stop 1: the writer field, the person never moving status, the window, prevented as kind and resolution, and a policy that resolves on training completion (with Peterson). Tyler's one question: who raises findings on a standalone machine.

Qpoint Brand Style Guide