My growth: the road to Everest
NepWalk teammates are warriors: they keep learning, help one another and finish work with care. My growth tells that story through milestone emblems, achievement badges and verified XP. Everyone can celebrate progress; nobody is ranked against a teammate.
Who participates
The manager and engineers participate. The founder plans, assigns, reviews and accepts work but has no team XP, badges, milestone emblems, weekly targets or personal learning progress. Keep founder development outside this workspace. Existing history is preserved; no teammate’s progress is removed.
The founder can still inspect team growth: Warriors shows teammates’ work, levels and Everything about [name] opens a full profile with their badges, learning, tasks and activity by date. This is oversight, not founder participation in XP.
Delivery first
Today, My growth, Warriors and teammate profiles show task progress before learning progress. Tasks count as complete only after acceptance (or release), not while waiting for testing or review. The denominator includes assigned tasks and excludes unassigned backlog and cancelled tasks. Empty assignments show zero progress. Learning is tracked separately and never substitutes for completed product work. The founder sees team delivery and team learning rather than personal XP. Team learning counts each participating member’s topics, including shared topics once per person. The next badge suggestion prioritises work achievements. XP rules stay unchanged.
The simple view
My growth starts with your current level, total XP and the XP needed for the next level. It shows one next badge and a compact list of badges already earned. Every earned badge appears directly below the current level banner, before the next badge goal. Select a badge to read its achievement. The road to Everest is a visible milestone graph with reached, current and locked labels; its green segment follows verified XP. On narrow screens, scroll the graph horizontally or focus it and use the arrow keys. All milestones also have an accessible text description. “Browse all badges” remains collapsed until you want the detail. There is no separate “Within reach” section or milestone-emblem counter. XP thresholds and existing achievements remain the same.
How rewards work
- Milestone emblems unlock at XP thresholds. Your current emblem and warrior title appear on Today. Every earlier milestone remains in your collection.
- Achievement badges recognise what you did: build, test, research, teach back, review or help the team. Each badge shows its requirement and progress. Select it to see how to unlock it; filter the collection by earned or still to unlock.
Unlocking an emblem or badge does not award extra XP. XP already came from the contribution itself. No bonus loops, purchased points or points for hours.
XP: what counts
| Contribution | XP | When |
|---|---|---|
| An accepted task | Task size: 5, 10, 20 or 40 | After checks, a real manual test and independent review; accepted by Prakash or Niwesh for P2/P3 work of others (A24) |
| Reviewing a teammate's task | 3 | When that task is accepted; founder review earns no XP |
| Understanding a learning topic | 5 | After teach-back, questions, corrections and a brief summary |
| Applying an understood topic | 2 | After a real application is recorded; optional |
| Reporting an accepted ticket | 2 | When the founder accepts it into the backlog or makes it a task |
These are current defaults. The founder can tune contribution values in Team settings. Tasks are sized before work, based on scope and quality, not hours or speed. A task must not be split artificially to farm points. Repeated acceptance, teach-back edits, duplicate tickets and reading alone do not create extra rewards.
A year-sized summit
Everest starts at 4,000 XP. At an illustrative 80 verified XP per week, that is 50 active weeks: roughly a year. This is a calibration assumption, not an observed team average, an individual quota or a promise about a completion date. There is no calendar gate. Faster verified progress can reach Everest sooner.
For example, three accepted 20-XP tasks, three understood 5-XP topics, one accepted review (3 XP) and one useful accepted ticket (2 XP) total 80 XP. Actual work and learning vary. Do not create busywork to hit that example.
After four weeks of real activity, review the pace across roles and adjust future planning if needed. Any threshold change needs an explicit decision; do not change it silently or remove people's earned progress. Current team members have zero XP at this rollout, so the new curve does not demote an existing rank.
| Milestone | Warrior title | From |
|---|---|---|
| 1. Kathmandu | Recruit | 0 XP |
| 2. Lukla | Scout | 30 XP |
| 3. Phakding | Trailblazer | 100 XP |
| 4. Namche Bazaar | Ranger | 250 XP |
| 5. Tengboche | Guardian | 500 XP |
| 6. Dingboche | Vanguard | 900 XP |
| 7. Lobuche | Champion | 1,400 XP |
| 8. Gorak Shep | Commander | 2,000 XP |
| 9. Everest Base Camp | Legend | 2,700 XP |
| 10. Kala Patthar | Summit Warrior | 3,400 XP |
| 11. Everest | Unstoppable | 4,000 XP |
The first milestone welcomes you; the early ranks offer visible progress while you learn the system. Later ranks take sustained contributions. The mountain trail is a game metaphor, not a climbing itinerary or travel guidance.
Unstoppable flames
- 4,000 XP: Everest, Unstoppable, flame ×1.
- 4,500 XP: flame ×2.
- 5,000 XP: flame ×3.
- Every further 500 XP adds one flame, without resetting XP or collections.
Flames come from lifetime verified XP, not attendance, consecutive days or working through a break. They never expire. Moon, Mars and galaxies are possible future themes; they are not implemented or required to keep growing now.
Achievement collection
| Badge | Requirement |
|---|---|
| First step | Your first accepted task |
| Builder | An accepted implementation task |
| Quality guardian | An accepted test task |
| Explorer | An accepted research task |
| Guide | An accepted documentation task |
| Extra mile | An accepted task picked from the backlog; always optional |
| Bug hunter | A ticket accepted by the founder |
| Second pair of eyes | Review a teammate's task that gets accepted |
| Curious mind | A topic explained until understood |
| AI foundations | All assigned AI foundations topics demonstrated |
| Steady pace | Reach the weekly goal once |
| Steady warrior | Reach the weekly goal four weeks in a row, with rest weeks protected |
| Craftsperson | Five distinct accepted tasks, of any kind |
| Trusted reviewer | Five reviews of distinct accepted tasks |
| Lifelong learner | Ten distinct topics demonstrated |
| Applied wisdom | Three understood topics used in real work; application stays optional |
| Unstoppable | Reach 4,000 verified XP |
The former four-week Unstoppable badge is now Steady warrior, retaining its
existing on-a-roll identity and requirement. Unstoppable now names the summit.
Task and learning badges use the award history. Reopening work or revisiting a lesson with new questions does not erase the achievement or grant it twice. The current task or learning status still shows what needs attention. No production records or XP are generated by the UI previews.
A motivating day
- Today: a compact emblem, current XP and next milestone, then today's tasks. Follow one next action. Work on one task at a time, including its quality gates.
- Academy: learn one topic, explain it back and answer questions. The AI foundations badge shows your demonstrated progress; application is optional.
- My growth: inspect the milestone collection, badge progress and recent victories. Locked badges explain their requirements instead of hiding them.
- Closure: see verified accomplishments, learning, extra work and XP gained, plus your rank and any milestones crossed. Unfinished work stays open.
- Together: celebrate every teammate's contribution in roster order. Your own hours remain personal; the founder and manager can view hours for planning.
Weekly rhythm and breaks
A18's weekly commitment remains 15 hours of work and 5 hours of learning, logged at closure. Weeks run Sunday to Saturday in Kathmandu time. Extra hours earn no XP. Rest weeks, set by the founder for festivals, illness or exams, have no target and never break a weekly streak. An unfinished current week also does not break it. A missed working week can reset the current weekly streak; it never removes XP, rank, flames or a previously demonstrated task or learning achievement.
Boundaries that make rewards trustworthy
- No leaderboard, race, loss of lifetime XP, speed bonus or overtime bonus.
- No fake test evidence or learning summaries. A failed test is useful feedback.
- No automatic task acceptance, role switching or shortcuts around review.
- Learning, testing, research, documentation and reviews matter alongside coding.
- Optional backlog work and optional applications remain optional.
- Ordinary progress updates do not interrupt work with a modal or flashing effect.
- Reduced-motion preferences are respected; rewards are readable without motion.