Operating numbers.
Open these numbers in the owner dashboard
Operating numbers computed from this deployment's records. Where a number cannot be measured, the card says so instead of guessing.
Reading /api/ops…
journeys published
dots on the coverage map
teams (accounts that own one)
Qualified leg
The paid third timestamp authority, read from the ledger of real draws — the nightly anchor, paid stamps, renewals — never from a probe. Counts are a floor; the supplier's own ledger is authoritative. Slot names are printed here and on no public page.
Reading…
Supply
Included use over the recorded horizon, against qualified tokens on file. A floor, not a forecast: the supplier's ledger is authoritative. The card below states whether supply limits sales. When the supply sales guard is off, plans and blocks remain for sale; qualified draws still need account allowance and an answering authority.
Reading…
Log founder minutes
Minutes you spent on accounts — onboarding, support, chasing a supplier on someone's behalf. Nothing measures this; what you log here is all the fifth number has. Each entry is added to the running total, never written over it.
How to read this page
Every figure is a count over the account records this deployment holds, taken at the moment the page loaded; nothing is cached and nothing is sampled. A request is a hand-off request the desk created; a deposit is a supplier record that landed on one. A paid period is what meter.mjs calls entitled: a plan other than the trial, paid through a date still ahead. The scan stops at 5,000 accounts and says so. No e-mail, no account id and no key leaves the route — it answers numbers. The definitions in full are in the repository, docs/OPS-DASHBOARD.md.