Running a winery is a long game. Building a brand is a long game. Most owners I work with have spent ten or fifteen years inside the business and plan to spend another twenty. The thing that ends careers in that kind of work is rarely the business. It is the body sending a bill the owner did not see coming. The injury that costs a quarter of harvest. The sleep debt that quietly compounds across two years of long days and surfaces as a heart event in the third. The protein gap during a stretch of travel that turns into a strength loss the GM does not notice until walking the production cellar starts feeling like work.
The Health Team agent is the one that watches the body for you. It does what a trainer, a nutritionist, and a doctor would each do — separately, on their own clocks, with their own data. It runs three scheduled tasks: a silent diet log every night at 10 PM, a weekly health pulse on Sunday evening, and a monthly visit-prep summary before any doctor's appointment on your calendar. The output is never instruction. It is observation. The body has been telling you something. The agent makes sure you read it.
This is the per-agent breakdown for the Health Team in the Agent OS Webinar series. Week eight of the 90-day install order. It is the only agent in the shadow team whose subject is you, not the business.
What the Health Team reads (Inputs)
Four inputs. The agent is quietly data-hungry but most of the data is passive.
- Diet photos. A photo of every meal during the day, taken on your phone, dropped into a shared folder. The agent reads the image and estimates calories, macros, and category. The accuracy is not surgical; the consistency is. Over a month the trend lines are real even if any single day's estimate is rough.
- Training entries. Whatever workout tracking you keep — a Strava feed, a notes-app log, a paper journal you photograph weekly. The agent reads what is there. Lifting, running, cycling, walking, yoga, what was skipped, what was modified.
- Sleep data. From an Oura ring, a Garmin watch, a phone-based sleep tracker, or a manual log. Bedtime, wake time, total sleep, deep sleep, restlessness if measured.
- Doctor appointment calendar. The next preventive visit. The next specialist follow-up. The next bloodwork date. The agent uses these to write a 5-minute visit-prep summary the day before each one.
The inputs are designed so that you do nothing extra in your day. The diet photos are already happening because you photograph meals out of habit. The sleep data is already happening because the watch is on your wrist. The training data is already happening because you log a workout when you finish it. The agent reads what you produce passively and assembles it into a view.
What it does with that material (Skills)
Four skills, sequenced by frequency.
- Diet log analysis. Every night at 10 PM, read the day's meal photos, write a one-line log entry per meal, calculate the day's running totals against your stated goals. The entry goes in a Health folder; you do not need to read it daily.
- Weekly health pulse. Every Sunday evening, read the week's diet log, training data, and sleep data. Compare to the prior 30, 60, and 90 days. Write a one-page brief that names the trend lines in plain language. Where protein went. Where sleep went. Where training went.
- Pattern correlation. When trends move together — a stretch of low sleep correlating with a stretch of low training, or a travel week correlating with a protein gap that is still showing four days after travel ended — the agent surfaces the correlation in the weekly pulse and proposes one observation about it.
- Doctor visit prep. A few days before any preventive or specialist visit, write a one-page summary of the last 90 days of health data plus any open questions you wrote in your daily notes about the body. The summary sits in your daily folder. You bring it to the appointment.
What the Health Team does not do is decide. It does not write your training plan. It does not write your meal plan. It does not make a medical recommendation. The hard rail is the strictest in the shadow team after the Personal CFO. The agent reads, surfaces, and observes. The judgment about what to do is yours, your trainer's, your doctor's.
The schedule (Scheduled Tasks)
Three scheduled tasks, deliberately quiet.
- Daily 10:00 PM, silent. Diet photo analysis. The day's meals are logged, the running totals are updated, the file in the Health folder is current. You do not see it. It accumulates.
- Sunday 8:00 PM weekly. Weekly health pulse. The one-page brief lands in your daily folder, between the Connector's relationship scan at 7:00 and the System Tuner's review at 9:00.
- Two days before any doctor appointment on the calendar. Visit-prep summary. The one-page brief sits in your daily folder, dated for the appointment day.
The 10 PM time matters. The diet photos accumulate during the day. Running the agent before bed catches the day cleanly. Running it the next morning loses the late-evening detail. Silence is also a feature: you do not need to read the daily log every day, you need it to exist so the weekly pulse has data to read.
What lands on your desk (Outputs)
Three outputs. The Health folder grows. Most days you do not look at it.
- The daily diet log. A one-page-per-day file in the Health folder. Running totals, photo links, calculated macros. The agent's eyes only, most of the time.
- The Sunday weekly pulse. One page. Trend lines on protein, sleep, training, weight if you track it. Any pattern correlations the agent caught this week. One observation about what to think about, in one sentence.
- The doctor visit prep. One page, generated two days before the appointment. The data the doctor will ask for, already aggregated. Any questions you have written down in your daily notes about the body, surfaced.
Nothing autonomous goes anywhere. The agent does not message a trainer. It does not auto-add an item to your shopping list. It does not adjust your training plan. The agent's job ends at the file.
The goal: track the body so the body lasts
The Health Team exists for one outcome. Track the body across long enough time horizons that the patterns you would otherwise miss are visible before they become problems. The Compass watches the calendar. The Health Team watches the body. Both run because the CEO inside the calendar cannot watch the calendar, and the person inside the body cannot watch the body.
The second-order effect is sharp but easy to miss. The trend lines are the value. Any one week's diet log is wrong by 200 calories somewhere. Any one night's sleep score is misleading. The patterns across 90 and 180 days are real, and the patterns are what surface in the Sunday pulse and the doctor-visit summary. Owners who run the Health Team for a year report that the second annual physical is a different conversation than the first. The doctor walks in with the year of data. The questions are sharper. The visit is shorter, because the reconstruction is already done.
A worked example, late harvest
Imagine the second half of harvest. You have been on the production floor or in distributor meetings for 12-hour stretches for three weeks. Travel between Sonoma and the East Bay twice a week. The Sunday health pulse drops into your daily folder at 8:00 PM:
Week ending — health pulse.
Sleep dropped to 5.5 hours average this week. Down from a 90-day baseline of 7.1.
Protein intake dropped 30% versus baseline. Two days under 80 grams. The trend started 11 days ago and has not corrected.
Training has been three skipped sessions in a row. The last lift was 13 days ago. The last run was 9 days ago.
Pattern correlation: low sleep is showing up with the protein gap, and the training has fallen off in the same window. The three are reinforcing each other.
One observation: two more weeks of this and the body sends a bill. The single thing that would correct course this week is the protein intake. If you eat to the baseline for the next four days, the sleep usually follows and the training usually resumes on its own.
You read the pulse Sunday night. You make a one-line note to ask your hospitality team to pre-stage protein-forward meals at the tasting room for the next four days. You set Monday morning's alarm for the 30-minute run you keep moving. By Friday, the sleep is back to 7 hours. By the next Sunday's pulse, the trend lines are pointing the other way.
The Health Team did not change anything. It told you, while there was still time to do something about it, that the body was about to send a bill you did not want to receive.
The hard rail: flags only, never modifications
The Health Team's rail is the strictest in the shadow team after the Personal CFO. The agent flags. It does not modify. It does not adjust your training program autonomously. It does not change your nutrition targets without you. It does not send messages to your trainer or your doctor. Health decisions are decisions only humans should make, with the inputs the agent surfaces but with the judgment that humans bring.
The reason is the same as for the Personal CFO. The downside of an autonomous mistake in the health domain is too high. A wrong calorie target shipped autonomously and held for a month is a body-composition problem the agent caused. A flagged trend the owner decides to ignore is the owner's decision. Keeping the agent in the observe-and-flag lane preserves the agency where it belongs.
Why this is week eight of the install order
The Health Team comes eighth because the body is the longest-feedback-loop input in the shadow team. The wholesale-channel data shows up in a week. The wine-club-retention data shows up in 90 days. The body shows up across a year or longer. Installing the Health Team in week eight means the agent starts accumulating data the same week you finally have the calendar bandwidth to read the pulse on Sunday evenings.
Two more reasons:
- The Health Team is the agent that benefits most from the Compass being installed first. Both are descriptive, both are read-only, both are about catching drift before it becomes damage. Owners who have lived with the Compass for a month understand the mode the Health Team operates in. The pattern is the same; the subject is the body instead of the calendar.
- The compounding is the longest in the stack. The first week of pulse reports is rough. The 13th week is sharper. The 26th week is a year of data the agent can read in two pages. The earlier you start, the longer the lookback becomes. Week eight is the latest in the install order I would put it. Earlier is fine.
Build this one in week eight. The webinar recording and the rest of the Agent OS series live at nunncurtislabs.com/webinars.