PTENES
MODULE 3.1

🌅 The daily routine

The heart of daily use: the morning review guided by the recovery, the logic of gating (green/amber/red), the slash commands for the day, and how yesterday’s choice becomes today’s number.

7
Topics
~35
Minutes
Practical
Level
Use
Type
Your progress in this module 0% · 0 of 7
1

🌅 The recovery-led morning check-in

Every day starts the same way: at 07:00 the coach triggers the morning review and the first thing it tells you is how you recovered the night before. “Recovery-led” means exactly that — the recovery score comes first, and the day’s plan adjusts to it, not the other way around. And it doesn’t stop at the score: it connects today’s recovery to yesterday's choices (food, caffeine, workouts, alcohol).

🟣 Three words before you continue

  • Recovery — the wearable’s recovery score (0–100%), a reading of how ready your body is today. It comes from last night’s sleep + heart rate variability.
  • HRV — heart rate variability; it rises when you’re rested and drops with stress/alcohol/poor sleep.
  • Recovery-led — “recovery-guided”: the day starts with the recovery score, and everything (workout, coffee, food) is decided based on it.

The day’s cycle is complete: the morning starts with recovery, you make choices, everything is recorded, and the next morning’s recovery reflects those choices. This is the loop that teaches your own buttons. The numbers below are illustrative (fictional) — not advice.

🌅 morning (07:00)recovery starts the day ☀️ choicescoffee, exercise, food 📝 logeverything becomes a row in the database 🌄 morning +1recovery reflects yesterday the loop closes: the +1 morning becomes the new recovery-guided review

📊 How to read: follow from left to right—the retrieval opens the day (purple), the choices and logging happen in the middle (cyan), and the dashed line closes the cycle: the next morning is already the new review. That’s the circle that turns choice into learning.

Example · 07:00 "Recovery 71% (green), slept 7h20, HRV 64, RHR 52. Yesterday’s protein hit the target and coffee was early and modest — that clean night is why you’re in the green. Today is a push day; have carbs around your workout. Morning weight? Any blood pressure?" (illustrative numbers)

Key concepts

Recovery first

The evening number starts the day.

Links yesterday

Explain why today's number is what it is.

Daily loop

Morning → choices → log → morning +1.

07:00

The check-in runs on a schedule.

2

🚦 The gating logic

Gating is “let it pass through a gate.” The day’s plan stays gated on the recovery score: the same question (“hard workout today?”) gets different answers depending on the color. Green gives the go-ahead, amber urges caution, red says no. The thresholds below are illustrative — your coach uses your own ranges.

recovery for the daythe gate decides 🟢 green · ~67%+push — hard workout, carbs around the workout 🟡 amber · ~34–66%go easy — smaller volume, protein/fiber 🔴 red · <~34%rest—mobility, hydrate, sleep plan for the daygated by the number illustrative ranges — the coach uses your own and never pushes you into a workout that recovery doesn’t call for

📊 How to read: the recovery number (purple) enters on the left and is routed to one of three colors based on the range; each color already carries the action (push / take it easy / rest), and all three lead to the same daily plan — just at different intensities. This is the "gate" in action.

🟢 Green — pull

Body ready. Hard training day: intensity and carbs around your session. The coach gives the green light, but reminds you of the limit.

🟡 Amber — take it easy

Partial recovery. Reduce volume, focus on technique, prioritize protein, fiber, and hydration.

🔴 Red — rest

Your body is asking for a break. Gentle mobility, hydration, and an early bedtime. The coach taps the brakes, not the accelerator.

💡 Why gated is better than “average”

A generic app gives you the same workout every day. HealthOS adjusts the plan to your actual state: push when you have room, pull back when you don't. This helps you avoid digging yourself into a fatigue hole — and teaches you that recovery isn't luck; it's a consequence of your choices.

Key concepts

Gating

The plan passes through the number's gate.

Three colors

Green draws you in, amber holds your attention, red lets you rest.

Your ranges

Thresholds are personal, not fixed.

No gaps

Backing off in time prevents fatigue from building up.

3

⌨️ /checkin /today /sofar /newday

Four commands cover the whole day. They appear in Telegram’s "/" menu (along with /supplements e /advice). Each one is a shortcut that triggers an agent turn with a specific focus.

🌅

/checkin — the morning review

Runs the recovery-led review on demand: brings in overnight recovery, connects it to yesterday’s choices, and suggests the day’s tone. It’s the same turn the 07:00 schedule triggers — useful to run again when the wearable syncs late.

📋

/today — today’s plan

Shows the plan gated by recovery: workout, food, and focus for the day already adjusted to the color (green = push, red = take it easy). It’s the “what should I do today?” based on your number.

📊

/sofar — what’s happened so far today

A summary of the day so far: what you ate, caffeine, workout, and how much you still need to meet your goals. Useful in the afternoon when deciding what to have for dinner ("I still need X grams of protein").

🌙

/newday — wrap up and start a new day

Closes out the day: saves the coach_summary with the recovery and the cause, and resets the context for the next day. That's what makes the story accumulate (detailed in topic 6).

▶️ Copy and run: use it in your Telegram

Goal: see all four commands working. You type the line from the block into the bot chat; the expected response is right below each one. (Illustrative responses — fictional numbers.)

1 · Trigger the morning review

/checkin

How to verify: it responds by opening with last night's recovery—something like "Recovery 71% (green)... yesterday’s protein hit the target, coffee was early: that’s why you’re in the green. Today is a push day."

2 · Request the day’s plan (gated)

/today

How to verify: the plan is visibly conditioned on the color — in green, "hard workout, carbs around the workout"; in red, "light mobility, focus on sleep". If recovery changes, the /today changes along with it.

3 · See the day’s totals (replace with your actual context)

/sofar
<ou descreva: "já comi ovos e frango, treinei pernas, 2 cafés">

How to verify: it adds up what's been logged today and says what's missing— "~120g protein so far, ~40g left to reach the target; caffeine within the limit."

4 · Wrap up the day

/newday

How to verify: it confirms the closeout and saves the summary— "Day wrapped. Recovery 71%, likely cause: a clean night + protein on target. Logged." Next /checkin it already remembers that.

Key concepts

/checkin

Opens the day through recovery.

/today

Plan gated by the color of the day.

/sofar

What’s accumulated and what’s left.

/newday

Closes out the day and saves the summary.

4

🔗 Yesterday → today: the choice becomes a number

What makes the morning useful isn’t the standalone number; it’s the linkage: the coach reads today’s recovery and explains it using what you logged yesterday. Since everything became a row in the database (food, caffeine, workout, alcohol), it can tell you the reason — not just what. That’s how you learn your triggers.

✗ Number without a cause

  • ✗"Recovery 48% today." — so what? There’s nothing you can do.
  • ✗Without connecting it to yesterday, it becomes just another chart app.
  • ✗You don’t learn what affected the result.

✓ Number with a linked cause

  • ✓"48% (amber) — the wine and late dinner are the likely cause."
  • ✓Links to yesterday’s entry: alcohol at 9 p.m., meal at 10:30 p.m.
  • ✓Turns into a lesson: "eating dinner late disrupts your sleep."

🧵 The three-step connection

  1. Reads today: the recovery your wearable measured last night.
  2. Cross-reference yesterday: the food, caffeine, workout, and alcohol entries recorded the day before.
  3. Assigns the likely cause: "what most likely pushed this number up/down" — always as a hypothesis, not a certainty.

📈 Why it becomes the default

Repeated over weeks, the connection stops being a guess and becomes a trend: "every time you eat dinner after 10 p.m., recovery drops ~15%". That’s the leap from memory from HealthOS—we'll cover how it works in module 3.3.

Key concepts

Linking

Links today’s number to yesterday’s.

Likely cause

Hypothesis, not certainty.

Becomes a pattern

Weeks of data = a trend.

Your buttons

You learn what moves your body.

5

☕ "Coffee now?"

The classic question shows specificity in the smallest format possible. A generic bot answers "avoid it after 2 p.m." HealthOS cross-references three things: your recovery today, the time of day, and your caffeine gene. The response is tailored to you.

🟣 The caffeine gene

CYP1A2 is the gene that controls how quickly your liver breaks down caffeine. Fast metabolizers tolerate coffee later in the day; slow metabolizers feel its effects for more hours and should cut it off earlier. The coach uses your variant to set the limit and timing—an illustrative example; check with your doctor.

Coffee now? ☕
You are green and it's 1:00 PM—you can. You metabolize caffeine quick (CYP1A2), so early coffee works well; just stay below your limit and mid-afternoon cut to avoid compromising sleep. (illustrative)
What if it were 5:00 PM?
I’d hold off then. Even if you metabolize it quickly, 5:00 PM is close to your sleep window—and today you want to protect your recovery. Have some tea or water instead. (illustrative)

💡 The same question, three inputs

Recovery (today’s state) + time of day (the sleep window) + gene (your metabolism speed) = a response that changes with context. Change the time, and the response changes. That’s “mechanism-aware” in the smallest example in the course.

Key concepts

Three inputs

Recovery + time + gene.

CYP1A2

How quickly you break down caffeine.

Limit + time

How much and until what time.

Context rules

The time changed, so the answer changed.

6

🌙 Close out the day (/newday)

O /newday is what makes the history builds up. At the end of the day, the coach records a coach_summary: that day’s recovery and the probable cause. This summary is short on purpose — it’s what the agent rereads later to spot patterns without having to load every message.

🟣 What is coach_summary

A summary row for the day in the database: date, recovery, and the cause the coach attributed to it (e.g., "71%, restful night + protein goal met"). It persists even if the rest of the day’s context is cleared—this is the long-term memory that, accumulated day after day, becomes a trend.

✓ What persists

  • ✓O coach_summary: recovery + the day’s cause.
  • ✓All the rows already recorded (food, workouts, vitals) stay in the database.
  • ✓Your goals and profile — they don't change when the day turns over.

↺ What resets

  • ↺The “context for the day” (today’s intake, focus for the day) resets.
  • ↺The next /checkin starts from scratch — but remembers past summaries.
  • ↺Nothing is lost: resetting the day doesn't erase the history.
Example · 23:00 /newday → "Day wrapped up. Recovery 71%, likely cause: a clean night + protein on target. Saved to history. Get some rest — tomorrow I’ll start you off with this." (illustrative)

Key concepts

coach_summary

Recovery + cause, in one line.

Persists

The story doesn’t disappear when the day ends.

Reset the context

The new day starts fresh.

Accumulates

Summary + summary = trend.

7

💬 Conversation best practices

The coach is only as good as what goes in. Three habits make the difference between a dead diary and a system that knows you: log right away, be specific e let the coach hold you accountable.

✓ Do it

  • ✓Log it right away. Take a photo of your food when you eat and your coffee when you drink it — your memory fails later, and the number has no context.
  • ✓Be specific. "200 g steak and a glass of wine at 9 p.m." is worth more than "I had dinner."
  • ✓Let the coach be "savage". Configured to push you on purpose — polite reminders don’t work for everyone.

✗ Avoid

  • ✗Log everything at night from memory — you lose times and quantities.
  • ✗Vague messages (“I ate well today”) — the coach can’t tie anything together.
  • ✗Treat the suggestion as a medical order — it's a hypothesis to discuss with your clinician.

🟣 What is “savage”

A deliberately configured tone that holds you accountable: instead of "you might want to log this," the coach insists ("where’s your check-in? you’ve been gone for 2 days"). The author says they switched to this tone because they didn’t respond to polite reminders. It’s a personality option from the prompt—adjust it to what works for you.

⚠️ A reminder that applies to everything

Everything here is educational and illustrative, with fictional numbers. This is not medical advice. The coach can be wrong; treat every suggestion as a question for your doctor, never as a prescription.

✅ Self-check (optional): in the gating logic, what does one day mean red?

📋 Module summary

✓
The morning starts with recovery — recovery-led: the night’s number comes first, and the day adjusts to it.
✓
Three-color gating — green means go, amber means hold, red means rest; the plan is gated by the number.
✓
Four commands cover the day — /checkin opens, /today plans, /sofar shows the running total, /newday closes.
✓
Yesterday explains today — the logged choice becomes the likely cause of tomorrow’s number.
✓
Closing builds the history — coach_summary stores recovery + cause; logging promptly and being specific feeds everything.

Next module:

3.2 — Food and workouts by photo: log meals and sessions by sending an image, and how vision estimates macros.