Fleet Overview Reports
Our advisor listed four reports a security team needs, and our founder framed the landing page as a summary of them. None of the four existed yet.
All four reports were mocked in full on one shared shape, with a landing page of four summary cards. Mark never picked a card style, and on 2026-11-03 the work closed into c128 Reports, which carries on its report shape and the Board report's summary.
Documents
With file names, on their own page →What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
Compliance, SLA Insights, Inventory and Board reports exist as full mocks, all built on one shared report shape.
Four reports, one shape · came from Mark Peterson and Mark Parsonopen →
- 2
The fleet overview became four cards, one per report, each opening its full report.
The landing is a summary of the reports · came from Tyler Flint and Mark Parsonopen →
- The cards became tiny documents where size and weight of type carry the message, and every line has to say something. In words
- Alert text that should have been red was quietly grey, because of how the shared library names its red; it now uses a different red. 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)c78-D1 Reports first, landing last; a full mock page for each of the four reports, Board included. Start with all the information, trim later. — Mark Parson
c78-D2 Card summaries and the whole Board report are worked out from report data, never written by hand. — Mark Parson
Compliance, SLA Insights, Inventory and Board reports exist as full mocks, all built on one shared report shape.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
The fleet overview became four cards, one per report, each opening its full report.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Named the four reports
On the Aug 20 product review he listed the reports a CISO hands out: SLA insights, an inventory like a bill of materials, a compliance snapshot and a board summary, each as a PDF for people and JSON or CSV for tools, and asked for posture as a trend, not a static score.
“machine readable, human readable. So for the human readable for the auditor, machine readable for your GRC platform like Vanta.” first-hand
"The landing page is really just a summary of those 4 reports"
Ran the list-the-reports exercise on the call and framed the fleet overview as their summary, with each card launching its report.
Asked for documents that speak
Set reports first and the landing last, picked the mini-document card over the plan's lean, and ruled that every line on a card must communicate.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 6 decisions · 10 key-change entries · 2,058 words · 0 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 c78 →