The engine
A rule engine that takes no view on what should count
A trigger, some conditions, an effect. That is the whole model, and it is where the product actually lives — everything else is plumbing around it.
Triggers
An action logged, a level gained, a badge unlocked, a streak milestone reached, a reward redeemed, a season ended. Six of them, and every one emits.
Conditions
Match on the action, the source it came from, the time of day, a running total, or how many times somebody has done it before.
Effects
Award XP, mint currency, unlock a badge, or fire a notification. Rebalance the numbers whenever the curve stops working.
Progression
Levels, streaks, and the parts people actually chase
Progress has to be visible on a Tuesday, not just in week one.
XP and levels
Every logged action lands in under a second. Shape the curve yourself; nothing is baked in.
Streaks in your own timezone
Daily windows in the community’s timezone, so "today" ends when your people think it does — not at UTC midnight.
Badges
Define the trigger, upload the artwork. Locked badges stay visible as silhouettes with a progress count, so people know what they are chasing and how far off it is.
Leaderboards and seasons
Rank by anything you log, over any window. Seasons end and boards reset, so a strong March stops haunting everyone in October.
The loop
Currency, rewards, and a feed that does the noticing
Recognition that does not depend on a manager remembering.
A currency you name
Rules mint it, members spend it. The product does not supply the name and does not need to.
Reward store
You define what points buy. Members request, an admin approves and marks it fulfilled — every cycle has a human in it.
Activity feed
Who moved, what they logged, who is one action from levelling. Members can opt out of the feed and the leaderboard without losing anything they earned.