Source: c78 fleet-overview-reports — summary-card bake-off for the fleet-overview landing, 2026-08-21
How does a full report compress to a card? Four treatments, each shown as the complete four-card row it would produce on the landing — the composition is the candidate, not the single card. Every value is derived from the report fixtures (deriveCardSummaries()); nothing is authored twice. One attention device per card (c68's queue lesson). Judging law: the card earns a device only if it answers "do I need to open this report?" better than a number would.
Metric register — score + spark + delta
The report as an instrument dial: current score, trajectory, movement. The verdict band's first two organs, miniaturized. Answers "how are we doing" — but not "what's wrong."
Notes: calm, scannable, honest about trajectory. But an 89% and a 83% read as neighbors when one hides a failing control — urgency lives in a tone color alone, which is exactly one device but a quiet one.
Worst-thing-first — the report's most urgent line
The card as a briefing: lead with the single most urgent item, count the rest. c68's worst-thing-first verdict treatment, applied per report. Answers "what's wrong" — but a clean quarter renders four polite sentences and no numbers.
✗ CC6.1 failing — Open high finding — secrets.yaml read in an agent session (maps to LLM06)
✓ 4 open, all within SLA
▲ 5 shadow installs — newest Windsurf on chen-mba
✗ AI governance posture: 83% of controls compliant across 2 frameworks · 1 open high finding · 87% of the agent estate monitored
Notes: the GRC persona's Monday-morning question, answered. But trajectory vanishes — you can't see the needle move — and the board card's "worst item" is its whole headline, which overflows the register.
Last-run receipt — the auditor's register
The card as the newest snapshot on the shelf: run id, timestamp, score, movement since the previous retained run. Speaks the evidence-trail language — schedulable, re-runnable, retained. Answers "is the paperwork current" more than "is the fleet healthy."
Notes: perfectly matched to Mark M's snapshot mechanics and the only candidate that surfaces when the report last ran — but it buries today's state behind last run's, and a monthly cadence means the card can be three weeks stale by design.
Mini-document — the report as a thumbnail
The card wears the artifact's identity: a tiny white page. Leans on the document face — reports are files you hand people, so the landing shows four files. Identity over density.
Notes: the strongest identity statement — "your landing page is four reports" is legible at a glance — and the weakest instrument: state hides in a caption, trend is gone entirely. A thumbnail answers "what is this," not "do I need to open it." Expanded: seven hierarchy-driven versions in report-card-minidocs.
Provisional verdict — awaiting Mark's pick
- No single candidate answers the judging question alone. The register carries state + trajectory; worst-first carries urgency; the receipt carries the evidence-trail cadence; the mini-doc carries identity.
- Lean: register + one worst line. Candidate 1's spine (score · delta · spark) with candidate 2's single urgent line beneath — two registers, one device each. The receipt's run id survives as a footer whisper (`CMP-2026-08 · run Aug 1`), which is all the auditor cadence needs at landing altitude.
- The mini-doc isn't wasted — it's the right form for the snapshot shelf and export surfaces, where the object really is a file.
- Stage 5 (fleet-overview-v3) composes the merged form; final treatment pick is Mark's.