GitHub streaks show that you kept pushing code. They do not show whether a push moved a specific goal forward. LifeQuest treats a qualifying push as evidence tied to a coding quest created before that push, then awards full XP when that connection checks out.
A signal needs a shared reference
In 1999, NASA lost the Mars Climate Orbiter as it approached Mars. The investigation found that one part of the system used pound-seconds while another expected newton-seconds. Both sides had numbers. The numbers failed because they did not refer to the same unit.
NASA’s Mars Climate Orbiter Mishap Investigation Board documented the failure plainly: data had moved through the system, but the reference point was wrong.
A GitHub contribution graph has a similar limitation, at much lower stakes. A green square can mean a tiny documentation change, a generated file, a meaningful fix, or work unrelated to the thing you meant to practice. It records activity. It cannot supply the goal behind that activity.
That is why a streak feels good while still leaving an awkward question: what did I actually get better at?
Create the quest before the evidence exists
LifeQuest’s GitHub verification starts with the goal, not the graph.
You create a coding quest under a Craft skill, such as “Fix the failing parser test” or “Ship the first API endpoint for my portfolio project.” The quest exists first. Then you make a qualifying GitHub push after the quest was created.
When LifeQuest can verify that later push, the quest earns full XP. The time order matters. A push from last week cannot be retrofitted as proof for a quest you made today.
That is a small constraint, but it changes the meaning of the record. Instead of asking a contribution calendar to explain your intent after the fact, you state the work you intend to do and attach evidence when you do it.
The system does not claim that a push proves excellent code, deep focus, or a finished project. Public GitHub activity cannot carry all of that weight. It establishes a narrower fact: a qualifying push happened after you committed to this particular coding quest.
LifeQuest also keeps that path limited to Craft-domain quests. If the quest is for a body, social, or mind skill, a GitHub push would be the wrong kind of evidence. The verification method should fit the work.
Full XP has a reason behind it
A generic “complete” button asks you to make every kind of progress look the same. LifeQuest gives you a choice between proof methods that genuinely apply.
For a coding quest, a qualifying GitHub push can earn full XP. For work that cannot be practically proven, honest self-report remains available at half XP. That option matters because real progress often happens away from a camera, timer, or public commit history.
The difference is not a punishment for self-reporting. It is a way to keep the XP signal legible. Full XP carries evidence where evidence fits. Half XP still recognizes work that only you can reliably report.
GitHub verification has ordinary limitations, too. LifeQuest reads public GitHub events, so you need to link a valid GitHub username. The backend can cache events for up to five minutes, meaning a push made seconds ago may not appear immediately. And a push made before the quest exists will not qualify. That timing rule is deliberate, not a bug.
For the practical edge cases, see What Happens When You Push Before Creating a Craft Quest?.
Use commits as evidence, not a scoreboard
A useful coding loop is simple: name the outcome, create the quest, work on the smallest meaningful next step, then push when that step is real.
“Work on my app” is hard to verify and easy to postpone. “Add password-reset validation and push the change” gives you a clear finish line. You may still revise the code tomorrow. You may discover the task was larger than expected. But the quest gives the push context that a streak alone cannot.
The Mars Climate Orbiter failure was about incompatible measurements. Your coding habit has a friendlier version of the same problem: activity and progress can look interchangeable until you need to tell them apart.
A GitHub streak can keep you showing up. A quest created before the push helps you see what you showed up for.
Comments
No comments yet.