Honest States — qdash Stops Saying “Fleet Is Clean” When It Doesn’t Know

October 2, 2026SeedDashboardProductscreengrab

qdash Findings with the backend unreachable: one amber banner — “Can’t reach qdash — showing nothing rather than a guess. Retrying…” — every severity count reads “—”, and the worklist shows “—” instead of an all-clear.

Before: the same page with qdash answering 503 — “0 HIGH · 0 MEDIUM · 0 LOW · 0 PAST SLA” and “No findings. Fleet is clean. 🛡”, a reassurance nothing had measured.

After: the banner names the problem once; every count and the worklist read “—”.

Posture while loading: “—” in the five tiles and the score, skeleton rows in “What lowers the score” and the risk table — no green 100, no “All instrumented harnesses are hardened”.

Data Protection with qdash unreachable: tiles “—”, both access panels “—”, the paths table waiting — where it used to say “No sensitive file access ✓”.

A detail page while its record loads: skeleton rows (it used to render nothing at all).

Data on screen, then qdash drops: the roster stays, with a small floating “Last updated 11s ago · retrying” notice bottom-right.

A failed save: PagerDuty’s routing chip rejected — the chip reverts and a toast reads “Couldn’t change the routing for PagerDuty — qdash is unreachable.”

Another failed save surface: the evidence-packet export fails and a toast says so, with the reason.

Project: Dashboard
Designer: Mark
Tool: Playwright capture
Type: screengrab
Tags: c108qcontrolhonest-statesr31toastskeleton