LifeQuest awards full XP for a focus session from elapsed time measured by its server, rather than from a countdown running on the student’s phone. That shared clock gives the session a record outside the device whose settings, connection, and attention can change mid-quest.
A shared clock solved a worldwide argument
In Washington, D.C., in 1884, delegates gathered for the International Meridian Conference to settle a problem that had become hard to ignore: places were using different local times, while railways, shipping, and telegraphs increasingly needed a common reference.
The outcome was not automatic. Countries had their own meridians and reasons to keep them. Sir Sandford Fleming had argued for a more coordinated approach to timekeeping, but the conference still had to decide what reference the world could use together. The delegates selected the meridian at Greenwich, England, as the starting point for a universal day. France and Brazil abstained; the decision had real disagreement behind it.
Royal Museums Greenwich documents the conference and its role in establishing the Greenwich meridian as an international reference. The point was never that every clock in every town would behave perfectly. The point was that people coordinating across distance needed one clock they could all refer back to.
A focus session has the same smaller-scale problem. Your phone can show a countdown. It can freeze in the background, lose its connection, have its system clock changed, or simply sit on a desk while your attention moves somewhere else. A timer visible on your screen is useful feedback, but it is weak evidence on its own.
The countdown is for you. The elapsed time is for the quest.
When you start a LifeQuest focus session, the server records when it began. When you finish, the server measures the elapsed time from that server-issued start time. The countdown in the app helps you pace yourself. It does not decide whether full XP is earned.
That distinction matters because LifeQuest is built around evidence-weighted progress. A self-report remains available when you did the work but cannot offer objective proof. It earns half XP, honestly reflecting what the system can verify. A server-timed session can earn full XP because the measurement comes from a reference the student does not control.
This is not a claim that a timer can see inside your study session. It cannot prove you understood the statistics chapter, wrote a strong draft, or kept your phone out of reach for every minute. It can establish one narrower fact: a session started, time passed according to the server, and the session was finished through that record.
Narrow evidence is still useful evidence. It avoids asking one generic completion checkbox to carry more certainty than it has earned.
Leaving the app does not pause the clock
Focus rarely happens in a perfectly sealed room. Someone knocks. You open a reference. The app moves to the background. Your battery dies. Those moments should not produce a fake story about time.
LifeQuest treats the on-screen countdown as cosmetic and the server clock as authoritative. If you reopen the app after leaving it, the session can show that you were away and that the timer did not pause. That may feel stricter than a timer that quietly freezes, yet it protects the meaning of verified full XP for everyone using it.
The alternative creates a strange incentive. If full XP depends on a device-side counter, the product has to trust the same device that can be paused, altered, or left unattended. The record becomes easy to confuse with the work itself.
For a practical example, imagine a 45-minute coding quest. If you start a server-timed focus session and then spend 20 minutes answering messages, the elapsed time still exists. LifeQuest has not certified your concentration. It has credited the kind of evidence the session can actually support. If the time no longer feels like the right proof for the quest, self-report remains the honest fallback.
For a closer look at that tradeoff, read What Happens When You Reopen LifeQuest After Leaving a Focus Session?.
Choose the proof that fits the work
A timer is strongest when time spent is a meaningful part of the quest: a focused reading block, a planned practice session, or protected time for a craft. It is a poor fit when the key outcome is visible in a photo or public in a qualifying GitHub push. LifeQuest lets you choose among the methods that genuinely apply instead of pretending every goal produces the same kind of proof.
That is why form coaching stays separate from quest completion. A 60-second exercise or craft recording can receive asynchronous coaching feedback, cues, and concerns. Helpful feedback is not proof that the whole quest happened. Keeping those records separate prevents an encouraging coaching response from quietly becoming XP evidence.
The delegates in Washington did not make every local clock identical in 1884. They gave distant people a reference point when their own clocks disagreed. LifeQuest uses server time in the same spirit: your phone can guide the session, while the full-XP record comes from a clock that belongs to neither your optimism nor your settings.
Comments
No comments yet.