The Rank System
Classification,
not competition.
Your Ascent rank is a mirror, not a scoreboard. It reflects where you are operating right now — based on what you actually did, not what you planned.
Establishing the baseline. The act of logging consistently is the work at this stage.
Starting point
Consistent output forming. A pattern is visible in your data. Momentum is accumulating.
Pattern forming
Reliable execution. You show up regardless of motivation. No filler days at this level.
Reliable execution
High-leverage output. Decisions are compounding. You are in the building phase of long-term work.
Decisions compound
Elite sustained output. This is not a sprint — it is a stable operating level. Identity is locked at this tier.
Identity locked
How It's Calculated
Your rank is derived from a single rolling metric — your 7-day weighted average of deep work hours. No subjective scoring, no manual input beyond your sessions.
Core Formula
Rank = f(weighted 7-day avg of logged hours)
Each of the last 7 days is weighted, with more recent days carrying slightly more influence. This means a strong day today has more impact than a strong day 6 days ago — rewarding recency without punishing past slumps.
1
Log a session
Start the timer on any task. When you stop, that session is recorded with its actual duration. Sessions are tagged to a category automatically based on the project.
2
Daily total is computed
At midnight, all sessions for that day are summed into your daily output figure. Rest days register as 0 — no penalty, just data.
3
7-day weighted average is updated
Your rolling average updates daily. The weighting formula applies a decay coefficient — recent output counts more. This is the single number your rank is derived from.
4
Rank is assigned
Your rolling average is compared against the five tier thresholds. The result is your current rank. It can move up or down daily as your average shifts.
Why It Works This Way
Most productivity systems use streaks or point totals. Ascent doesn't. Here's why each design decision was made deliberately.
Rolling average
Rewards trajectory, not perfection
A streak breaks the moment you miss a day. A rolling average absorbs one bad day without catastrophe. What matters is the direction of the line — not whether it's unbroken.
Streaks
Punish recovery
Streak systems create an all-or-nothing psychology. One missed day can erase weeks of progress visually, which often triggers complete abandonment. That's a design flaw, not a motivation tool.
Identity-based ranks
Classification over competition
You are not competing against other users. You are classified by your own output. "Architect" means you are operating at Architect level — that's a fact about you, not a trophy.
Leaderboards
External validation dependency
Leaderboards tie your sense of progress to other people's behavior. If everyone improves, your rank drops. Ascent's system is self-referential — your rank only reflects you.
No shame at any level
Foundation is a valid operating state
If you're averaging 0.8h of deep work per day, Foundation is your current reality. That's the starting point, not a failure state. The rank names are descriptive, not judgmental.
Resets every 90 days
Prevents stagnation
Ranks reset on a 90-day cycle. This keeps the system forward-looking — you can't coast on past output indefinitely. Each cycle is a fresh classification based on recent behavior.
The 90-Day Reset
Every 90 days, your rank resets to be recalculated from scratch. This is intentional. It prevents a high rank from becoming a resting identity that requires no maintenance.
Your historical rank data is preserved in analytics — you can see what tier you held in previous cycles. The reset affects only the live dashboard display and the active classification.
The reset date is shown on your dashboard so you always know how far into the current cycle you are.