A focus-session reward should depend on time recorded by the server because a device-side timer can pause, drift, reset, or report a value the server cannot verify. Server timing gives LifeQuest a shared record of when the session started and finished, so full XP reflects elapsed time rather than a claim from one phone.
Imagine Lena, a first-year student in Manchester, sitting in a quiet corner of the library at 7:42 p.m. Her statistics notes are open beside a paper cup gone cold. She has one evening left to prepare for a difficult seminar, and skipping another study block could break the streak she has spent weeks building.
She creates a Mind quest, starts a LifeQuest focus session, and puts her phone face down.
The same session from two points of view
From Lena’s side, the session looks familiar. A countdown moves across the screen. Optional focus music fills her headphones. Her job is simple: stay with the work until the required time has passed.
Then the screen goes dark.
Lena taps the power button. Nothing. Her battery has died, and the charging cable is back in her room. The visible countdown has disappeared with it.
Now the reward is genuinely in doubt. If the phone was the only authority, Lena might lose the full XP even after doing the work. The alternative would be equally weak: the app could trust whatever elapsed time the phone reports after restarting, even though that value may be incomplete or unreliable.
The server sees a different sequence.
When Lena started, LifeQuest created a focus session with a server-issued start time. The phone displayed a countdown derived from that record, but the display did not become the source of truth. Time continued passing after the screen went dark because the session existed beyond the device-side counter.
That distinction protects both sides of the reward. Honest work does not disappear with a dead screen, and a changed phone clock cannot manufacture elapsed time.
Why the countdown is only the display
A countdown feels like the session itself because it is the part you can see. In LifeQuest, it acts more like a window onto the server’s record.
When you finish a focus session, the server compares its own start and finish times. Full XP comes from that recorded interval. If you leave the app and return, the screen can explain how long you were away, but it does not pretend the session paused while you were gone.
This design also sets a clear boundary. Only one focus session can run at a time. There is currently no cancel endpoint, and an abandoned session clears after 12 hours. Those limits matter because credible progress depends on rules the product can consistently enforce, including the inconvenient ones.
A device-only approach would place too much authority in a fragile environment. Phones sleep. Apps close. Operating systems interrupt background activity. Device clocks can change. The server provides one consistent timeline for deciding whether the required interval passed.
That is the same principle behind LifeQuest’s broader evidence-weighted system: each quest offers verification methods that genuinely fit the work. A coding quest may use a qualifying GitHub push made after the quest was created. A visible result may use an in-app camera photo and AI plausibility review. When objective proof is impractical, honest self-report remains available for half XP. The difference between an honest claim and full credit comes down to the evidence attached to the completion.
What the server can prove
The server can establish that a session began at one recorded time and finished at another. It can calculate elapsed time without relying on a counter maintained by Lena’s phone.
It cannot prove that she understood every page, resisted every distraction, or produced brilliant notes. Time evidence has a narrow job: confirm that the qualifying interval elapsed. LifeQuest does not turn that record into a broader claim about attention, learning quality, or character.
That narrowness makes the reward more credible. The system asks the evidence to support only what it can support.
The same separation applies elsewhere in LifeQuest. A form-coaching video can produce asynchronous feedback about exercise or craft technique, including cues and concerns, but it cannot award XP or serve as quest proof. Coaching and completion answer different questions, so the product keeps them apart.
The moment Lena returns
Lena finds a wall outlet, gives her phone enough charge to restart, and opens the focus screen again. The session record is still there. LifeQuest shows that time passed while she was away rather than inventing a pause that never reached the server.
Once the server-recorded interval meets the quest requirement and she finishes the session, the full-XP reward has a defensible basis. The celebration marks verified completion, not the survival of a local animation.
Her notes still need work. The seminar has not become easier. But the hour she spent at that library table remains attached to a record her dead battery could not erase.
For your next focus quest, start the server-timed session before putting the phone down. Then let the visible countdown do its proper job: show the time, while the server records it.
Comments
No comments yet.