Honest self-report earns half XP because effort still matters when objective evidence is impractical. LifeQuest preserves momentum while reserving full XP for completion backed by an applicable verification method.
Imagine Nia, a design student in Manchester, standing beside her kitchen table at 11:43 p.m. A half-finished cardboard prototype sits between a mug of cold tea and three snapped craft-knife blades. She has rebuilt the hinge twice, and tomorrow morning her class will test whether it holds.
Her LifeQuest crafting quest says, “Build and test the prototype hinge.” Nia did the work, but she forgot to photograph the process. The room is too cramped to frame a useful recording now, and another attempt could damage the only working version. Without a truthful fallback, tonight ends with zero XP. Her streak disappears from view, and the system treats three hours of careful work like it never happened.
Evidence and effort answer different questions
Evidence can support a specific claim. A camera photo can undergo an AI plausibility review. A coding quest can check for a qualifying GitHub push made after the quest was created. A focus session can use elapsed server time instead of trusting a device-side counter.
Those methods strengthen confidence that a quest happened as described. When accepted, they earn full XP.
Still, objective proof does not fit every real goal. You may practise a difficult conversation alone, revise handwritten notes, help a classmate understand a concept, or work on a craft project where stopping to document each step would interfere with the work itself. A generic demand for proof would reward goals that are easy to record and neglect goals whose value happens off camera.
Nia faces exactly that mismatch. Her hinge exists, and her effort was real. The available evidence is weak because she thought about the prototype before she thought about the app.
Self-report gives her an honest choice: complete the quest for half XP and state that she did the work. She does not receive the same reward as an accepted photo, server-timed session, or qualifying GitHub push. She also does not have to pretend the evening was a total failure.
Half XP protects the difference between imperfect and imaginary
A binary system has only two stories: proven success or nothing. Real life contains a much wider range.
Sometimes you finish the work and forget the photo. Sometimes the useful result is private. Sometimes the quest involves judgment that a camera cannot settle. Sometimes recording would be awkward, distracting, or inappropriate. In those cases, zero XP makes an inaccurate claim of its own. It says no meaningful effort occurred.
Half XP records a more careful conclusion: you reported completion, but LifeQuest lacks strong objective evidence for the full reward.
That distinction matters because progress systems shape attention. If one missed proof step erases the night, the easiest response is to stop tracking honestly or abandon the streak altogether. If every tap earns full XP, evidence loses its purpose. Half XP keeps the next quest worth doing while preserving a clear reason to choose stronger verification when it genuinely applies.
This is also why form coaching stays separate from quest completion. A short exercise or craft recording can receive asynchronous AI feedback about cues and concerns, but coaching feedback does not become proof. Different tools answer different questions, and LifeQuest does not present AI review as fraud-proof or as professional coaching.
For a closer look at the reward distinction, read Why Does Camera Proof Earn Full XP While Self-Report Earns Half?.
A smaller reward can preserve a stronger habit
At 11:51 p.m., Nia chooses self-report. The quest moves to completed, she earns half XP, and the hinge remains intact for the morning test.
The smaller reward leaves a useful trace. She can see that the effort counted, while also seeing what would have earned full XP. For her next build session, she creates the quest before starting and decides whether a suitable photo can capture the finished result. If photography would interrupt the work again, self-report remains available.
There is no punishment mechanic waiting for her. XP is informational. The goal is to make progress visible with the level of confidence the available evidence supports.
That approach also reduces the temptation to manufacture proof after the fact. Nia does not need to stage a misleading photo or repeat risky work solely to satisfy the system. She can accept the lower reward, keep an honest record, and plan better evidence next time.
Choose verification before the work begins
The practical move takes less than a minute. When you create a quest, ask what completion will look like and which verification method genuinely fits.
Use a server-timed focus session when elapsed focused time is the work. Use GitHub verification for a qualifying coding push when the quest falls within the Craft domain. Use camera proof when a current image can plausibly show the completed result. If none of those methods fits without distorting the task, plan to self-report for half XP.
The following morning, Nia places the prototype on her classroom table. The hinge holds through the first test. Her LifeQuest record does not claim more certainty than she earned, and it does not erase the night that made the test possible.
Comments
No comments yet.