The franchise ledger
A public reading of Hashmark's archive: what the product has preserved, what moved recently, and exactly what each number does—and does not—mean.
Within the published seven-day refresh window. Computed Thursday, August 13, 2026 at 2:07 AM UTC.
archive
This is the durable player registry available for longitudinal scouting and career context, not a count of active people.
Distinct player rows in the franchise archive. This is not the number of human players.
Every accepted Companion App payload is retained as an audit receipt before normalization; retries are receipts, not unique sessions.
Authenticated raw export receipts retained before normalization. Idempotent retries may produce more than one receipt.
These are postseason stat rows preserved beyond the game’s rolling career summary—the core data-loss problem Hashmark exists to solve.
Postseason stat rows stored in Hashmark’s dedicated playoff vault.
This sums source-declared record counts in weekly team and schedule exports; it does not infer missing weeks as zero.
Sum of record_count declared by the latest unique weekly team/schedule export rows.
community
Each franchise is a separate long-memory football archive; the count includes created leagues, not anonymous visits.
League records created inside Hashmark. A league may be active, dormant, or in setup.
This counts registered accounts, not monthly actives, email subscribers, or page visitors; small values are banded for privacy.
Registered product accounts. Counts from one to four are rendered as a privacy band.
momentum
Export traffic is flat versus the preceding 30-day window; this measures receipts, not active users.
Receipts received in the trailing 30 days compared with the immediately preceding 30 days.
editorial
Every edition in this count is an append-only archive entry; corrections create a new record rather than rewriting history.
Append-only editorial archive entries, including corrections as separate editions.
Method & privacy
The homepage, this desk, and Analytica consume the same integrity-bound Feed v1 artifact. It is precomputed through one gateway-backed aggregate query; no public request reaches the product database. Counts from one through four are banded, identities are excluded, and zero is shown only when the source measured zero.