Methodology // v3.3 // 3 August 2026
Hours.gg publishes a combined ranking-hours total that orders products on an exact category or game board. It is a weighted ranking total, not product-use duration.
Public ranking formula
Combined ranking hours add the protected foundation input and eligible verified-playtime contributions.
The displayed total combines a protected foundation input with capped, eligible Steam-verified game-hour contributions.
the measure
The published order keeps its founding and verified-playtime inputs distinct.
Hours.gg publishes combined ranking hours: the weighted total used to order each exact board.
This value is not product-use time, a player count, ownership, adoption or market share.
combined_ranking_hours = protected_foundation_hours + eligible_verified_playtime_contributionprovenance
The public explanation documents each input without publishing composition, quantities, or internal controls.
The displayed total combines a protected foundation input with capped, eligible Steam-verified game-hour contributions.
The ranking begins with a completely frozen synthetic baseline. It is permanently immutable and contributes ranking hours, but it does not represent a real player, vote, review, pledge, or product-use duration.
Those protected numeric values cannot be raised, lowered, rebalanced, reassigned, regenerated, or deleted. A reviewed correction can append a label or membership-state decision, but it cannot alter the value.
evidence
Exact observed game hours can support a capped connected contribution without becoming product-use time or a standing signal.
Verified Steam playtime belongs to the connected evidence layer. It contributes capped game hours to the combined ranking total without becoming product-use duration.
connected_hours_weight = Σ min(exact_game_hours, 4,000)For this connected-only calculation, each eligible record contributes the lesser of its exact observed game hours and 4,000.
The cap controls contribution math. It does not estimate how long any product was used.
counting
Until identity resolution and deduplication are validated, every count uses the same observable unit.
One eligible connected setup is one current eligible setup record for the exact Steam account, game, and category at the stated cutoff. A report states the board, method version, cutoff, and setup denominator.
The observable record is not silently merged, split, or relabelled as a headcount or market-uptake measure.
publication
There is no universal row-count threshold. Wording and evidence requirements are bound to a versioned policy.
No single threshold unlocks every claim. Each claim policy binds an exact metric, cohort, denominator, observation window, freshness rule, suppression rule, permitted wording, limitations, approval, and activation state.
All policy rows below are unratified and blocked for production use. This page documents the court; it does not activate a claim.
Combined ranking hours
combined-ranking-hours.v1
Anonymous ranking projection
Exact board, projection version, material timestamp, method link, and approved wording.
Connected setup distribution
connected-setup-distribution.v1
Eligible connected-only projection
Exact cohort, setup denominator, cutoff, method, limitations, and reproducible evidence.
Setup transitions
setup-switching.v1
Post-cutover append-only setup events
Trustworthy event window, transition definition, denominator, censoring, and suppression.
Enterprise cohort
enterprise-connected-cohort.v1
Connected-only customer-safe projection
Contracted cohort, current enterprise-use scope, suppression, reproduction pack, and human approval.
legal boundary
F-003 records product direction for anonymous aggregate contribution, not permission to activate it.
F-003 approves product direction under which a documented legacy deliberate pledge may contribute to anonymous aggregate ranking. It does not authorize named Steam identity publication, exact individual-hours publication, optional profile fields, research use, or enterprise use.
New named, exact, optional-field, research, or enterprise surfaces require the applicable current versioned consent scope. One scope never silently implies another.
controls
Projection state, evidence freshness, consent, policy approval, and release approval are checked before a claim can appear.
A claim is withheld unless its exact source projection is available, current enough for the policy, complete, privacy-safe, approved, and active. Missing evidence does not become a displayed zero.