Progression mechanics that persist across sessions
Progression is the always-on layer: currencies, status, recognition, streaks, and public rank. These pages explain how each primitive behaves under the hood so PMs and engineers can make sound design and implementation decisions.
Mechanics5 primitives
Best forLoyalty, retention, habit
AudienceEngineers + technical PMs
Key takeaways
Quick read- Points track value, tiers track status, badges track recognition, streaks track consistency, and leaderboards track relative rank.
- Most mature programs combine at least two progression primitives; these pages help you avoid modeling one primitive as another.
- Read these before writing admin config or choosing which metric becomes your source of truth.
Primitives
Browse the progression cluster
Guide cluster
Core concepts
5 playbooks
01Playbook
Points
Ledger, expiry, spendable balance vs lifetime, and idempotent grants.
Read the guide02Playbook
Badges
Definition vs award, locked-state rendering, and recognition patterns.
Read the guide03Playbook
Tier
Qualification, next-tier progress, overrides, and downgrade policies.
Read the guide04Playbook
Streak
Period keys, grace windows, freeze tokens, and at-risk signals.
Read the guide05Playbook
Leaderboard
Ranking periods, scopes, caches, and individual rank lookup.
Read the guideNeed the big picture?
Map progression to your product goal
Read the strategy layer for when-to-use guidance, then come back here when the team is ready to implement.
1 brief to align the room2 mechanics max in version one
What happens next
01
Pick the mechanic
Choose the smallest working system for the brief.
02
Launch without rebuilds
Configure rules and rewards in one place.