LifeQuest matches proof to the quest because a single verification method cannot honestly fit every kind of real-world work. Timed focus can support a study session, a qualifying GitHub push can support coding work, a photo can support visible results, and honest self-report keeps progress available when objective proof does not make sense.
In 1970, Apollo 13’s crew faced a rising carbon-dioxide problem while travelling back from the Moon. The lunar module had round fittings for lithium hydroxide canisters; the command module carried square canisters. NASA engineers in Houston had to make the available parts work together with materials already aboard. The crew used the improvised adapter, and it helped manage carbon dioxide for the return trip. NASA’s History Office documents the mission and the engineering response.
The lesson is not “use duct tape on everything.” It is that the right solution depended on the shape of the problem. A square canister was useful. A round receptacle was useful. Treating either one as universal would have failed.
Why a universal timer looked tempting
We nearly made timed sessions the standard route to verified XP because the idea is easy to explain. Start a session, stay focused, finish it, earn full XP. For a reading block, practice session, draft, or revision sprint, that relationship can be meaningful.
LifeQuest runs focus sessions from server time rather than a counter that only lives on your phone. That matters because the timer should record elapsed time consistently. If you leave the app, the session does not pretend time paused. You can see why server-timed focus has a place in an evidence-weighted system.
But time alone has limits. A 45-minute timer can show a committed block of time. It cannot show that a room was cleaned, that a sketch was made, or that a particular workout happened. It also cannot confirm that a code change was pushed after a quest was created.
Making every quest fit a timer would turn the timer into a workaround. People would spend energy choosing a task that can be timed instead of choosing evidence that reflects the work they actually did.
Different quests leave different evidence
A coding quest has a useful external signal: a qualifying public GitHub push made after the quest exists. LifeQuest can use that signal for full XP when the quest belongs in the Craft domain and the account is linked to the relevant GitHub username. It does not require private-repository access or a generic “trust me” checkbox.
A visible task can call for a different kind of evidence. For a quest where a current photo is genuinely useful, the in-app camera can submit proof for AI plausibility review. Accepted proof earns full XP. Rejected proof does not consume a photo-review allowance, and the review is not presented as fraud-proof. It is a practical confidence signal, with clear limits.
A focus session works when time is the evidence that fits. A GitHub push works when a change in a repository fits. A photo review works when there is something useful to inspect.
That distinction also protects a separate job: form coaching. You can record up to 60 seconds of exercise or craft form and receive asynchronous feedback with a summary, cues, and concerns. Feedback can help you improve your squat, guitar posture, or movement pattern. It does not become proof that a quest was completed. Mixing coaching and verification would make both less clear.
Honest self-report belongs in the system
Some meaningful work does not create a clean artifact, a useful photo, or a timed block. A difficult conversation, a small act of care, a reflective practice, or a task completed away from a camera can still deserve progress.
LifeQuest lets you complete a suitable quest by honest self-report for half XP when objective proof is impractical. That is a deliberate middle ground. You keep momentum and acknowledge the work, while full XP remains connected to stronger evidence where that evidence genuinely applies.
This avoids a brittle rule where users either manufacture proof or lose all credit. It also avoids treating every completion as equally verified. Your streak, skill tree, ranks, cosmetic titles, and badges can reflect progress without asking you to perform your life for a camera.
For a closer look at why the distinction matters, LifeQuest’s comparison of rewards and evidence-weighted progression lays out the difference between checking off intention and earning full XP through a fitting signal.
Choose the evidence before you create the quest
The practical move is simple: write the quest around work you can recognize honestly, then choose the verification route that matches it.
If you want to spend a focused block outlining an essay, use a server-timed focus session. If you are building a feature, create the coding quest before the qualifying push. If the finished result is visible and a current camera photo helps establish plausibility, use photo review. If none of those methods fit, take half XP through self-report and move on.
Apollo 13 did not require one component to do every job. The engineers matched the available pieces to the connection they had. LifeQuest takes the same approach to progress: evidence should fit the work, instead of forcing the work to fit one evidence method.
Comments
No comments yet.