Source: c78 fleet-overview-reports — mini-doc iteration 4 (after report-card-minidocs-v2), 2026-08-24
The content is settled; this iteration bakes off the attention device — how a card calls out its area of concern. Ten devices on the v2 briefing card, in four families: line-level (ink, highlighter — color the concern itself), object-level (border, spine, pink-slip — color the file), boundary-breakers (badge, flag, dog-ear, chip — change the silhouette), and a labeler (stamp — name the problem class). One device per card holds: when a device carries the tone, the text under it goes neutral and keeps only weight. The fixture spread is the test — two alert cards, one warn, and SLA clean: a device is judged as much by its absence as its presence.
Ink — the control
line-levelThe v2 baseline: tone lives in the text of the concern itself. Nothing else changes.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: Perfect locality — the color sits on exactly the line to read — and the weakest reach: at squint distance all four cards look calm. The device the rest are judged against.
Highlighter — the reviewer's swipe
line-levelA marker swipe across the concern line — the paper metaphor's own gesture, more area than colored text, same locality.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: The best line-level device: area beats ink weight at a distance while still pointing at the exact line. It reads as "someone already reviewed this file for you." Scales badly if many lines are flagged — three swipes is a coloring book.
Border — the file signals
object-levelThe whole paper is outlined in tone. Concern colors the object, not the line.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: Strongest pure-color reach — but the loudest row on this page: three toned perimeters read as more alarm than information, and locality is gone (which line?). The stage-4 worst-first treatment had this same property.
Spine — the file-tab edge
object-levelTone on the left edge only, like the colored spine of a folder in a drawer.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: The border's reach at a third of its volume; the row stays calm and the eye still snags. Pairs naturally with the ledger. Still binary and still can't point at a line.
Pink slip — the paper changes color
object-levelThe sheet itself is tinted — the strongest statement a document can make about itself.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: Unmistakable at any distance, and far too heavy for this fixture world: every calm figure on the card inherits the alarm. If it has a place, it is a reserved top rung — a catastrophic state — not a standing device.
Merit badge — the seal on the file
boundary-breakerA sticker seal over the card's corner — tone plus a count, breaking the page silhouette the way a foil seal breaks a certificate's.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: The silhouette break wins the four-up scan before color is even read, and it is the first device that carries magnitude — 2 failing vs 5 shadow. Absence-is-calm is clean. Risk: charm shades into kitsch; the dashed seal ring is doing a lot of costume work.
Flag — sign here
boundary-breakerA sticky flag over the page's top edge — the gesture a paralegal leaves on a contract.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: Slimmer than the badge and quieter, but it carries no magnitude and reads as to-do more than alarm — a flag says "look here eventually," not "this is failing."
Dog-ear — the folded corner
boundary-breakerThe corner folds over in tone: this file has something in it. The quietest possible boundary break.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: Near-subliminal — pleasing, and probably too quiet for alert-grade concerns. Better suited to warn-grade ("worth a look") if devices are ever tiered by severity.
Chip — the notification badge
boundary-breakerThe app-icon count chip — the one device borrowed from software instead of paper.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: Instantly understood by anyone with a phone, magnitude built in, smallest footprint of the breakers. But it concedes the document fiction — the chip says "app," and the mini-doc's whole identity argument is "file."
Stamp — the labeler
labelerIteration 2's audit stamp, shrunk and moved off-center so it labels the concern class without covering the content.
✗CC6.1 — secrets.yaml read in an agent session · sofia
✗SI-4 — Adapter error on one machine — events stopped for 2 agents · kai
▲5 shadow installs · 4 personal accounts — newest Windsurf on chen-mba
Notes: The only device that says what kind of problem ("2 failing" vs "5 shadow") in words. The overlap still costs a little legibility, and two stamped cards side by side start to feel like a prop room. Note the clean card earns a quiet "current" — the stamp is also the only device with a positive state.
Transfer check — leaders on the ledger
A device must work on both v2 compositions. The two provisional leaders on the ledger card: the badge (card-level, silhouette) and the highlighter (line-level, on the toned rows).
Merit badge on the ledger
Highlighter on the ledger
Notes: both survive the move. The badge is indifferent to what's under it — its virtue; the highlighter gets better on the ledger, where every concern is already a row it can swipe.
Provisional verdict — awaiting Mark's pick
- The families trade reach for locality. Line-level devices tell you which line but vanish at squint distance; object-level devices carry across the room but can't point; boundary-breakers win the four-up scan because a changed silhouette beats a changed color; only the stamp says what kind of problem.
- Magnitude is underrated. Badge and chip are the only devices that say how much (2 failing vs 5 shadow); border, spine, fold, and tint are binary. A CISO triaging four cards wants the count before the color.
- Lean: merit badge outside, weight inside. Paper-native, counts built in, absence-is-calm, and it survives the ledger unchanged. The highlighter is the line-level runner-up if the pick favors in-page devices over silhouette.
- Devices may be rungs, not rivals. Ink → badge → pink-slip reads as an escalation ladder (noted → needs you → on fire) rather than four competing styles; if adopted, the ladder needs a severity rule from the fixtures, not taste. Recorded as an open thread.
- The chip works instantly but is the one device from software rather than paper — using it concedes the document fiction the mini-doc exists to keep.