Accepted photo evidence earns full XP because it gives LifeQuest a concrete record to review. Honest self-report stays available at half XP because real progress still counts when a photo would be awkward, unsafe, or meaningless.
At 8:40 p.m., Imani was standing in her apartment kitchen in Chicago with flour on one sleeve and a loaf cooling on a wire rack. Her Craft quest was simple: bake bread from scratch. She had meant to take a photo before cleaning up, but the evening had already gone sideways, and now her phone was at 3 percent.
The quest mattered to her because it was part of a streak she had built after months of dropping hobbies the moment they got inconvenient. If she skipped the entry, the bad ending felt familiar: one missed night turning into another abandoned plan. Yet a photo of a half-sliced loaf and a messy counter would show something real. She opened LifeQuest, took the picture, submitted it, and waited for the AI plausibility review.
When the photo was accepted, Imani received the full XP for the quest. The next morning, the loaf was gone except for two slices in a container, but the proof and the progress remained.
Full XP reflects stronger evidence
LifeQuest treats XP as a record of effort with different levels of supporting evidence. A submitted camera photo can show the result or context of a quest in a way that a checkbox cannot. When the review accepts that evidence, the quest earns full XP.
That does not make photo review perfect, and LifeQuest does not claim it can prove everything. A camera image can be unclear. The result of a task may be hard to capture. Some progress happens in places where taking out a phone would be distracting or inappropriate.
The point is more modest and more useful: accepted evidence gives the system a stronger basis for recognizing a completed quest. Full XP marks that stronger basis.
This matters because life goals are full of tasks where a visible artifact exists. A finished sketch, a repaired bicycle chain, a set of meal-prep containers, or a study desk covered in completed notes can all give a quest a concrete ending. The photo is part of the record, not a performance for an algorithm.
For a different kind of evidence-weighted progress, compare photo review with server-timed focus sessions and GitHub verification. Each method fits a different kind of work.
Half XP keeps the quest alive when proof does not fit
A useful system needs an answer for the days when evidence is impractical. Self-report provides that answer.
Picture Imani again, two weeks later. She is on a crowded train home after helping a friend move boxes up four flights of stairs. Her Body quest was to do the lifting safely and take breaks instead of trying to prove she could carry everything at once. There is no meaningful photo to take, and asking everyone to pause for one would make the moment worse.
She can honestly self-report the quest and receive half XP. The smaller reward reflects less evidence, while the completion still acknowledges the work she chose to do.
That distinction protects two things at once. It gives evidence-backed completions a reason to matter, and it avoids turning progress into an all-or-nothing contest. A person who reads for twenty minutes after a difficult day, helps a sibling, practices a private skill, or gets through a quiet workout should not have to choose between staging proof and losing the quest entirely.
Self-report also leaves room for honesty. You decide whether you did the work. LifeQuest gives you a reduced-XP path when the best available proof is your own account.
Choose the proof that matches the quest
The best verification method depends on what actually happened. A coding quest may suit a qualifying public GitHub push. A focused study block may suit a server-timed focus session. A task with a visible result may suit an in-app camera photo. Every quest still has self-report as the fallback.
That choice is deliberate. One generic completion checkbox would treat a polished project photo, a timed focus session, and a private act of effort as if they carried identical evidence. They do not.
Imani did not need to turn every bread-baking session into a photo shoot after that first accepted review. On nights when she had a clear result and wanted full XP, she used the camera. On nights when she was cooking for friends and the kitchen was chaos, she self-reported and kept moving.
The reward structure gave her a practical question: “What proof genuinely fits this quest today?” That question is easier to answer than “Can I make this look impressive?”
Keep coaching separate from proof
Form coaching belongs in a different lane. You can record up to 60 seconds of exercise or craft form for asynchronous AI feedback, including a summary, cues, and concerns. That feedback can help you notice something worth adjusting before the next attempt.
It does not serve as quest proof or award XP. Keeping those roles separate prevents coaching feedback from posing as evidence that a quest happened. It also keeps the focus where it belongs: better practice, honest records, and a clear line between them.
Before submitting a quest, pick the method that tells the truest version of the work. Take a photo when the result is visible and safe to capture. Use a timer or GitHub verification when those fit. Use self-report when they do not, then return to the next quest with your streak still in reach.
Comments
No comments yet.