A focus session can award full XP only when elapsed time comes from a server-issued start time, rather than a countdown running on your phone. Device counters can pause, reset, or drift; one server record gives the session a consistent beginning and ending.
In April 1970, Apollo 13 lost its planned path after an explosion disabled critical systems on the way to the Moon. Jim Lovell, Jack Swigert, and Fred Haise moved into the Lunar Module Aquarius while Mission Control in Houston worked through the mission’s remaining options.
The crew could not rely on the normal setup they had left behind. Ground teams and astronauts had to coordinate actions around a shared account of where the spacecraft was, what systems remained, and what had already happened. A correction made at the wrong moment could have mattered. Apollo 13 returned safely, but its outcome was uncertain for days. Jim Lovell and Jeffrey Kluger document that tense coordination in Lost Moon.
A focus quest has smaller stakes, thankfully. The principle still holds: progress needs a record that survives interruptions.
A phone countdown only shows one version of events
A countdown on a device is useful for helping you focus. It can show the minutes remaining, play your optional focus loop, and give you something concrete to look at while you work.
It cannot provide a dependable account of elapsed work by itself. The app may be backgrounded. The operating system may interrupt it. A device clock can change. The app can restart. A local timer may continue displaying a familiar number while the underlying session no longer has a clear, trustworthy timeline.
That matters when a focus session earns full XP. LifeQuest treats full XP as evidence-weighted progress. A visible countdown helps the experience, while the server-issued start time anchors the evidence.
When you begin a focus session, the server records when it began. When you finish, the server measures the elapsed time from its own clock. Your device displays that timeline, but it does not get to rewrite it.
One shared start time keeps the session honest
This design protects you from accidental confusion as much as deliberate shortcuts.
Imagine starting a 45-minute focus quest, then receiving a call, closing the app, or losing battery. A device-side counter can leave you wondering what happened: Did it pause? Did it restart? Did those minutes count? A server-timed session has a simpler answer because its start remains fixed.
If you leave the app, the time keeps moving. LifeQuest tells you how long you were away rather than pretending the session paused invisibly. When you return, you can make an honest decision about whether you completed the work.
That shared record also keeps the rules understandable. Full XP comes from elapsed server time. Half XP remains available through honest self-report when the focus session did not meet the requirement. The choice recognizes real work without treating every completion method as equally strong evidence.
For a related example, see The Countdown That Cannot Earn Full XP, and What the Server Clock Changes.
The timer should support focus, not impersonate proof
A server clock does not prove what happened at your desk. It establishes that a focus session ran for the required amount of time under a consistent rule. That is the claim LifeQuest can honestly make.
This distinction is why the timer shown on screen is cosmetic. It reflects the session’s server-issued start instead of becoming the source of truth. The visual timer serves you. The server record supports the XP decision.
LifeQuest also keeps verification methods matched to the quest. A coding quest can use a qualifying GitHub push. A physical task may use in-app photo proof. A focus quest uses elapsed server time. When objective proof does not fit, self-report remains available for half XP.
That structure leaves room for real life. You may finish meaningful work after a disrupted session. You can still record it honestly. You simply do not receive the same evidence weight as a completed, server-timed focus session.
Apollo 13 required everyone involved to work from a shared understanding of a changing situation. Your focus quest deserves a quieter version of the same discipline: one start time, one elapsed record, and no mystery about what the clock counted.
Comments
No comments yet.