A photo, server-timed focus session, qualifying GitHub push, and self-report provide different kinds of evidence. LifeQuest gives full XP when a verification method supports the quest, and half XP when honest self-report is the only practical fit.
Apollo 13 needed evidence that matched the problem
In April 1970, the Apollo 13 crew faced rising carbon dioxide in the Lunar Module after an explosion forced them to use it as a lifeboat. The Command Module had square lithium hydroxide canisters. The Lunar Module used round ones. The hardware existed, but it did not fit.
NASA engineers in Houston had to work from the materials actually available on board and devise an adapter the crew could assemble. The outcome was uncertain while they worked. The improvised solution helped remove carbon dioxide, and the crew returned safely to Earth. NASA’s Apollo Flight Journal documents the mission and the work around its life-support constraints.
That moment matters because “we have a filter” and “this filter can work in this spacecraft, with these materials, right now” were very different claims. Mission control needed evidence suited to the claim before acting on it.
LifeQuest treats completed quests the same way. “I did it” can be a truthful report. A photo can show a relevant result. A server record can show elapsed focus time. A GitHub push can show that qualifying code activity happened after the quest was created. Those are all useful signals, with different strengths and limits.
Four paths, matched to the work you did
A photo proof submission can fit work that leaves visible evidence. You take the photo in the app, submit it for AI plausibility review, and receive full XP if the evidence is accepted. The review is evidence-weighted progress, not a claim that AI can make proof fraud-proof.
A focus session fits work whose meaningful proof is time spent staying with the task. LifeQuest measures that session using server time rather than a timer controlled by your phone. For a 25-minute focus quest, ending at 24:59 leaves the record short. That can feel fussy until you remember what the XP means: the full amount represents a completed, verified session. This focus-session example shows why the server record matters.
A GitHub push fits a coding quest, provided the quest belongs to the Craft domain and the push qualifies after the quest was created. A push from last week does not document today’s quest. Nor does a push prove every kind of work. It proves a specific event in a public development record.
Self-report fits everything else, especially the work that is real but hard to capture cleanly. You may have had an important conversation, practiced privately, or completed a task with no sensible photo, timer, or code record. LifeQuest keeps that route available and awards half XP. Honest progress still counts.
Full XP carries a clearer record
Giving identical XP to every completion method would flatten meaningful differences. It would tell you that a checked box, a reviewed photo, a measured focus session, and a qualifying code event all say the same thing. They do not.
The point is not to turn your life into an audit. The point is to let the strength of the evidence shape the strength of the reward. A self-report can mark real effort without pretending it carries the same record as a server-timed session. A photo can support a completed workout or project without being confused with form coaching, which exists to offer feedback rather than validate XP.
That separation matters. A 60-second form-coaching submission can return cues, concerns, and a summary for exercise or craft practice. It may help you improve your next attempt. It does not become proof that a quest was completed.
Apollo 13’s engineers did not ask one instrument to answer every question. They used the information that applied to the immediate constraint. Your quests deserve the same practical judgment.
Choose the proof that makes sense before you begin
When you create a quest, ask one simple question: what could honestly show that this particular work happened?
For a writing or coding task, a qualifying GitHub push may be appropriate. For deep study, use a focus session. For a finished physical result, use an in-app photo if it is genuinely relevant. For work that does not produce practical evidence, complete it with self-report and take the half XP.
That choice turns verification into part of planning, rather than a frustrating decision after the work is done. It also protects the meaning of your ranks, streaks, titles, and badges. Each full-XP completion carries a record that fits the quest. Each self-report preserves room for the parts of life that cannot be neatly captured.
Comments
No comments yet.