What Happens When Form Coaching Counts as Quest Proof?

Form coaching and photo proof should stay separate because they answer different questions. A useful AI review of your squat, brushstroke, or guitar grip should never count as evidence that you completed the quest.

A lesson from Coca-Cola’s wrong question

In Atlanta in 1985, Coca-Cola introduced New Coke after taste testing suggested people preferred the new formula. The company had evidence about a narrow question: which drink people liked in a sip-by-sip comparison.

It did not have evidence that people wanted the original Coca-Cola replaced.

The response made that gap painfully clear. Coca-Cola brought back the original formula as Coca-Cola Classic later that year. Mark Pendergrast documents the episode in For God, Country & Coca-Cola: the research result was real, but it was being asked to carry a claim it could not support.

That is the design problem we are trying to avoid in LifeQuest.

A 60-second form clip can give the coach something useful to assess: whether your knees track inward during a squat, whether your wrist position may need attention while drawing, or which movement cue to try next time. It can help you practice better. It cannot establish that you completed the specific quest you created, at the time you said you did.

Those are separate jobs. We keep them separate on purpose.

Coaching should help the next rep

Form coaching in LifeQuest is asynchronous. You record up to 60 seconds of exercise or craft form, submit it for review, and later receive a summary, cues, and concerns. A notification can tell you when that review is ready.

The point is feedback you can use. Maybe you are practicing a push-up variation and want another set of eyes on your setup. Maybe your goal is drawing hands, and you want a cue about how you are holding the pencil or approaching the gesture. The review can be helpful even when the clip does not prove the quest itself.

That distinction makes the feedback easier to trust, too. The coach does not need to pretend it saw everything. It can focus on what is visible in the short clip and give you a next action, without turning every comment into a verdict on your progress.

We also do not present AI coaching as professional instruction. It is a lightweight practice aid, with real limits. If the review flags a concern, that is a cue to slow down and use judgment, not a credential from a trainer, doctor, or teacher.

Proof needs to match the quest

Photo proof has a different role. When objective proof is practical, you can use the in-app camera to submit a photo for AI plausibility review. If the evidence is accepted, the quest earns full XP.

The standard is intentionally narrower. A photo is reviewed as evidence for completion, not as an opportunity for technique coaching. Full XP depends on an accepted proof submission. Rejected proof and failed provider calls do not consume your review allowance, and self-report remains available for half XP when proof does not fit the task.

That last part matters. Plenty of worthwhile quests are hard to prove honestly with a camera. Reading a chapter, making a private phone call, reflecting in a journal, or taking a walk without a distinctive destination may all be real work. For those, self-report is the honest path. The system should not push people into manufacturing evidence for a task that does not naturally leave any.

LifeQuest uses other verification methods where they fit more cleanly. A server-timed focus session measures elapsed time with the server clock. A qualifying GitHub push can verify a coding quest created before the push. Each method is tied to a specific kind of claim.

That is why we built a tier sheet instead of one generic “complete” checkbox. The question is always: what can this method genuinely establish?

For more on the same principle, see The 60-Second Clip That Can Improve Your Form but Cannot Award XP.

Keeping the reward loop honest

It would be tempting to merge these features. A form clip already contains video. AI already reviewed it. Why not award XP?

Because that shortcut would blur the promise of the product. Helpful feedback would start masquerading as completion evidence, and users would have less reason to believe that verified XP means what it says.

New Coke was not a failure of collecting no data. It was a failure of treating one kind of data as an answer to a different question. We want the opposite habit inside LifeQuest: give each signal a clear job, state its limits, and let progress reflect the evidence actually available.

If you want technique feedback, submit a form check and use the cues on your next rep. If your quest has suitable proof, choose photo review, focus time, or GitHub verification. If it does not, take the honest half-XP self-report and keep moving.