The Square Canister That Had to Work, and What Accepted Evidence Must Prove

Your first LifeQuest can earn full XP when you choose a verification method that genuinely fits the work and that method succeeds. Create one real quest, complete it, and let accepted evidence move the skill tree you are building, free.

In 1970, the Apollo 13 crew faced a problem with no ready-made part: the lunar module had square carbon-dioxide canisters, while the command module used round ones. Engineers at Mission Control in Houston had to devise an adapter from materials already aboard the spacecraft. The crew used that improvised solution, and NASA brought Jim Lovell, Fred Haise, and Jack Swigert home safely.

The point was never to make the crew perform for a scoreboard. The evidence had to match the problem. A square canister needed a workable connection to a round opening, and the solution had to function in the capsule.

LifeQuest asks for the same kind of fit at a much smaller scale. A coding quest can be verified by a qualifying public GitHub push made after the quest exists. A focused study session can earn full XP from elapsed server time. A physical or craft result can be submitted through the in-app camera for AI plausibility review. Pick the method that can actually support the claim.

Make the challenge about one completed thing

For your reel, start with a quest that has a clear finish line. “Write and push the first version of my portfolio site” works. “Study harder” gives you nothing concrete to verify.

Choose a skill in Body, Craft, Social, or Mind, then create a quest you can complete in one sitting or one day. Keep the camera on the small decisions: naming the quest, choosing the applicable verification path, doing the work, then returning to LifeQuest when the work is done.

That structure matters because disconnected XP loses meaning quickly. A growing number alone cannot tell you what you did to earn it. A quest attached to evidence can. The rank, streak, skill tree, title, and badge become a record of work you can point to.

If your quest is coding, make the timing visible in the reel. Create the quest first, then make the qualifying public push afterward. Old GitHub activity cannot prove a new quest. For a fuller walkthrough of that rule, see What Happens When Your Coding Quest Ends With a Public GitHub Push?.

Show the verification method that fits the work

A useful reel does not pretend every quest can be proved the same way. That is the whole challenge.

For a focus quest, start a server-timed focus session before you begin. The on-screen countdown helps you see the session, but the XP comes from the server’s recorded elapsed time. If you leave the app, the session keeps counting honestly rather than quietly pausing on your device. The Countdown That Cannot Earn Full XP, and What the Server Clock Changes explains why that distinction matters.

For a physical result or craft task, submit a fresh in-app camera photo when the quest is complete. The photo goes through AI plausibility review. Accepted evidence earns full XP. Rejected proof does not consume a photo-review allowance, and it does not mean the work never happened. It means that proof could not support full XP.

For a quest where objective proof does not make sense, use honest self-report and receive half XP. LifeQuest keeps that path open because real progress sometimes has no clean artifact. Form coaching is separate: its short video feedback can offer cues and concerns, but it cannot pose as quest proof.

Let the accepted result be the reveal

The strongest moment in the reel comes after the evidence is accepted. Show the completed quest, the full-XP celebration, and the skill tree changing in the domain where the work belongs. Then open the rank ladder for a second. Viewers should see that XP has a destination: E-to-S domain ranks, cosmetic titles, badges, and a visible history of effort.

Do not rush past the wait if your evidence is reviewed asynchronously. That wait is part of the story. Apollo 13’s improvised adapter mattered because it had to work under the conditions the crew actually faced. Your verification should have the same standard: evidence connected to the specific quest, not a generic completion checkbox.

A 20-second reel can make the sequence clear:

• Create one specific quest.
• Complete the real work.
• Use the verification method that applies.
• Show the accepted result moving your skill tree.

Complete the first quest before asking for a streak

Streaks are easier to care about after the first entry has weight. Start with one quest you can finish today: one focused study block, one piece of code pushed after the quest is created, or one visible result captured in the app’s camera.

LifeQuest’s core loop is free, including unlimited goals and quests, self-report, focus and GitHub verification, XP, streaks, skill trees, ranks, learning resources, and notifications. The free plan also includes 10 accepted AI photo reviews and one successful form-coaching review each month.

Film the proof that fits your first quest. Then let the accepted evidence do the talking.