Index Overview
To close: Write the Outcome: hierarchy and mocks done, landing shipped through c109 · Move to HISTORY.md
last activity Aug 27
The dashboard's first page overlapped with the inventory page, and nobody had settled what a person should see first when they log in.
An order for the first page: a one-line verdict, what needs you, then doors to each area. Seven mocks, ending in Mark's three cards. Picks never came; later cycles shipped it.
Documents
With file names, on their own page →Start here
Documents
Threads
- thread — glance-ideas (2026-08-14)
- thread prompt: inventory-card (verbatim)
- thread: inventory-card — health seam + possibility space (doc-first)
- thread — posture-findings-overlap (2026-08-14)
- thread — queue-ideas (2026-08-14)
- thread prompt: three-card-mock (verbatim)
- thread: three-card-mock — Mark's manual design as a page mock
- thread — verdict-ideas (2026-08-14)
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
The landing went from a verdict sentence over a list of alerts to three cards: inventory, compliance and remediation deadlines.
From verdict page to three cards · came from Mark Peterson and Mark Parsonopen →
- 2
First a one-line verdict, then the things that need you, then doors to the rest of the product.
What comes first · came from Mark Parson
- Three rounds of ideas for showing what needs attention, from plain lists to cockpit warning lights. New in this cycle
- A side study proposed folding the posture page into findings, so risk lives in one list. 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.
“machine readable, human readable. So for the human readable for the auditor, machine readable for your GRC platform like Vanta.”
market-analyst /calls/2100ac03… (local)“if we have a critical vulnerability finding, for example, remediated 14 days, we have a high, it's 30, A medium, it's 90 days”
market-analyst /calls/2100ac03… (local)c68-D1 The landing is a daily driver; an executive summary would be a separate future page. — Mark Parson
c68-D5 Inventory card: write it up first and mock it later, with the body figure as one treatment. — Mark Parson
The landing went from a verdict sentence over a list of alerts to three cards: inventory, compliance and remediation deadlines.
From the record: no recorded conversation behind this one.
c68-D1 The landing is a daily driver; an executive summary would be a separate future page. — Mark Parson
c68-D2 The scorecard is demoted to a card. — Mark Parson
c68-D3 The canonical coverage band lives on the landing. — Mark Parson
First a one-line verdict, then the things that need you, then doors to the rest of the product.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Named the reports a landing should sum up
On the Aug 20 product review, a week before the three-card mock, he listed the reports a security team needs, including compliance, SLA insights and inventory status, and gave remediation deadlines by severity. The three cards follow that shape.
“if we have a critical vulnerability finding, for example, remediated 14 days, we have a high, it's 30, A medium, it's 90 days” first-hand
Set the landing's job and drew the three cards
Made it a daily driver with the scorecard demoted to a card, asked for broader and more visual attention ideas, then designed the three-card landing by hand and asked for four changes to it.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 7
The full record 5 decisions · 11 key-change entries · 1,383 words · 7 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 c68 →