Symptom trend summary
Recovery
+22
Change from first check-in to latest entry. Direction does not prove cause.
Tracking dashboard
A protocol journal for symptoms, recovery markers, and result trajectory. The product logic keeps uncertainty visible while helping users organize observations.
04
Weekly snapshots
03
Tracked trendlines
1
Uncertainty-first dashboard
Active protocol
The dashboard shows how protocol events, check-ins, and proof context can stay connected over time.
Protocol selector
Injury recovery
Frequently paired in public recovery discussions, but evidence remains uneven and product quality is central.
Avoid treating a stack mention as protocol guidance.
Verify each compound and vendor independently.
Trendlines
Check-in data keeps cause, correlation, and proof quality separate.
Symptom trend summary
+22
Change from first check-in to latest entry. Direction does not prove cause.
Symptom trend summary
+13
Change from first check-in to latest entry. Direction does not prove cause.
Symptom trend summary
-26
Change from first check-in to latest entry. Direction does not prove cause.
Timeline
1
Week 1
Baseline
2
Week 2
Low signal
3
Week 3
Watch
4
Week 4
Trend forming
Week 1
Baseline
Baseline entry before enough signal exists.
Week 2
Low signal
Some improvement, still too early to attribute.
Week 3
Watch
Trend may be forming; training load context still needed.
Week 4
Trend forming
Directional improvement, still not causal proof.
Track what changed, when it changed, and what else was happening at the same time.
Keep vendor, COA, and evidence tier attached to the observation record.
Look for patterns while keeping placebo, training, sleep, and diet context visible.
Log entry preview
Tracking is most useful when product proof and symptom context travel together.
Attach product proof