Private Pro category · 9 compositions
Statistics
Context-rich metrics, trends, comparisons, and methodological notes. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 9 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Trend current
Benchmark bands
Cohort comparison
Milestone totals
Regional distribution
Usage health
Delivery cadence
Methodology annotated
Category contract
- Purpose
- Context-rich metrics, trends, comparisons, and methodological notes.
- Declared dependencies
- gummy-typography, gummy-button, gummy-card
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Statistics blocks
Choose a statistics composition only when a number helps a customer make or verify a decision. Pair every value with a clear unit, time range, comparison basis, and enough methodological context to prevent an attractive metric from becoming a misleading claim.
Format real values with locale-aware rules and define loading, unavailable, stale, zero, and error states. Charts need accessible summaries and consistent scales. Keep source or methodology links close to public claims, and never replace missing data with plausible demonstration growth.
Reconcile figures against their system of record, test extreme and negative values, and inspect colour-independent meaning, narrow layouts, tables, and screen-reader output. Owners should approve rounding, trend language, freshness labels, and any conclusion drawn from the displayed comparison.
For every statistic, supply a definition, unit, time zone, date range, comparison formula, freshness expectation, source owner, and approved rounding. Include zero, unavailable, stale, and error examples. Implementation should not calculate a persuasive trend from incomplete client data or let a delayed provider response silently reuse an old value without its timestamp.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.