Health Log Analysis

Trigger

User shares an Amazfit/smartwatch screenshot or workout data and asks for analysis or logging.

Step 1: Extract Everything from the Screenshot

Pull ALL available data, not just summary numbers:

• Summary: distance, time, avg/max pace, avg/max HR, calories
• HR zones: % time in each zone (the Amazfit "Training Effect" screen or HR zone chart)
• Biomechanics: cadence, stride length, vertical oscillation, ground contact time, power
• Environment: temperature, humidity (Amazfit often shows this)
• Splits: per-km pace and HR
• Performance index: real-time performance score if shown
• Training effect: aerobic TE, anaerobic TE, workout balance

Step 2: Read the Health Log

File: wiki/self/health/2026 Health Log.md

Read enough history to identify trends — not just the last 2-3 entries. Look for:

• Weight trajectory (weekly/monthly direction)
• Pace trends for similar distances
• HR trends at similar paces (fitness progression)
• Cadence/stride consistency over time
• Resting HR and HRV trends (recovery readiness)
• Training load patterns (hard/easy balance)
• Any health notes (wheezing episode, injuries, etc.)

Step 3: Analyze Like a Coach

Interpret the data, don't just restate it:

• Cardiac drift: HR climbing while pace stays flat = dehydration or heat stress. Name it when you see it.
• Mechanical consistency: Did cadence/stride hold up across splits? Deterioration = fatigue or poor form under load.
• HR zone distribution: What % of the run was aerobic vs threshold vs VO2? Does this match the intended session type?
• Pace variability: Smooth splits = good economy. Spikes/drops = fatigue points or terrain.
• Performance index trend: Watch's own assessment of fitness relative to baseline.
• Training load context: Where does this sit in the week/month? Overloaded or undertrained?

Step 4: Advice — ONLY if Rooted in Data

The rule: If you can't point to a specific number or trend from his data or health log history, don't give advice.

Good (data-rooted):

• "Your cadence dropped from 160 to 154 — worth watching if it persists over multiple runs"
• "This is your 3rd run in 3 weeks. Your last consistent stretch was Jul 6–29 where you hit 100 km in the month"
• "HR was 131 avg at 10'42" pace. On Jul 28 you ran 10'42" at 144 avg — your aerobic efficiency has improved since then"

Bad (generic):

• "Make sure to stay hydrated"
• "Consider adding interval training"
• "Good job, keep it up!"
• "Don't forget to stretch"

If there's nothing actionable from the data, say so. A clean "this was a solid aerobic session, nothing unusual in the data" is better than padding with generic tips.

Step 5: Log to Health Log

File: wiki/self/health/2026 Health Log.md

August summary table — add row if not already there. Detailed entry — structured with:

• Weight (if provided)
• Activity & Training section with full metrics (skip Location and Device — always the same)
• ### 📊 vs Previous section — structured comparison with previous run of same type:
• Pace: new → old (+/- delta)
• HR: new → old (note if faster pace at same/lower HR)
• Cadence: new → old
• Distance: new → old
• Aerobic TE: new → old
• Brief analysis note grounded in data (replace the old narrative paragraph)

Pitfalls

• Don't assume weather data if it's not in the screenshot
• Don't give nutrition advice unless he has his actual intake data from the log
• Don't compare across different activity types (jog vs walk vs home workout) unless explicitly asked
• Cadence range for Joseph: typically 149-160 spm on jogs. Below 150 = tired or casual pace.
• Joseph's VO2 Max has been stable at 33 — don't treat it as a fitness concern unless it drops
• Weight range: typically 77.3–78.4 kg. Don't flag fluctuations within this range.
• Location and Device are constant (Panchkula, Amazfit Active 2) — never log them.