Food-to-sleep observation set / Source cutoff 28 September 2026

22 days, 22 following nights.

Dinner and later intake, movement modality, reported bedtime and next-morning Garmin outcomes are linked by date. This is a descriptive n=1 record, not an intervention result.

22

Linked observations

21

Detailed sleep outcomes

20

Valid reported bedtimes

Current reading

Twenty-one observations have a Garmin Sleep Score (mean 67.7, median 71, range 45–83). The 21 nights with detailed records averaged 379 minutes (6:19); 17 of 21 were shorter than seven hours. Sleep duration remains the clearest recurring constraint in the active series. These are descriptive device readings, not a diagnosis or personal sleep-need estimate.

The timing question remains unresolved. Among the 17 observations with both an unambiguous final-calorie time and a reported bedtime, the food-to-bed interval had essentially no linear association with Garmin Sleep Score (r = 0.01) or total sleep time (r = 0.02). Reported bedtime is not verified sleep onset, and meal composition, activity and other context vary, so this does not rule out a timing effect under more controlled comparisons.

The September 26 San Jacinto exposure produced the most disrupted multi-metric night in the current detailed series: score 45, total sleep 5:05, awake time 3:53, HRV 24 ms, average overnight heart rate 68 bpm and Body Battery change +9. The following recovery night rebounded to score 71, sleep 6:25, awake time 16 minutes, HRV 37 ms, overnight heart rate 61 bpm and Body Battery +55. This is a recovery-trajectory candidate, not a causal hike effect: the acute night was confounded by an unusual elevated-leg sleeping position, and two other long hikes in this series did not reproduce the crash.

Food observations: hypotheses, not rankings

The meal record is still heterogeneous, so these are descriptive component-level checks, not food effects. Crude means below are unadjusted for activity, bedtime, prior sleep or co-occurring foods. The purpose is to identify what deserves a matched repeat—and what currently looks like a false lead.

ExposureCurrent recordDescriptive patternStatus / next test
Grapes11 scored nightsScores 47–83; crude mean 69.6 versus 67.7 overall. High and low outcomes both occur across different activity contexts.Working hypothesis: at the observed portions, grapes are not a dominant driver of sleep outcome. Continue within-modality comparisons.
Orange / citrus6 exposures; 5 scored nightsScores 54–79; crude mean 67.8, essentially the same as the full scored series.Unresolved / no directional signal. Keep recording final-fruit exposures and compare similar rest or low-load days.
Quinoa-containing meals12 exposures; 11 scored nightsScores 47–83; crude mean 68.6. This common meal base spans nearly the full outcome range.Background candidate: useful as a recurring dietary backdrop rather than a current explanatory variable.
Mooncake3 exposures; 2 scored nightsThe two scored late-mooncake nights were 75 and 83; the newest half-mooncake exposure lacks a Sleep Score.Counterexample only: the record does not support “late mooncake always worsens sleep,” but it does not support a benefit either.
Pork / char siu7 exposures; 6 scored nightsCrude scored-night mean is 62.2 versus 69.9 on non-pork nights. But two low pork nights also carried major competing exposures: late popcorn after a hike and the San Jacinto/high-fragmentation night.False lead for now: removing those two confounded nights raises the pork-night mean to 70.3. Do not treat pork as a current adverse signal; collect matched repeats.
Alcohol1 natural exposureThe sake night scored 46 with HRV 25 ms, RHR 60 bpm and Body Battery +34, followed by a rebound night.Single perturbation: strongest food-related one-night disturbance so far, but not a replicated result. Observe natural recurrence only; do not manufacture an exposure.

Current food-layer conclusion: no food has earned a “sleep-promoting” or “sleep-disrupting” label. The most useful early result is narrower: several recurring foods span both good and poor nights, while an apparent pork signal fails a simple sensitivity check. That shifts the next phase toward matched comparisons rather than rankings.

Evidence register

QuestionStatusCurrent evidenceNext informative comparison
Sleep durationRepeated descriptive pattern17 of 21 detailed nights under seven hours; mean 6:19.Capture sleep opportunity and wake time consistently on comparable days.
Food-to-bed timingUnresolved17 paired intervals; r=0.01 with Sleep Score and r=0.02 with total sleep.Accumulate nights with similar activity and meal context but naturally different intervals.
Recurring food componentsMixed / unresolvedGrapes, citrus and quinoa-containing meals span broad score ranges; no repeated component shows a stable directional effect. A crude pork signal fails sensitivity to two confounded low nights.Use matched activity/timing contexts and repeated component exposures before assigning direction.
High-load recoverySingle observation, confoundedSan Jacinto night showed a broad acute disturbance followed by next-night rebound; other long hikes were materially different.Repeat a high-load hike with normal sleeping position and complete timing data.

Observation ledger

The dates below are the sleep dates. A dash means the value was not recorded, not zero. Observation 1 has a score but no detailed sleep record or bedtime; observation 20 has detailed sleep metrics but no reported bedtime or Sleep Score. Download the 22-row CSV snapshot for food descriptions, documentation quality, activity dose, notes and source values. The master workbook retains additional Garmin fields.

Sleep dateDay activityLast caloriesBedtimeScoreSleep h:mmHRV msRHR bpm
09-05Unrecorded18:45—69———
09-06Hike19:0023:00726:063458
09-07Rest19:1523:30707:054254
09-08Rest19:1022:20816:594456
09-09Rucking—22:38465:552560
09-10Run18:3022:38776:074054
09-11Run18:3023:22545:164651
09-12Hike18:5000:10636:044453
09-15Rest—23:48687:505655
09-16Ruck18:5022:51747:453560
09-17Walk21:0022:38756:033957
09-18Run19:0023:25516:023555
09-19Hike—23:08826:464255
09-20Rest19:0022:24516:203855
09-21Hike21:0023:21475:073956
09-22Walk19:0022:41836:404754
09-23Ruck18:4022:53806:394054
09-24Run20:3022:55837:094052
09-25Rest18:3023:15795:404751
09-26Rest19:00——5:363956
09-27Hike18:4521:30455:052458
09-28Recovery19:1522:30716:253755

Questions the next observations should test

  1. Duration and opportunity: when bedtime and wake opportunity are comparable, what repeatedly distinguishes nights above and below seven recorded hours?
  2. Food components: on matched rest or low-load days, do repeated grapes, citrus, protein type or dessert exposures show a stable effect that survives counterexamples?
  3. Timing: does a food-to-bed interval signal emerge within comparable activity and meal contexts rather than across the pooled series?
  4. Movement dose: why did the San Jacinto response differ from other 12–13 mile hikes, and does duration, elevation gain, heat, recovery state or another recorded factor repeat?
  5. Recovery trajectory: does a high-load stimulus repeatedly produce an acute autonomic cost followed by a next-night rebound when sleep conditions are normal?

Sources and limits

Source: Sleepgenic_Food_to_Sleep_Master_Log_2026-09-28.xlsx, Master Log, observations 1–22. Date of this release update: 28 September 2026. Historical comparison: separate Sleep Data.xlsx baseline workbook; it is not added to these 22 observations. Three final caloric cutoffs and two bedtimes are missing; one of those bedtime-missing observations also lacks a Sleep Score. Photo-derived food descriptions can be uncertain and activity dose is incomplete on some days. Bedtime is reported time in bed, not verified sleep onset. Garmin stages are estimates. Correlations are exploratory Pearson correlations across available paired observations, with no missing values imputed.

Read the research method · Read the superseded ten-night interim report.