StatCard
- Status
- Specified
- Family
- 2 of 13
StatCard is specified but not yet built. The spec below is the contract it will be built against — reviewed before the code, which is the order that makes the review worth doing. See the roadmap for where it lands.
The four-layer spec
The minimal unit: label + value. 16px inset, no delta, no media. For dense grids where a KpiCard is too much.
Lifted verbatim from Cards. The doc and this page are the same paragraphs, so they cannot disagree.
Also in Cards
- BalanceCardThe hero: one trusted number.
- KpiCardMetric + delta + optional sparkline.
- AccountCardBank account with available vs. current.
- PaymentMethodCardThe physical card object. 3D flip, pointer tilt.
- RunwayCardMonths of runway with a burn line.
- InvoiceCardInvoice summary with aging state.
- SubscriptionCardRecurring charge with next-billing.
- AnomalyCardA flagged deviation with its explanation.
- GoalCardTarget vs. actual with a progress rule.
See also
A component is specified in one place, defined in another, and running in a third. All three, from here.
Elsewhere in the system
Where StatCard sits in the rest of the system — the live section it renders in, the calculators that compute what it displays, and the ledger payloads it is fed from.
Components are copied into your repository and meant to be edited — rounding policy, fiscal calendar and compliance copy differ per company.
Told when Cards changes
Components are copied into your repo, so a fix here does not reach you on its own. One email when a component in this family changes in a way that needs a migration — and nothing when it does not.