QualityQuality Trend
12 days

Analytics & Quality

Operational health and test investment on one surface. The top half is live from the read-only analytics views (event readiness, blockers, role coverage); the bottom half is the cockpit's own automated-test growth across the build waves. Nothing is estimated — an unreachable database or empty trend renders a safe placeholder.

Operational quality

Live roll-ups across every event the cockpit can see. Sourced from v_event_readiness, v_open_blockers, and v_role_coverage.

100%

Role coverage

24/24 required

4

Events tracked

2 at risk

2

Open blockers

2

Critical blockers

Lowest-readiness events

The events most in need of attention, sorted lowest average readiness first.

0%

RW05-SMOKE-Z9NUQ

DRAFT · 0 nodes

0 blockersceiling 100%
58%

ISR-IND-OCT26

DRAFT · 3 nodes

3 blockersceiling 40%
95%

ISR-IND-SEP26-REH

REHEARSAL_READY · 3 nodes

0 blockersceiling 100%
99%

ISR-IND-MAY26

COMPLETED · 2 nodes

0 blockersceiling 100%

Test investment

The cockpit's automated-test surface and how it grew. Illustrative project-tracking state — the cockpit's picture of itself, not product data.

421

Tests today

+421

Added since baseline

9

Waves recorded

+72

Peak wave (G)

Cumulative tests

Running total of automated tests after each wave landed, left → right.

12 → 421 tests across 9 waves

Tests added per wave

Net new tests each wave shipped. Bar length tracks the wave against the busiest burst; color reads as a heat scale.

FFoundation
+12 · 12 total+12
AWave A — validation-engine + ui kit
+38 · 50 total+38
BWave B — web app + BE migrations
+64 · 114 total+64
CWave C — write-path APIs + UX
+47 · 161 total+47
DWave D — cockpit live-data + drift + E2E
+53 · 214 total+53
EWave E — MVP02 backend depth
+41 · 255 total+41
F2Wave F — frontend completeness
+36 · 291 total+36
GWave G — i18n/auth + quality
+72 · 363 total+72
HWave H — security (RLS) + E2E + design
+58 · 421 total+58

Operational figures are live from the read-only analytics views and render an empty-state when the database is unavailable. Test counts are the cockpit's own build log (illustrative project-tracking state), not product data.