Why stack recipes Most wellness “stacks” are one‑size‑fits‑all. You end up with more subscriptions, more noise, and no clarity on what changes what. Stack Recipes give you a minimal, time‑boxed combo of devices, signals, and habits aimed at a specific mystery, so you learn quickly and avoid overwhelm.
What makes a good recipe Solves one concrete question (e.g., "Why do I crash mid‑afternoon?") Minimal devices and signals (start small, expand only if needed) Clear timeframe and review cadence (2–6 weeks) Safe defaults: least‑privilege data scopes, revocable shares
How it works (3 steps) Pick a mystery — Sleep drag, afternoon crash, glucose spikes, plateaued training, jet lag, brain fog.Pick a recipe — Prebuilt combos (devices + annotations + habits) with a recommended timeframe and checkpoints.Run it — Context guides setup, captures context, and shows Then‑vs‑Now results.
Outputs Annotated timeline and a short insight (how [habit] affected [data track])
Core recipe categories Metabolic clarity — CGM + meals + movement + sleep Late‑Meal Shift (14 days): move dinner 60–90 min earlier; watch spikes and sleep. Walk‑After‑Meals (10 days): 10–15 min walks post‑meal; compare crash frequency. Sleep & recovery — HRV/RHR + evening routine + light Evening Wind‑Down (14 days): screens down, dim lights, last caffeine 8h pre‑bed. HRV Rescue (10 days): two low‑stim evenings before long training/launch. Focus & energy — Focus Sessions + calendar + tags Morning Monotask (10 days): two 45‑min blocks before noon; track interruptions. Commute Shift (14 days): swap late‑night work for AM commute reading/light. Training & endurance — HRV + training load + protein Protein Floor (21 days): minimum grams/day; see recovery and session quality. Long‑Run Buffer (14 days): schedule buffers before/after; compare HRV dips. Travel resilience — Time zone + light + meal timing Jet Lag Plan (7–10 days): AM outdoor light + earlier local meals; track rebound. Social Nights Guardrails (10 days): cap back‑to‑back late nights; watch next‑day energy. What success looks like “Moving dinner earlier cut my overnight spikes; sleep regularity improved within a week.” “Two low‑stim evenings before my long run stopped the usual HRV crash.” “Morning monotask blocks doubled deep‑work hours; interruptions dropped 30%.” What you get Prebuilt recipes with minimal scopes and clear stepsChecklists & templates (what to track, when to reflect)Then‑vs‑Now comparisons and short auto‑summaries
Privacy & control Recipes use least‑privilege defaults. You decide what to connect, what to share, and for how long and you can revoke with one tap.
Generate your starter stack
Step 1: Name Your Mystery or Goal
Step 2: Choose devices you already own
Step 3: Set timeframe (10–21 days) and checkpoints
Step 4: Start → Context creates the view, templates, and reminders]
FAQ Do I need to buy some wearable devices? No. Recipes adapt to what you already have. They’re designed to start minimal.
What if nothing changes? That’s a result. The summary suggests a next iteration (different lever, longer window).
Will this replace my training or nutrition app? No. Context is the OS layer that unifies your data and experiments across apps.
