Full XP from a LifeQuest focus session is awarded from time measured by the server, not from the countdown displayed on a student’s phone. The phone can show progress, but the server records when the session starts and decides whether enough elapsed time has passed when the student returns.
The measurement has to live outside the display
In 1970, Apollo 13 had a carbon dioxide problem in space. The lunar module’s filters used round cartridges, while the command module had square ones. The crew could not solve that mismatch by changing what an onboard indicator displayed.
Engineers at Mission Control in Houston worked with the same limited materials available to the crew and devised an adapter that made the command module cartridges fit. NASA’s Apollo 13 history documents the episode because the solution had to work in the physical system carrying Jim Lovell, Jack Swigert, and Fred Haise home.
That distinction matters: a reassuring display has value, but the underlying condition decides the result.
A focus timer has the same separation of roles. Your phone can count down, animate an XP bar, and play music while you work. Those are useful cues. They cannot establish that a session lasted long enough for verified progression. A device clock can change. An app can be closed. A connection can drop. Time can pass while the screen is no longer in front of you.
LifeQuest starts the focus session on the server. When you finish, the server measures the elapsed time from its own recorded start. If the session meets the quest’s requirement, it earns full XP. The completion is based on a record outside the device that is showing the animation.
A countdown is useful, but it is not the evidence
Students often use timers because beginning is hard. A visible countdown lowers the friction of sitting down with a chemistry chapter, a coding assignment, or a practice routine. It gives the session a boundary.
That visible timer still has limits. If it paused whenever an app disappeared from the screen, it could claim a block of focused work that never occurred. If it trusted the device’s local clock alone, the reward would depend on a setting the student controls.
LifeQuest treats the countdown as a guide and the server record as the evidence. When you leave the app during a running focus session, the session does not pretend that time paused. On return, the app can tell you how long you were away. That may feel stricter than a timer that quietly freezes in the background, but it keeps full XP meaningful.
The alternative remains available. If a quest is genuinely complete but objective proof does not fit the moment, honest self-report earns half XP. That path respects real effort without presenting an unverified completion as server-timed evidence. The Half XP LifeQuest Gives You When Proof Does Not Fit the Moment explains why that distinction exists.
Full XP should describe a stronger record
The point of verification is not to turn every task into surveillance. It is to make the XP in a skill tree describe the kind of completion behind it.
A self-reported study session, an accepted photo, a qualifying GitHub push, and a server-timed focus session each leave different evidence. LifeQuest lets a quest use the method that actually fits. A coding quest can use a GitHub push. A physical task may use a camera photo. A focused block of work can use elapsed server time.
Form coaching stays separate from this process. You can submit up to 60 seconds of exercise or craft footage for asynchronous AI feedback, including cues and concerns, but coaching feedback does not count as proof of quest completion. Advice about form and evidence of completion answer different questions.
This is why a verified focus session earns full XP only after it finishes. Starting the timer signals intent. Returning to finish creates the event the server can evaluate. The reward follows the completed record, not the opening tap.
Make your next session easy to finish honestly
Before you start, choose a quest with a clear unit of work: read a section, draft an outline, solve a problem set, or work through a focused coding task. Then start the focus session when you are ready to give it your attention.
If you need to step away, do not build your plan around a timer quietly preserving a streak. Return when you can. The server will measure the real elapsed session, and you can decide whether the quest still deserves full XP through focus verification or half XP through self-report.
Apollo 13’s crew did not get home because a gauge looked better. The adapter had to alter the actual air system. In the same smaller-stakes way, a LifeQuest focus session earns its strongest progression signal when the record behind it can support the claim.
For a practical example of what returning to a running session looks like, read Server-Timed Focus Sessions: Why Eli Earned Full XP Only After Returning.
Comments
No comments yet.