A LifeQuest focus completion earns full XP when the server confirms that the required time elapsed between the recorded start and finish. The device can display the countdown, but the server’s timestamps decide the award.
Imagine Mina, a first-year chemistry student, at 9:17 p.m. in a quiet corner of the campus library. Her periodic table notes are open beside a paper cup of cold coffee. A practice quiz closes that night, and she still confuses the trends that run across a period with those that run down a group.
She creates a 25-minute Mind quest, opens a focus session, and puts her phone beside the notebook. From Mina’s side, the screen begins counting down.
From the backend’s side, one fact matters first: the session has started.
The start timestamp becomes the source of truth
When Mina taps to begin, LifeQuest creates a server-timed focus session and records its start. That timestamp establishes when the eligible work period began.
This distinction matters because a timer displayed on a phone can become unreliable. The app may move into the background. The screen may lock. The operating system may suspend parts of the app. A device clock can also change.
LifeQuest avoids asking the phone to prove how much time passed. The countdown helps Mina see her remaining time, while the server keeps the record used for XP.
At 9:29 p.m., she switches to a message from her lab partner. When she returns, the app tells her she was away and that nothing paused. The session kept aging according to server time.
That creates a tense choice. Mina can abandon the quest and leave the chapter unfinished, or use the remaining minutes to work through the last set of examples. If she stops too early, the server will not treat a shorter session as the 25-minute completion she set out to earn.
She turns the phone face down and keeps going.
For a closer look at why the phone’s clock does not control the result, read The Phone Clock LifeQuest Won’t Trust, and What Decides Your Full XP.
The finish request triggers three checks
When Mina reaches the end and taps finish, the backend receives a request tied to that specific focus session. It can then evaluate the completion using information it already holds.
First, it identifies the quest attached to the session. The focus work must belong to the quest Mina started, rather than an unrelated task created later.
Second, it checks eligibility. The quest must still be in a state where it can receive a completion award, and the focus session must be the applicable verification method being finished.
Third, it calculates elapsed time from the server-recorded start to the finish. The number shown by a device-side counter does not replace that calculation.
This gives the completion a simple audit trail:
The server recorded the beginning. The server observed the finish request. The elapsed interval met the quest’s required focus duration. The quest remained eligible for completion.
If the interval falls short, LifeQuest does not quietly round it up. Mina can continue when the session permits, or use honest self-report for half XP when objective proof is not practical. The distinction preserves a useful meaning: full XP reflects accepted evidence, while half XP still gives credit for work reported honestly.
Full XP follows accepted evidence
At 9:42 p.m., the finish request arrives after the required 25 minutes have elapsed. The backend accepts the focus completion and awards the quest’s full XP.
That award comes from elapsed server time. It does not claim Mina mastered the periodic table, understood every example, or stayed perfectly attentive for every second. A timer can verify duration, not comprehension.
This boundary makes the evidence useful without making it grander than it is. LifeQuest can say that an eligible 25-minute focus session ran for the required time. Mina still decides what the work meant and whether another quest is needed tomorrow.
The same boundary separates focus verification from other completion methods. A qualifying GitHub push can support a coding quest. An accepted in-app photo can support work with visible evidence. Self-report remains available for suitable work that cannot be objectively shown. Each method answers a different question.
Evidence-weighted progress works because the award matches the strength of the evidence. Habit App Rewards: How Evidence Weighted Progress Keeps Credit Grounded in Reality explores that principle beyond the focus timer.
What Mina sees after the award
Mina sees the celebration for a verified, full-XP completion. Her quest moves out of pending work, her progress updates, and the result names the completion tier.
The backend sees a shorter story: a start timestamp, enough elapsed server time, an eligible quest, and a full-XP award.
At the library table, Mina closes the practice quiz with answers entered before the deadline. One index card remains beside her cold coffee, now covered with arrows showing which periodic trends run in which direction. Tomorrow’s study session has a clear starting point.
Comments
No comments yet.