Contribution heatmaps can show that a person returned to a habit over time, but they cannot decide what happened away from a code repository. Progress at the gym, desk, workshop, or library needs evidence that fits the quest, with an honest fallback when proof is impractical.
At 8:42 p.m., Maya is standing beside a squat rack with her phone on the floor against her water bottle. She has just finished the last set in a strength quest she created after weeks of skipping workouts whenever a lab report ran late. Her streak is one completion from breaking, and the gym closes soon.
A green square on a heatmap would show that she checked in. A generic completion button would accept the same claim. Neither can tell the difference between doing a set, opening an app in the locker room, or recording an unrelated clip from last month.
That distinction matters because the bad ending is bigger than one missed square. If Maya starts treating every hard day as completed progress, her rank can keep climbing while the routine that was supposed to support her quietly disappears. The system has to make room for real life without asking her to pretend that every kind of work leaves the same trail.
A streak records return, not the whole story
GitHub made the contribution heatmap familiar: a small grid that turns activity into a visible pattern. A habit tracker built in that style can be useful for the same reason. It answers a simple question: did you come back today?
That is a good question. It is not the only one.
A coding quest can leave public evidence after the quest exists, such as a qualifying GitHub push. A focused study block can be tied to elapsed time measured by a server. A bread-making practice session or a workout may have a photo that makes the completed work plausible. These signals have different strengths and different limits.
LifeQuest treats that difference as part of the loop. A verified completion can earn full XP when the evidence fits the quest. Honest self-report stays available for half XP when objective proof would be awkward, unavailable, or beside the point.
The reduced reward is not a penalty for being human. It is a clear label for uncertainty. Maya can still protect the habit on a day when filming feels wrong or her phone is dead. Her progress continues, while the system avoids acting as though every completion carried the same evidence.
Evidence should match the work
A single checkbox creates a strange incentive: make every kind of progress look identical. LifeQuest asks a more useful question before awarding XP: what evidence could reasonably support this particular quest?
For a desk task, a focus session can use server time rather than a device-side countdown. The timer on screen helps someone pace themselves, but the reward comes from elapsed time the server records. The Countdown That Cannot Earn Full XP, and What the Server Clock Changes explains why that distinction matters when a phone is left unattended or an app is backgrounded.
For a coding quest, GitHub verification looks for a qualifying public push made after the quest was created. Old activity cannot be recycled into a new quest. For physical or hands-on work, an in-app camera photo can go through an AI plausibility review. Acceptance earns full XP; rejection does not consume a review allowance, and self-report remains there if the photo cannot make the case.
None of these methods claims to prove a whole life. AI photo review is not fraud-proof. A focus session cannot prove understanding. A GitHub push cannot prove every minute spent thinking. Evidence is weighted because it is evidence, not because it is perfect.
Keep coaching and proof in separate lanes
Maya sees another option after her set: record up to 60 seconds of form for asynchronous AI coaching. The feedback may flag a cue to try next time or a concern worth taking seriously. It can arrive later as a notification.
She does not use that feedback as proof that the workout happened.
That separation is deliberate. Coaching answers, “What could I improve?” Verification answers, “What support do we have for awarding this level of XP?” Combining them would blur a useful boundary and could make a coaching summary feel like a verdict. Exercise form also deserves humility. Product feedback is not professional coaching or a substitute for medical advice.
Maya chooses a photo for the completed quest, then records a short clip because she wants feedback on her movement. The photo is accepted. Her quest gets full XP, her streak remains intact, and the coaching review stays pending in its own lane.
Later, at her kitchen table, Maya opens the response and sees one cue to use during her next session. Her rank has moved because the evidence fit the quest. Her next workout has a clearer starting point because coaching stayed focused on learning.
Build a record you can read honestly
Heatmaps are compelling because they make consistency visible at a glance. LifeQuest keeps that feeling through streaks, skill trees, domain ranks, cosmetic titles, and badges across Body, Craft, Social, and Mind. The harder work happens underneath the visible progress.
Choose a quest that can be checked in a way that makes sense. Use full-XP verification when it genuinely applies. Take half XP when the honest answer is, “I did this, but I cannot reasonably prove it here.” That record will be less uniform than a grid of green squares. It will also tell a more useful story when you look back at it.
Comments
No comments yet.