Pages
Findings Topline v1

Source: c79 finding-lifecycle — top-section bake-off · 2026-08-26

Eight treatments of the findings page's top section, all derived live from the same world. The reasoning: this is a worklist, so the topline's job is triage — ranked: is anything unseen (unacknowledged + oldest age) · what's about to breach (clocks running low) · what's already late · severity mix · are we keeping up (throughput, within-SLA %) · what's coming back (expiring exceptions) · where's the mass (worst control).

1 · Extended cards

The baseline enriched: the four severity/breach cards gain Unacknowledged and Due ≤ 30d. Minimal change; six equal boxes means nothing leads.

2
high
4
medium
0
low
3
unack
2
due ≤30d
0
past SLA

2 · Handling funnel

The attention pipeline (axis 2 as a flow): unseen → seen → routed → closed. Answers "is work moving," but hides severity and clocks entirely.

3
unacknowledged
2
acknowledged
1
routed
3
closed

3 · Remediation runway

Clock-centric: every open finding is a tick on a 45-day runway (severity-colored, breaches pinned at zero). The "running low" zone is tinted. Shows urgency as position — the only variant where time is spatial.

0 past SLA · 0 due ≤ 7d · 2 due ≤ 30drunway →
now10d45d+

4 · Two-axis grid

The model made visible: severity × handling for open findings. Complete and honest — and probably more matrix than a topline wants.

UnackAckRoutedhigh011medium310low000

5 · Verdict + worst lines

The c78 landing idiom at worklist altitude: one hero number (within-SLA %), then the three worst facts as toned sentences with names. Reads top-down like a briefing.

100%
within SLA · 1 judged
3 unacknowledged — oldest 2d: Codex · ravi
Nearest deadline — Claude Code · sofia due 09-04 (18d left)
Exception expires 09-15 — marcus-mba re-enters the queue

6 · Your move

Three action cards, each naming its top item — count for scale, name for the first click. Severity mix demoted to a quiet footer line. The purest triage reading of the page's job.

3unacknowledged
oldest 2d — agent: Codex · ravi
2running low
next: Claude Code · sofia · 18d left
1coming back
marcus-mba — exception expires 09-15
6 open · 2 high · 4 medium · 0 low · 100% within SLA

7 · Scoreboard

Report altitude on the worklist: within-SLA % hero, this quarter's found vs. resolved (throughput debt), and the worst control. Ties the page to the SLA report — but tells you how you're doing, not what to do.

100%
within SLA
2/10
resolved / found · Q3 2026
8 carrying into next quarter
Unapproved tool use
worst control · 2 open

8 · Compact strip

Everything as one quiet band — counts as words, tone only where deserved. Minimum chrome, maximum density; nothing is a click target and nothing leads.

6 open3 unacknowledged2 due ≤ 30d0 past SLA1 excepted · next exp 09-15100% within SLA

Composition notes

  • The ranking behind all eight: unseen (unacknowledged + oldest age — the adjudication-lag signal's only home) · about-to-breach (early warning beats breach count, per the c78 card audit) · already late · severity mix (context, not action) · throughput + within-SLA % (the report tie) · expiring exceptions (mechanical re-entries) · worst control.
  • Provisional verdict: 6 (Your move) — the only variant whose every element is an action with a name, matching the worklist's job; severity demotes to the footer line, where context belongs. 8 (Compact strip) is the minimal alternative if cards feel heavy; 3's runway is the one idea worth stealing into any winner (time as position is the clearest "running low" display). 1 is the safe non-choice; 2/4 explain the model better than they triage; 5 and 7 are report-altitude summaries that belong closer to the fleet overview.
  • All eight derive live from the shared world — no authored numbers. Cards would filter the table on click in product (the qdash stat-card behavior); not wired here.
  • Winner graduates to findings-regroup-v2, replacing the severity 4-up.

Qpoint Brand Style Guide