← Cycles
design · c147activestarted Nov 13Auto draft — not yet reviewed

Findings, a Common Tongue

Waiting to be picked uplast activity Nov 13· waiting on Mark Peterson

Next: The Peterson conversation from peterson.md; then qnative's cycle from qnative-brief.md, whose step 0 is design's (each policy's configuration in the sidecar). Committed in 81f3ee59ee, unpushed; c149 builds the simulation's prevented rows against it.

Why we did this

A rule that stops something on your laptop gives you no explanation, and an inbox for it would be one more thing to check.

What happened

One record, the finding, is shared by your laptop and the company: it goes up whole, follow-ups come down onto it, and what was stopped in time stays the gentlest case.

New in this cycleThere is one record for a policy moment, and both your laptop and the company read it.
At a glance
7
changes
2
conversations
36
decisions
1
outside helpers

What changed

The three changes that matter most, in plain words. Open any one to see it.

  1. 1

    There is one record for a policy moment, and both your laptop and the company read it.

    The common tongue · came from Mark Parsonopen →

  2. 2

    Your machine's findings now have a page in the app, drawn exactly as the security team sees theirs, so the next step can change what doesn't suit you.

    Findings in the native app, copied first · came from Mark Parsonopen →

  3. 3

    What was stopped in time now reads as kept safe, not as a list of offences, and you can ask for what your work needs from the finding itself.

    The person's view of the same record · came from Mark Parson and Rob Genovaopen →

Also in this cycle
  • Every message c137 designed is now either the finding itself, an event on it, a line on Status, or shelved. In words
  • The app asks once how noisy it should be, and by default it says nothing until you look. New in this cycle
  • When HQ writes to you about something on your machine, it arrives on that finding, in their words, and you answer there. Early → final
  • What looked like a mailbox became the company's own record, seen from your chair. 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.

Someone said

From the record: no recorded conversation behind this one.

We decided

c147-D3 One finding shape on both sides: findings bubble up to a connected plane, trainings bubble down. — Mark Parson

c147-D4 Prevented is softest: an Enforced finding is born Resolved: prevented; c121 D16's stamp stands and c121 D3 is superseded (Open by default). — Mark Parson

c147-D5 Every finding bubbles up; prevented ones arrive softer. — Mark Parson

So now

There is one record for a policy moment, and both your laptop and the company read it.

Someone said

From the record: no recorded conversation behind this one.

We decided

c147-D2 Start by copying design's phase-4 Findings (S2, S1) as this machine's view; redesign after the copy exists. — Mark Parson

c147-D8 The rail: Safety & Security → Findings · Settings, the web's word for the same object. — Mark Parson

c147-D9 Meridian first; a world's findings are derived by the lab's detector from its own sessions, never seeded without a label. — Mark Parson

So now

Your machine's findings now have a page in the app, drawn exactly as the security team sees theirs, so the next step can change what doesn't suit you.

Someone said

From the record: no recorded conversation behind this one.

We decided

c147-D19 The person's view opens on Open with Observed shown; prevented findings are one quiet group with a count. — Mark Parson

c147-D20 The SLA clock and the remediation deadlines leave the person's view; the shape keeps them for the plane. — Mark Parson

c147-D21 The person's member table is severity, the finding, the harness, when and status; the rail scrolls once the section joins it. — Mark Parson

c147-D14 The person never moves a finding's status; the plane resolves. — Mark Parson

So now

What was stopped in time now reads as kept safe, not as a list of offences, and you can ask for what your work needs from the finding itself.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Peterson
Advisor · Moto

Framed compliance as a posture, never 100%

Relayed by Mark at the same session: security sets a posture as close to ideal as it can and deals with the gaps as they come up; an auditor needs to see that something went wrong and was corrected. His walk is owed before review stop 3.

MP
Mark Parson
Qpoint team

Saw that the finding was already the answer

Asked to rename the inbox so a correction never feels like prison, ruled Safety & Security, then saw that design's findings already carry both sources (before and after, and the plane's remediations), questioned the purpose of c137, and ruled one shape on both sides: findings bubble up, trainings bubble down.

RG
Rob Genova
Qpoint team

Called the inbox another thing to check

At the 2026-11-12 Product session: employees should not have to make it part of their lives, the homepage promises no changes for end users, and messages from HQ belong in the channels people already have.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

The common tongueNew in this cycle
Findings in the native app, copied firstBefore → after
→
The person's view of the same recordBefore → after
→
How much qcontrol saysNew in this cycle
HQ's half, on real rowsEarly → final
→

Everything captured · 12

The full record 36 decisions · 11 key-change entries · 2,731 words · 12 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 c147 →

Qpoint Brand Style Guide