Deficit adherence
—
Weekly coach report
A plain summary of your visible data — not medical advice, and thin data means lower confidence, not causation. Generated through 2026-08-20 · current week · deterministic.
Deficit adherence
—
Complete balance days
0/4
Logged intake days
0/4
Sleep days
0/4
No days had both calories burned and logged intake, so deficit adherence could not be evaluated.
| Date | Out | In | Balance | Status |
|---|---|---|---|---|
| 2026-08-17 | 2,034 kcal | — | — | missing intake |
| 2026-08-18 | 2,034 kcal | — | — | missing intake |
| 2026-08-19 | 2,034 kcal | — | — | missing intake |
| 2026-08-20 | 171 kcal | — | — | missing intake |
Logged intake appeared on 0/4 days, which is not enough for a reliable weekly intake trend.
Avg calories out
1,568 kcal
Avg calories in
—
Trend
insufficient data
No sleep logs were found for this window.
4/4 days had daily activity metrics. Activity logs added 0 provider session rows and 0 app session rows.
Readiness context was derived for 4/4 days from the existing Today Snapshot heuristic.
No provider food logs were found for this window.
No manual logs were found for this window.
AI estimate rows visible through Today Snapshot: 0; unconfirmed estimate rows: 0. Estimates are not treated as truth until confirmed/corrected.
Only 0/4 days had both burn and intake data. Prioritize confirming intake and keeping sync fresh before judging the deficit goal.
Grounded in: completeCalorieBalanceDays=0 · daysExpected=4
Logged intake appeared on 0/4 days. Add a quick end-of-day food check so sparse logs do not look like low intake.
Grounded in: intakeDays=0 · foodLogs=0 · manualLogs=0
Sleep was available on 0/4 days. Treat missing nights as unknown rather than good or bad recovery.
Grounded in: sleepDays=0 · daysExpected=4
Only 0 provider activity rows and 0 app sessions were visible. Put two easy sessions on the calendar so next week has clearer activity signal.
Grounded in: activityLogs=0 · activitySessions=0