LifeQuest’s completion screen matches evidence to the quest instead of reducing every achievement to one checkbox. A new user can choose photo proof, a server-timed focus session, a qualifying GitHub push, or honest self-report when that method genuinely fits the work.
In April 1970, the Apollo 13 crew faced a dangerous mismatch. The command module used one shape of carbon-dioxide scrubber canister, while the lunar module used another. After an oxygen tank failure forced Jim Lovell, Jack Swigert, and Fred Haise into the lunar module, rising carbon dioxide threatened the crew. The available filters could help, but they did not fit the system keeping the astronauts alive.
NASA engineers in Houston had to build an adapter from materials already aboard the spacecraft. NASA’s historical account documents how Mission Control relayed the procedure, allowing the crew to connect the command module’s square canisters to the lunar module’s round openings. The solution worked, and Apollo 13 returned safely to Earth.
The lesson reaches far beyond spacecraft hardware: the method must fit the problem in front of you. Forcing every kind of work through one completion mechanism creates the same basic failure, with far smaller stakes. The proof may be useful, yet the interface between the work and the evidence is wrong.
One checkbox cannot represent every kind of progress
A photograph can plausibly show a finished meal, a cleaned desk, or a completed drawing. It cannot show that you studied without interruption for 25 minutes.
A timer can measure elapsed focus time. It cannot confirm that code reached GitHub after a programming quest began.
A public GitHub event can support a coding claim. It makes little sense for a run, a conversation practice session, or a handmade object.
That is what becomes clear when a new LifeQuest user opens the completion screen. The app presents the verification methods that genuinely apply to the quest. There is no universal “Done” button pretending every activity leaves the same kind of evidence.
That moment changes the meaning of XP. Progress through Body, Craft, Social, and Mind skills is tied to what the person actually did and what can reasonably support the claim.
Four completion paths for four evidence situations
Photo proof offers full XP when an in-app camera image passes an AI plausibility review. The review is evidence-weighted, not fraud-proof, and LifeQuest does not present it as certainty. A rejected image does not consume monthly usage, and self-report remains available.
A focus session awards full XP from elapsed server time. The device display is not the authority. If the app leaves the foreground, the server’s clock continues measuring the session. The away-time message explains exactly what that means for full XP.
GitHub verification applies to suitable Craft quests. LifeQuest checks for a qualifying public push made after the quest was created. Users link a username rather than granting private-repository access. A recent event may take up to five minutes to appear because GitHub activity is cached.
Honest self-report is always available and awards half XP. Some worthwhile actions do not produce practical objective proof. LifeQuest leaves room for that reality while preserving a meaningful difference between a claim and stronger evidence. That half-XP tradeoff is examined in more detail here.
The choice is not between trust and suspicion. It is between evidence types, each with clear limits.
Coaching and proof stay in separate lanes
LifeQuest also lets users record up to 60 seconds of exercise or craft form for asynchronous AI coaching. The response can include a summary, cues, and concerns, with a notification when it is ready.
That coaching does not complete the quest or award XP.
The separation matters because useful feedback answers a different question from verification. A form review can suggest how to adjust a squat or refine a craft movement. It cannot establish the full circumstances of the work, and it does not replace professional coaching.
Keeping those functions apart prevents a polished AI response from masquerading as proof. The completion screen remains about evidence. The coaching flow remains about improvement.
Choose the quest, then choose the honest evidence
When creating a quest, consider what trace the work can naturally leave.
Use photo proof when a current image can reasonably show the result. Use focus timing when elapsed attention is the relevant commitment. Use GitHub verification when a qualifying public push represents the coding work. Use self-report when stronger evidence would be impractical, intrusive, or unrelated to the goal.
Full XP marks accepted objective evidence. Half XP still records honest progress. Neither path punishes the user, and neither requires inventing proof where none belongs.
Apollo 13’s engineers did not solve their problem by insisting that every filter already fit every opening. They respected the mismatch and built the right connection. LifeQuest applies the same practical principle to everyday progress: start with the work, then use the completion method that fits.
Comments
No comments yet.