Product Journey
The product journey is a controlled loop. Onboarding provides context; it does not attempt to infer today's priority indefinitely. Meaningful use begins when stable context, current state and outcome feedback are connected.
Establish context
Onboarding captures goals, routine, training and nutrition patterns, available capacity, constraints, preferences and relevant physical context. Questions are limited to information that changes scoring, branching or recommendation eligibility.
Add today's state
Before the first Dashboard analysis, the user completes a Check-in covering signals that can change quickly: recent sleep, stress, energy, soreness, food and fluid intake, focus, workload, planned training and immediate priorities.
Select the current constraint
RBD compares current signals with the user's own baseline, checks data recency and safety boundaries, and ranks plausible debts by evidence, causal importance, severity, goal relevance, urgency, actionability and expected benefit.
Present a disciplined output
The normal result is one primary debt, an optional secondary contributor, the supporting evidence, one proportionate action and one method of verifying whether it helped.
Act within real capacity
The action is capped by available time, environment, equipment, limitations and tolerance for difficulty. It should be executable now, not merely correct in theory.
Verify and correct
At the next relevant Check-in, RBD asks whether the action was completed, whether it helped, whether the priority felt accurate and what prevented completion. A disagreement is evidence, not disobedience.
Calibrate over time
The first seven completed Check-ins refine starting estimates. They do not need to be consecutive, and seven entries do not guarantee high confidence for every signal. Calibration continues as patterns accumulate.
Refresh when context changes
Travel, illness, a new work pattern, changed training volume, injury, altered diet or a new objective can invalidate old assumptions. RBD should request a focused baseline update rather than rely quietly on stale information.
Calibration is not a countdown to certainty
Seven Check-ins improve the reference point; they do not make every conclusion reliable. Confidence should remain specific to the debt, the evidence and the current time window.
What maturity looks like
With continued use, RBD should ask fewer unnecessary questions, explain repeated priorities more clearly, avoid actions that have failed for the user and distinguish a persistent real constraint from a stale model.
Journey standard. The loop is complete only when a recommendation produces new evidence. An action without verification is advice; an action with verification becomes part of the decision system.