Nutrition, food & body

How nutrition works in Ojava

Ojava turns what you eat and how your body is changing into the same kind of plain-language picture it builds for your labs and wearables. You log food (by photo or by hand), Ojava estimates the calories and macros, and it compares your intake to targets it calculates from your own weight, height, age, and activity. Everything you log feeds your dashboard, your trends, and Ojava Coach, so your nutrition sits in the same longitudinal record as the rest of your health.

This is general wellness guidance, the kind a thoughtful coach or a food-tracking app gives you, not medical nutrition therapy. Ojava does not treat a diagnosed condition with a diet and never prescribes a clinical eating plan. For a condition like diabetes or kidney disease, bring these numbers to your clinician or a registered dietitian.

Log a meal from a photo

The fastest way to log a meal is to photograph it. Ojava looks at the picture, returns a full-meal estimate, and, when the plate can be separated responsibly, shows item suggestions you can use instead of the total. You can start a scan from the food log or straight from the Ojava Coach composer (the camera button beside the message box), so you can ask a question about a meal and log it in the same motion.

Food photos are the one category Ojava may use to improve its food-recognition feature. Every other kind of health data, labs, imaging, medications, wearables, and notes, is never used to train any model. See Privacy & your data for the full policy.

Your food log

Fitness is the first tab in the top navigation, and it is the whole nutrition and fitness workspace. The Features panel can open Fitness directly, jump straight to the food quick-add form, or open Calories, Food scanner, Workouts, Water, Fasting log, Meal plan, and Body metrics inside the same tracker. Diet and Exercise still stage Ojava Coach prompts when you want coaching context. Use these shortcuts when you want the food scanner, barcode package lookup, calorie diary, calorie and macro targets, workout log, water log, fasting log, meal planner, and body trends without hunting through Timeline.

The Nutrition Coach entry point is now dedicated too. From the Coach welcome chips, command panel, or Fitness quick actions, choose Nutrition Coach to open the existing Ojava Coach composer with a safe nutrition-assistant prompt staged for review. The Fitness quick action also jumps straight to the Nutrition Coach review panel inside Fitness > Nutrition. It is the same Coach handoff and deterministic nutrition context, not a second chat or a separate AI nutrition pipeline.

Paid Nutrition Chat

The free Nutrition Coach review above remains part of the free experience. A separate, dedicated Nutrition Chat workspace is built as part of the Body Composition Report and Nutrition Chat add-on. Its activation flags are off, so it is not available to buy or open yet. Once activated, it will give paid members a focused conversation about their logged meals, goals, routines, and nutrition patterns. It reuses Ojava’s private record and chat safeguards, but it does not replace the free Nutrition Coach summary and does not provide medical nutrition therapy.

Fitness opens on a diary-style view: calories logged for the selected date, macro totals, meal sections, scan and logging shortcuts, custom nutrient target progress, meal-balance signals from complete macro rows, and a report panel are visible before the detailed entry form. A Progress overview above the tracker tabs also pulls together today’s food and water, weekly active minutes, daily and weekly steps, sleep and recovery context, fasting rhythm, and latest body progress from the same records. Ojava Coach receives the same finished progress overview as wellness context when those rows are present. Ojava also builds private nutrition challenge readiness from the same reviewed rows: food-logging streaks, protein-anchor days, water consistency, completed fasting windows, movement support, and meal-plan follow-through. Fitness > Nutrition shows that private challenge card next to the rest of your food-log review, and the same private packet names candidate challenges, current streaks, recent completed days, and missing inputs before Ojava Coach sees a summary. These are personal adherence prompts that Ojava Coach can read when you ask about consistency. They are not public challenges, leaderboards, friend graphs, social sharing, food scores, prescribed diets, dehydration assessments, fluid prescriptions, diagnoses, treatment, weight-loss treatment, or medical nutrition therapy. Missed-day recovery plan uses that same private rhythm across food, water, workouts, and fasting to notice recent days where tracking dropped off and suggest a few low-pressure reset actions, such as logging the next meal, adding water, restarting a chosen fasting timer, or recording a familiar workout. Ojava Coach can read that reset context when you ask about getting back on track, but it is not an adherence score, diet plan, calorie prescription, fasting prescription, exercise prescription, diagnosis, treatment, medical monitoring, or medical nutrition therapy. When you want outside accountability without exposing your diary, Fitness > Nutrition shows a privacy-safe accountability prep card from those same reviewed patterns. If the packet is still building, it names the missing diary context. Once ready, it uses habit counts and streak context, then includes evidence, missing inputs, a copy action, and a redaction checklist for names, exact dates, locations, contact details, clinician names, medication or supplement details, screenshots, file names, and account identifiers before anything leaves Ojava. Ojava Coach can read the same bounded packet when you ask about accountability. It does not post, send, create a friend graph, match peers, disclose protected health information, score foods, prescribe a diet, or provide medical nutrition therapy. Completed diary days also carry private review-readiness detail: how many entries had calories, complete macros, and meal labels across the day. Ojava Coach can use that quality context to say whether a day is strong, basic, thin, or empty before discussing patterns. It is not an adherence score, calorie prescription, diet plan, diagnosis, treatment, or medical nutrition therapy. Weekly review-readiness uses that same reviewed-day state, then checks whether the week has enough logged food days, basic-or-strong diary detail, body-weight check-ins, and workout or wearable activity context before Coach treats the week as ready for a broader nutrition conversation. If the week is partial, the packet names the missing context first instead of turning the gap into advice. Ojava Coach can also receive a selected-day tracker action summary when the diary day is reviewed or explicitly opened: food entries, calories and macros, water, movement or steps, latest body context, reusable meal-copy shortcuts, missing inputs, and the next best logging action. This is self-tracking context only, not a diet plan, health score, adherence score, diagnosis, treatment, exercise prescription, fasting prescription, or medical nutrition therapy. Reviewed water rows also feed a hydration digest for Coach: recent row count, total and average mL per logged day, same-day total, target or reference context, and missing inputs. When you ask an acute digestive or foodborne-illness prep question, Coach can also receive a request-scoped acute GI nutrition packet from your reviewed food rows, symptom entries, water logs, medication names, and supplement names. It organizes timing context, missing inputs and questions you may choose to bring to an independent clinician. It does not diagnose food poisoning, prove a food caused symptoms, assess dehydration, prescribe fluids or electrolytes, recommend antibiotics or anti-diarrheal medication, order stool tests or labs, detect outbreaks, report to public health, triage emergencies, book urgent care, or replace medical care. The goal is to make everyday food tracking feel immediate instead of buried inside a generic tracker card.

The food log is your running record of what you eat, by photo, label scan, package barcode, voice-style transcript, typed quick log, search, or hand entry. Each entry keeps the food, an estimated calorie and macro breakdown, the diary date, and the time. Photo, label, barcode, and search results stay reviewable before saving, and Ojava Coach can explain that readiness plus the cited food-logging education handoff when you ask how food logging works. You can switch the diary to another date with the date picker, previous and next day controls, or the seven-day strip, then add an entry to that date or edit an existing row without creating a duplicate. The strip marks reviewed days, days with entries, and today so multi-day logging is easier to scan. The log is the raw material every other nutrition feature builds on.

Ojava also offers a public free food-log quality checker for people who are not signed in yet. It is the lightweight, cited prep version of the same idea: enter diary counts and capture methods, then check whether the log has dated meals, serving-size context, source labels, calories that line up with macros, review notes, and clear gaps. The public checker does not read your private Food Log or produce a diet plan. If you sign in afterward, the Coach handoff carries only the quality summary, cited source context, missing inputs, and the question you chose to ask.

For food-log data quality, Ojava also reviews whether declared calories and macros line up closely enough to inspect before you rely on the entry. The check uses the standard education math of 4 kcal/g protein, 4 kcal/g carbs, and 9 kcal/g fat, then treats normal label rounding, serving changes, fiber, sugar alcohols, and imported-source gaps as caveats. It is a consistency check for reviewed food rows, not a food score, nutrition guarantee, diet plan, calorie prescription, diagnosis, treatment, or medical nutrition therapy. The same review note appears when a packaged-food lookup, local food-library match, restaurant paste row, quick add, or MyFitnessPal CSV import carries calories that need a second look before reuse.

When a public barcode lookup or food database search cannot return a usable match, Ojava keeps a private coverage note for the unresolved lookup. Fitness > Nutrition shows the recent cleanup queue beside the diary, grouped by barcode, search, and issue, so you can decide which labels to retry or turn into reviewed custom foods. Coach can summarize the same recent barcode and search misses when you ask about lookup coverage, package misses, or custom-food cleanup. When you save a reviewed custom food with the same normalized food name or barcode, Ojava marks matching private misses resolved so the cleanup queue does not keep stale rows. This is review context only: it does not certify the public food database, score foods, create a diet plan, prescribe a target, or write anything back to an outside nutrition app.

When you want to start from an existing food, use the Search foods shortcut in the Today card or the food database search form. Search for a food, brand, or packaged item, and Ojava searches your recent foods, custom foods, saved meals, recipes, and public food labels in one place. Local foods appear first when they match, public food data fills in broader package matches, and public results are ranked toward complete macro labels with serving detail and useful nutrient fields. Public food data comes from two free, independent public databases: Open Food Facts (crowdsourced package labels) and, when configured, USDA FoodData Central. Each result names its source, and a FoodData Central result drawn from USDA’s own analyzed reference data (not a manufacturer’s self-reported label) is marked USDA verified, so you can tell a lab-analyzed value apart from a crowdsourced one. If your custom food or reviewed diary correction carries the same barcode as a public package row, Ojava keeps your reviewed version ahead of the public match. Every result still applies to the same diary form for review before anything is saved. Change the servings field before saving and Ojava scales the calories, macros, and label nutrients for the amount you actually ate. Foods you mark as favorites in your recent shortcuts also sort higher when they match your search, so the meals you rely on do not get buried by public database results. Every result also has a one-tap Quick Log button beside it: it logs that food’s default portion straight to your diary with no drill-in, showing an inline confirmation with an Undo right after in case it was the wrong pick. When a result comes from Open Food Facts, it also carries a link back to that food’s own page on Open Food Facts and a Data looks wrong? flag, so you can help correct the public entry at the source and let Ojava know, without sending the food name or any nutrition value.

You can also import the CSV files from a MyFitnessPal export. Ojava recognizes meal nutrition details, exercise history, step or calorie-burn rows, water rows, and progress history for weight, body fat, waist, and extra body measurements such as neck, chest, hips, thigh, arm, calf, forearm, and shoulders, then saves valid rows only after you confirm the preview. Re-import checks your existing rows across the candidate date span and skips matching reviewed MyFitnessPal entries, while leaving manual Ojava rows alone. Reviewed step rows from those exercise exports can fill weekly movement context when wearable step rows are absent; wearable step rows stay the preferred source when both exist. For restaurant meals, paste public menu nutrition rows with an item name, calories, and at least one macro; Ojava shows every parsed public-menu row in a compact preview before batch save, flags skipped rows that need clearer calories or macros, and lets a single clean item save immediately through the same Food Log save path. Imported food rows stay visibly marked in the diary with compact MyFitnessPal or restaurant source chips, using the same source labels that travel into reports and exports. Imported rows are reviewed context you chose to bring over, not verified external data, automatic nutrition guarantees, diet advice, or a clinical nutrition plan, and Ojava does not copy a closed restaurant or community food database.

Food logging guide

Ojava also gives food logging its own education path, because the quality of the diary matters as much as the logging tool. The live guide starts with why a diary helps: memory and portion estimates are noisy, labels can be imperfect, and consistent entries are most useful when you look for patterns instead of treating one meal as a verdict. From there, it maps each logging method to the right moment: search or barcode for packaged foods, photo or label scan when typing is slow, voice or typed quick log when you already know the numbers, saved meals for staples, recipe import prep for batches, and MyFitnessPal CSV import when you are bringing over history.

The guide keeps practical accuracy visible without making the product brittle. It reminds you to review serving size, use weight when precision matters, write down oils, sauces, and drinks, log close to the meal when possible, and keep restaurant entries clearly marked as estimates. It also points you back to the parts of Ojava that turn logging into follow-through: water and fasting logs, meal planner, recent foods, saved templates, grocery prep, weekly digest, Nutrition Coach review, and Ojava Coach prompts for trend review.

The underlying education packet is ready for Ojava’s live logging surface. It covers why logging helps, what to capture, how to review accuracy, coach handoff, then gives Coach a consent-gated handoff line only after the user asks for that context.

• Why logging helps: Ready: explain food logging as a way to make meals visible over time, spot routine patterns, and reduce reliance on memory alone.
• What to capture: Teach users to capture food names, rough timing, meal slot, serving context, label or package clues, and notes they want reviewed later.
• How to review accuracy: Frame calories, macros, labels, and database matches as useful estimates that still need user review, especially for servings and custom foods.

Scientific references

• Dietary Assessment Primer, National Cancer Institute (2026). Used for the scientific boundary that no self-reported diet method is perfect and that food records need clear details, consistent timing, and careful interpretation.
• 24-hour dietary recall at a glance, National Cancer Institute (2026). Used for the food-detail model behind Ojava logging prompts: capture foods, beverages, time, source, preparation details, and portion size instead of relying on a food name alone.
• Overview of Dietary Assessment Methods for Measuring Intakes of Foods, Beverages, and Dietary Supplements in Research Studies, Current Nutrition Reports (2021). Used for the evidence boundary that self-reported dietary exposure measurement is difficult, so Ojava treats food logging as reviewed pattern context rather than precise nutrition truth.
• Essential guide to food logging, Local food-logging education reference snapshot (2025). Used as competitive reference context for food diary education patterns: logging consistency, portion review, label caveats, and app workflow readiness. Ojava wording and boundaries remain original.

When a reviewed MyFitnessPal exercise export includes calories burned, Ojava keeps that source-provided burn in the workout row and uses it before estimating activity calories from duration and body weight. When the export includes strength sets, reps, and load, Ojava saves those details into the same strength log used by the Workout tab and Coach context instead of flattening them into a generic note. If there is no reviewed workout burn for the day, same-day wearable active calories can fill the exercise add-back before Ojava falls back to a rough duration estimate. If a reviewed source supplies a signed activity calorie adjustment, Ojava can carry that signed value into the same context, so a negative adjustment lowers the same-day energy reference instead of becoming a workout. Ojava Coach uses the same saved exercise-calorie add-back setting as the diary, including partial 0 to 100 percent add-back, so turning add-back off keeps the Coach energy context on logged food only. Coach also receives a separate activity-adjustment context line that explains whether exercise calories are off, missing same-day food or activity context, represented by wearable active calories, signed from source activity adjustment, waiting on account-backed settings activation, or active with reviewed workout rows. That signed source value remains reviewed source context, not a diet prescription or clinical nutrition plan. If the same export includes steps, Ojava can include those reviewed steps in the weekly digest, the visible Fitness Progress steps card, and the Fitness Progress Overview line that Coach reads when no wearable step rows are available, without adding them on top of wearable steps or converting them into active minutes. Coach also receives a compact fitness source reconciliation packet when recent reviewed workouts, MyFitnessPal exercise imports, or wearable activity rows overlap. It chooses one preferred source per comparable metric, keeps reviewed workout calories beside wearable active calories for review, and names any fallback instead of silently summing app totals together.

Ojava now has licensed content scaffolds for future food, restaurant, community, and recipe catalog partnerships. Those scaffolds prepare provider contract placeholders, rights review, ingestion mappings, review queues, activation flags, and audit fields. Recipe catalog readiness also tracks the provider contract state, source license, recipe media rights, ingredient and nutrition mapping, human review workflow, and the disabled catalog import flag before anything can be exposed. Ojava Coach can explain that the current live substitutes are your own foods, saved meals, recipes, MyFitnessPal CSV imports, Open Food Facts and USDA FoodData Central label search, reviewed public restaurant menu paste, reviewed recipe import prep, and local ingredient matching. The scaffolds still do not copy a corpus, scrape external sources, expose third-party catalogs, fetch arbitrary recipe URLs, auto-save recipe nutrition, prescribe a diet, or skip your review.

Ojava Coach also receives source-specific import packets for reviewed MyFitnessPal food, exercise, water, and progress rows. Those packets name how many rows and days came from the reviewed import, the latest date, meal slots, sample foods, macro completeness, label nutrient coverage, source calories, steps, duration, imported strength-set counts, hydration totals, and weight, body-fat, or waist changes when those values are present. Progress imports can also preserve extra measurement names and values as reviewed body-context notes, so Ojava Coach can summarize them without turning them into a separate body-composition score. They are provenance and self-tracking context only: no live MyFitnessPal sync, food scoring, training plan, dehydration assessment, body judgment, diagnosis, treatment, or medical nutrition therapy.

MyFitnessPal-style meal-detail imports and hand-entered foods can preserve more than calories and macros when those fields are present. Fiber, sugar, sugar alcohol, sodium, saturated fat, cholesterol, potassium, calcium, iron, vitamin D, vitamins A, C, E, K, B1, B2, B3, B6, folate, B12, magnesium, zinc, phosphorus, selenium, copper, manganese, and chloride travel into the same reviewed Food Log notes as photo scans, barcode results, custom foods, recipes, and public label matches. When a row has total carbs plus fiber or sugar alcohol, Ojava derives net carbs from the reviewed row instead of asking Ojava Coach or the diary to guess. Ojava Coach can also receive a carb-quality readiness packet from those reviewed rows: recent food days, rows with total carbs, rows with parsed label detail, fiber, sugar, added-sugar, sugar-alcohol, and net-carb support, plus missing inputs to tighten before a conversation. It is descriptive diary context only, not a glycemic score, food ranking, diet prescription, diabetes management, diagnosis, treatment, or medical nutrition therapy. Goal settings can also turn on net carb view, which makes the diary show net carbs first only on days with enough reviewed label detail and fall back to total carbs when that detail is missing. Ojava also checks nutrient-depth completeness across your recent diary before Coach uses micronutrient or custom nutrient-target context. It counts which food rows include reviewed label nutrient detail, which nutrients have enough rows across enough days to discuss, and which saved nutrient targets still need more label detail. That helps Coach say when fiber, sodium, saturated fat, vitamin, mineral, caffeine, alcohol, or other supported label fields are ready for pattern review, or when the diary is still too thin. Ojava also separates the same-day target details into supported, estimated, and missing nutrient evidence before Coach discusses them. A target is supported only when every reviewed same-day row has an explicit parsed value and no estimated source mode; label scans, barcode lookups, public food searches, meal-photo scans, quick adds, and imported app totals stay marked as estimated evidence until you review the rows. It does not diagnose a deficiency, recommend supplements, certify nutrient accuracy, score foods, prescribe a diet, create medical nutrition therapy, diagnose, or treat.

The Nutrition Coach review panel summarizes the selected day’s diary, the nutrition digest, weekly check-in, weekly digest, protein anchors, nutrition rhythm, recent food patterns, and follow-through changes from recent logging, planning, library, and step context before it opens Ojava Coach with nutrition-specific prompts. When metabolic-program context is available, the same panel also shows the current weekly priority, first habit, source lanes, progress fields to review, and a save-to-goals action that writes the priority into your own goal list for the next week. Its quick actions and custom question box carry that current review summary into Coach, while Ojava Coach also receives reviewed-day status, food timing review, weekly digest, recent prior-week digest recall, weekly calorie and macro budget, meal-plan coverage, and planned versus logged meal review through its regular patient snapshot. The digest is built from reviewed food rows for the selected day: meal slots, entry count, calories, protein, carbs, fat, target percentages, saved per-meal calorie-goal progress where the meal has reviewed calories, logged eating window, workout minutes, and missing inputs. It is the MyFitnessPal-style daily recap Ojava Coach can read before nutrition questions, not a diet plan, calorie prescription, or medical nutrition therapy. When enough reviewed food-log days exist, Coach also receives an annual nutrition recap: reviewed row count, logged days, calorie and protein day coverage, average logged macros where present, frequent foods, broad food-group clues, busiest tracked month, and parsed label-nutrient coverage. The recap prefers the current year and falls back to the prior year early in a new year, names missing signals, and stays in general wellness context only. Coach also receives a same-day nutrient dashboard focus when your diary and saved targets support it. Ojava picks custom label nutrients first, then heart-healthy, low-carb, macronutrient, or calorie focus, and sends only finished logged, target, percent, and remaining values from reviewed rows. When no custom label-nutrient targets are saved, Coach can still see a MyFitnessPal-style macro fallback from reviewed same-day calories, protein, carbs, fat, and your resolved nutrition targets. Saved goal settings can also carry your daily water target, so the Water tab, Fitness Progress, reminders, and Coach context use the same reference when it is present. It does not score foods or turn those numbers into a prescribed diet. The visible nutrient dashboard in Nutrition now has the same five selectable preset lenses (Calorie focus, Macronutrient focus, Heart healthy, Carb conscious, and a Custom pick of up to three tracked nutrients), and your selection persists per account so the dashboard and the Coach context describe the same focus. If you track a current GLP-1 medication and log a matching routine event, Coach can read a diary-native context packet for that day: food entries, calorie and protein completeness, water logging, appetite or digestive notes, body trend or same-day weight rows, workout context, and missing inputs to tighten before a clinician conversation. It is conversation prep only, not eligibility, prescribing, dosing, medication adjustment, or treatment guidance. When a connected source provides nutrition-app totals across multiple days, Fitness > Nutrition shows the same source check beside the diary: source nutrition-app calories and macros, reviewed Ojava diary totals, overlapping days, days that need review, and the largest visible gaps. Coach can compare the same overlapping source days with reviewed diary days, summarize agreement or missing days, and keep the imported totals separate from reviewed diary calories and macros instead of silently adding them together. Ojava Coach also receives food-quality context from reviewed rows: label detail coverage, protein anchors, fiber clues, plant-variety clues, and packaged or heavily processed food clues. If your record contains reviewed HEI-2020 constituent rows, Ojava can also calculate Healthy Eating Index 2020 readiness from those exact amounts using the official component standards. Ordinary diary rows, macros, photos, and meal descriptions do not become HEI inputs by themselves; when constituent rows are missing, Ojava names the missing inputs instead of scoring the diet. When you ask about food-entry review, scan sources, barcode matches, quick-add entries, database matches, restaurant menu imports, label scans, or nutrition-app imports, Coach can also see food entry review readiness from recent accepted food rows across quick add, barcode lookup, food database search, nutrition-label scan, meal-photo scan, custom foods, saved foods, recent foods, recipe library items, reviewed public restaurant menu imports, and nutrition-app imports. The same readiness packet is visible in Fitness > Nutrition when recent food rows are available, so you can review source counts, entries that need serving or macro cleanup, calorie-to-macro consistency notes, strengths, next steps, and the review boundary before asking Coach. The packet sends source counts, serving completeness, macro completeness, label nutrient detail coverage, calorie-to-macro review prompts, review queue prompts, restaurant menu review prompts, and next logging steps as finished context. It is private general-wellness logging review only, not food database accuracy certification, food scoring, diagnosis, treatment, a prescribed diet, calorie prescription, or medical nutrition therapy. When your record has enough reviewed food-log days plus source-backed sleep, readiness, HRV, or resting-heart-rate rows, Coach can also see association-only nutrition habit patterns. It can compare day patterns such as late eating, protein-anchor days, high label-detail days, later caffeine or alcohol clues, and heavier late meals with the next recovery day. This is sample-guarded pattern context only: no food scoring, causation, alerts, diet prescription, diagnosis, treatment, or medical nutrition therapy. Coach can also read association-only meal timing and movement context when reviewed food rows, timestamped workouts, or wearable movement days are present. The packet names how many workouts have nearby food within four hours, whether calorie or protein context is present, which movement days have food logged, and what inputs are missing. It is not a fueling plan, timing prescription, score, causation claim, diagnosis, treatment, or medical nutrition therapy. If you explicitly log wheelchair pushes, seated workouts, chair workouts, mobility-aid context, adaptive cardio, or a source-provided adaptive mobility metric, Coach can pair those movement days with reviewed food diary context before preparing access-aware review questions. Ojava does not infer disability from low steps, create a diet plan, set a calorie target, prescribe exercise, clear activity, diagnose, treat, or create medical nutrition therapy. Reviewed diary rows can also prepare a local food-name writeback readiness packet for a future partner sync. Coach sees the bounded candidate count, skipped-row count, examples, and the fact that external writeback is off; Ojava does not send food names, calories, macros, or credentials to MyFitnessPal, Fitbit, Apple Health, Google Health, or any partner from that packet. When you ask specifically about live source-account sync, MyFitnessPal writeback, or food-app writeback, Coach also receives a source-account activation-readiness line. It names the missing OAuth or provider contract, user consent, field mapping, review before write, conflict handling, and audit trail rails, plus the disabled source-sync, writeback, and auto-log flags. The safe substitutes remain reviewed CSV imports, reviewed Ojava Food Log rows, local food-name review, and source-total reconciliation. Grocery provider status stays on the separate server-backed connected-grocery card. Fitness also shows a Nutrition sync status card beside the diary, and when you ask about mobile sync or logging food on your phone, Coach receives the same nutrition sync-status packet. It names Fitness > Nutrition as the phone-friendly account-backed Food Log route, and separates account-backed food rows, workouts, water, fasting, meal plans, body measurements, progress photos, reports, Coach context, messages, custom foods, saved meals, recipes, favorites, nutrition goals, completed diary dates, and reminders from activation-gated rails such as HealthKit, Health Connect, live MyFitnessPal sync, Fitbit food-name sync, and provider writeback. The same card includes source-readiness profiles for MyFitnessPal, Fitbit, and food-name writeback. It shows local substitutes such as reviewed CSV imports, source-total reconciliation, and local food-name review, plus the owner or provider rails still needed before any live sync, external writeback, or auto-log path can be reviewed. When you ask what MyFitnessPal, Fitbit, or Health Connect sync fields mean, Coach can also read a reference-only provider contract: Health Connect gets MyFitnessPal meal summaries and custom meals under Other, Fitbit receives link-date-forward MyFitnessPal meal summaries, individual food names are Premium-gated provider behavior, historical meals do not backfill, water is one-way from MyFitnessPal, and Fitbit weight behavior stays separate from Ojava body rows. For source-account, MyFitnessPal, or writeback questions, Coach also receives one consolidated native and platform sync diagnostic packet so each rail is named as live or gated with its reason. Its grocery rail describes only local reviewed-list export; the server-backed connected-grocery card remains the source of truth for Kroger and Chicory readiness. The native HealthKit and Health Connect adapter can contribute supported wearable rows such as total energy burned and basal body temperature after native activation, but it does not expose dietary macro or water-intake samples today. Dietary totals and water context therefore stay on reviewed file imports, nutrition-app source totals, and manual Water Log rows until a truthful adapter or provider path exists. Ojava also keeps a deterministic app-detail parity check for the Levels-style nutrition and metabolic app surface: onboarding, food and exercise logging, source-glucose context, personalized review loops, daily reports, lab-panel context, privacy, support, and Health Connect readiness. That check is a product-readiness map, not a new claim of direct CGM connectivity, live Health Connect sync, glucose scoring, diabetes management, alerts, medication guidance, prescribed diets, or medical nutrition therapy. A stricter plant-variety packet counts distinct visible plant-food names over the recent diary window, grouped only when descriptions or notes support categories such as berries, leafy greens, legumes, whole grains, nuts and seeds, herbs, and spices. If a row just says smoothie, bowl, salad, or another broad meal name without ingredients, Coach sees that as a detail gap instead of guessing what was inside. The same reviewed rows also produce a gut-nutrition packet with fiber, plant-variety, fermented-food or probiotic clues, processing clues, total-sugar context, and saturated-fat context when those details are present. When enough recent diary days, parsed fiber details, explicit plant-food clues, and fermented-food context are ready, Coach can also anchor a compact gut nutrition readiness line for gut, microbiome, fiber, fermented-food, plant-diversity, probiotic, ultra-processed, or nutrition-readiness questions. Coach receives an ingredient and processing packet from reviewed food descriptions and notes only: ingredient-group clues, package or label context, prepared or frozen context, restaurant or takeout context, and snack, dessert, or sweet-drink context when those words are present in your diary. A separate processed-food education packet turns those reviewed package, prepared-food, restaurant, snack, dessert, and sweet-drink cues into plain-language context for Coach. A risk-factor readiness packet then names the evidence coverage, cue families, missing label or ingredient inputs, and review questions Coach can use for a bounded conversation. It explains what to inspect in the diary, such as ingredient lists or label detail, but it does not assign a processed-food risk rating, score foods, verify food safety, open grocery checkout, or create medical nutrition therapy. A scan-to-grocery readiness packet can also turn accepted diary rows plus reviewed meal and photo-scan drafts into a local grocery checklist with store-section suggestions. It is navigation help for your own review only, not camera-based meal recognition, a live grocery database, checkout, ordering, food scoring, or medical nutrition therapy. Meal-plan grocery lists and saved recipes also feed a connected-grocery readiness packet for local export without guessing whether a provider is live or connected. The Meal Plan grocery card can keep a browser-local picked-up checklist for needed items while leaving pantry items marked on hand. The same planner area includes an editable account-backed shopping list: type groceries line by line, mark on-hand pantry items, check items off locally, copy the reviewed list, export `.txt`, and send bounded grocery-list context to Coach when nutrition settings sync is active. A separate server-backed card shows the real Kroger runtime and connection state. When every server dependency and the Kroger activation switch are ready, you can connect your account, choose a store, match exact products, review the final preview, grant purpose-specific consent, and confirm one cart handoff. Every preview, confirmation, and acknowledgement is size-bounded and strictly validated before handoff processing, and failures show recovery copy without raw service or configuration details. If the runtime is unavailable, new provider actions stay disabled while an existing connection remains visible for export or disconnect. The handoff can add reviewed UPCs and quantities to a Kroger cart, but Ojava never checks out, charges, places an order, schedules delivery, accepts substitutions, or writes back to MyFitnessPal. It can also compare the current 7 days with the prior 7 days for movement in those same quality signals, so trend language comes from the reviewed diary instead of a model guess. That context stays descriptive: no microbiome test, gut score, food score, plant-variety score, processed-food risk rating, processed-food score, prescribed diet, diet advice, microbiome claim, or medical nutrition therapy.

Ojava also organizes metabolic-program readiness into four educational tracks inspired by the way people naturally think about their goals: Heart Health, Weight Management, Glucose Stability, and Metabolic Exploration. The packet uses reviewed food logs, workouts, weekly nutrition patterns, progress context, source-provided glucose summaries, source-provided post-meal glucose rows when they exist, and finished metabolic lab scores from accepted records, then names available signals, lab context, missing inputs, weekly priorities, first habits, progress fields, and user-set targets. You can save the current weekly priority into your own goals so the program does not disappear after one review. It is a planning surface for general wellness conversations, not a CGM live connection, glucose-control plan, clinician-assigned program, diet prescription, diabetes-management plan, medication recommendation, diagnosis, or medical nutrition therapy.

If source-provided glucose rows line up with timestamped meal logs, Ojava can also compare repeated meals or large macro contrasts for a Levels-style meal experiment conversation. The comparison is built only from the source-backed pre-meal and post-meal glucose context already in your record, then Coach receives a compact pattern line when you ask about glucose, metabolism, or meal experiments. It is not direct CGM connectivity, glucose scoring, diabetes management, alerts, medication guidance, a prescribed diet, diagnosis, treatment, or medical nutrition therapy.

Because account-backed nutrition settings are active, Ojava Coach can also read a bounded reusable-template summary from your saved custom foods, saved meals, recipes, favorite food shortcuts, and saved preference filters. It can also receive a nutrition library maintenance packet that names saved foods, meals, recipes, favorite shortcuts, and shopping-list lines that may need serving, macro, label-source, or freshness review before they are reused. That packet is review context only: it does not certify nutrition accuracy, score foods, auto-correct labels, prescribe a diet, diagnose, treat, or provide medical nutrition therapy. Fitness tracker ZIP exports also include a saved nutrition-library CSV for account-backed custom foods, saved meals, recipes, favorite shortcuts, shopping-list lines, and goal-setting summaries. That file is personal portability only, separate from logged intake, and incomplete saved-meal or ingredient macros are labeled incomplete rather than treated as zero. It also gets deterministic Nutrition Coach food ideas from your saved foods, repeated accepted diary foods, saved meals, recipes, and planned meals, ranked against today’s remaining calorie and protein context when those targets and logs exist. The visible Nutrition Coach review uses those same custom foods, saved meals, repeated diary patterns, recipes, and planned meals, so the ideas you see in Fitness match the reusable food context Coach can discuss. If you ask Nutrition Coach for broader ideas, it can add request-scoped public food-label candidates from the public food database beside, not ahead of, your own foods, meals, recipes, and plans. Those rows are idea candidates only: public label data can be incomplete or stale, each candidate should show its source and missing serving, macro, or label fields, and you review the match before saving or logging it. Public candidates do not create medical nutrition therapy, a diagnosis, a treatment plan, a calorie prescription, or a safety guarantee. When your account settings or meal-plan details include saved preferences, foods to avoid, or allergy notes, Ojava uses those terms as review filters before ranking ideas: preference matches and repeated recent logging can move familiar foods up, while avoid or allergy matches are left out of the candidate list. The ideas are review-before-logging context only, so Coach can talk through foods you already saved without promising food safety, judging a food good or bad, diagnosing an allergy, inventing a diet plan, calorie prescription, or medical nutrition therapy. Coach can also see recipe follow-through when saved recipes or user-owned recipe starters have not yet been planned or logged, and it can see consolidated meal-prep sessions that group planned meals by date, prep mode, repeated ingredients, and grocery readiness. Those packets stay local and review-only: no automatic meal plan, food-safety verification, grocery checkout, calorie prescription, or medical nutrition therapy is created. It also receives a completed-day five-week consistency estimate only when the reviewed date is account-backed and has enough weight and maintenance context, plus a fourteen-day Nutrition Coach history packet with logged days, entry count, average calories and protein per logged day, meal-slot coverage, often-logged foods, week-over-week logging direction, and a follow-through summary of what changed since the prior seven days when enough diary rows exist. It also receives the metabolic-program readiness packet as finished context, including lab signals when accepted records support them, so Coach can discuss Heart Health, Weight Management, Glucose Stability, or Metabolic Exploration without recomputing your nutrition, labs, or glucose patterns itself. If a browser is offline or account settings cannot be reached, Coach keeps using the logged foods and saved templates it can verify.

When you only know the numbers, use quick add. It saves calories plus optional protein, carbs, and fat directly into the same food log row, then updates the selected day’s totals and the breakfast, lunch, dinner, and snack breakdown. Quick add, log again, saved meals, custom foods, recipes, multi-day logging, and meal copy all honor the selected diary date and entry time.

The diary also shows a seven-day calorie and macro budget when you have enough logged food and saved targets. It compares your current week against your own calorie, protein, carb, and fat targets so you can see what is left or already over, without turning those targets into a prescribed diet or medical nutrition therapy. Coach can also carry a compact recall of recent prior weeks from the same weekly digest and budget calculators, so if you ask about last week it can answer from logged rows instead of guessing.

For foods you create yourself, save a custom food with its serving, calories, macros, and optional label nutrients across the shared nutrient and compound set. Custom foods can sync with your Ojava account for reuse across browsers; when you log one it becomes a normal Food Log row on the selected diary date and time, or across selected upcoming diary days when you are planning repeated foods. If a packaged-food barcode is not found, Ojava can prefill a custom-food draft with the barcode in its notes so you can add the label numbers once and reuse it later. If you scan a readable nutrition label, the diary form can also send the reviewed serving, macros, and label nutrients into a custom-food draft for reuse. When a public barcode or food database result fills the diary form, you can also save that reviewed result as a custom-food draft, so the corrected serving, barcode, macros, and label nutrients are available from your own reusable foods next time. You can log a quarter serving, double serving, or another reviewed amount without doing the math by hand.

Each meal also shows its own macro breakdown. Toggle between grams and percentages to see how breakfast, lunch, dinner, or snacks are split across protein, carbs, and fat for today, using the same food rows that feed the daily macro tiles. Ojava Coach receives those meal percentages as meal ratios only, while daily protein, carb, and fat remaining comes from your saved daily targets. It does not turn meal percentages into per-meal macro targets.

Goal settings cover calories, macros, meal calories, exercise-calorie add-back, and optional diary meal names, plus daily label-nutrient targets for the shared vitamins, minerals, fats, caffeine, alcohol, and label-compound fields. When today’s saved entries include those label details, the diary shows how much is logged against your own target, and Coach receives the same saved add-back preference plus same-day wearable active-calorie context before it summarizes same-day calories remaining.

Goal settings can also rename the visible diary meal slots and split your daily calories across those meals. Ojava supports two extra account-backed meal slots, Meal 5 and Meal 6, for people who prefer more detailed diary labels. When a meal goal is set, the diary shows that meal’s calories against its target and whether you still have room left for that part of the day. Ojava Coach receives the same per-meal goal progress only when the account-backed settings are available and the meal has reviewed calories, so it does not invent progress for blank or partial entries. The daily digest, Nutrition Progress Overview, and Ojava Coach use the same meal-slot labels and expanded slots as the diary, so Meal 5 and Meal 6 count consistently across saved food rows, planned meals, and Coach context.

Multi-day logging is for planned repeats. Add one staple, choose up to seven upcoming diary days, and Ojava writes each selected day as its own food-log row with the same calories, macros, serving, and meal slot. Future planned rows stay out of same-day quick picks and Coach context until their day arrives, so planning ahead does not pretend you already ate it. Saved meals, custom foods, and recipes have the same selected-day action, so a breakfast template, packaged staple, or batch recipe can be planned without retyping the entry.

Foods you have already logged can be added again with one click. Ojava copies the same serving, calories, protein, carbs, and fat into a fresh entry for today, so repeat meals and regular snacks do not have to be typed from scratch.

When typing the whole form is inconvenient, use voice logging in browsers that support speech recognition, or paste the same quick-log wording into the typed log box. Say or type what you ate, including the meal if you want, and Ojava fills the food description and meal slot for review. If you include the calories, protein, carbs, or fat, Ojava fills those numbers too. It also understands common phrases such as “protein 28 grams” and ignores out-of-range one-entry nutrition numbers instead of trusting a bad transcript. Otherwise, add the numbers yourself or use a photo or barcode when you want nutrition numbers filled in.

For meals you eat often, use saved meals. Save the current breakfast, lunch, dinner, or snack as a reusable template, then log every item in that meal back into today’s diary at once or across selected upcoming diary days. The saved template can sync with your Ojava account; when you log it, each item is written as a normal food-log row so reports, calorie totals, and Ojava Coach use the same record path. Choose the number of servings before logging when you ate more or less than the saved template. Coach can also name saved meal or custom food templates that need serving, calorie, macro, label-detail, source, or freshness review before they should be treated as reusable context. That cleanup list stays private to your record and never edits a label or scores a food automatically.

The Today card also surfaces quick picks from your recent food history. Foods you log often appear as compact actions, ranked by favorite status, frequency, and recency, and they use the same one-click log-again path as the diary rows. The star button keeps a favorite food ahead of other recent foods. Those favorite shortcuts follow your account when sync is available, with browser storage as the fallback for offline or unavailable settings.

Meal plans can also carry household context. When a planned meal includes servings, household count, shared-with notes, and optional per-person calories or protein, Ojava turns that into review-only household prep math, such as how many bowls or wraps to prepare for the people listed. If you add prep notes to planned meals, Ojava can also turn those user-authored notes into a short local checklist and send the same finished steps to Ojava Coach for meal-prep questions. Preference, avoid, and allergy notes can also filter reviewed Nutrition Coach food ideas from your own saved items. Account-backed preference settings provide the same preferred, avoid, and allergy filters across browsers when sync is available. They narrow suggestions only; they do not prove that a food is safe for you, prescribe what to eat, or replace allergy or nutrition care. That checklist is not food-safety verification, grocery ordering, a diet plan, calorie prescription, medical nutrition therapy, or automatic food logging.

Food reminders help you keep the diary visible through the day. Set breakfast, lunch, dinner, snack, or any-food check-ins with quiet hours, and Ojava marks each reminder as logged, upcoming, due, or muted from today’s food rows. On the web, you can allow same-device browser notices while Ojava is open. In the native iOS or Android app, Ojava can schedule PHI-free local food-reminder notifications for later today after device permission is granted. Coach can also see the configured diary checkpoints as habit context. These are local diary reminders, not a medical alert system, adherence proof, remote push service, or diet treatment.

When yesterday or another recent day is close enough, copy the latest logged day into the selected diary date, or copy just breakfast, lunch, dinner, or snacks from the most recent matching meal. Ojava keeps the same meal timing, serving, calories, macros, and notes, then marks each new row as copied so you can adjust anything that changed.

Recipes work the same way. Enter each ingredient with calories and optional protein, carbs, and fat, choose the number of servings, and Ojava calculates the per-serving total. You can also paste recipe text, a recipe link note, a plain ingredient list, or recipe page source that includes schema Recipe data into the import prep box. Ojava pulls out the recipe name, serving count, source URL, and ingredient names for review, but it does not invent calories or fetch recipe pages for you. You can also scan a photo of a recipe card, cookbook page, or screen; Ojava pulls the recipe title, servings, and ingredient lines it can actually see in the photo into the same review box, without inventing calories, servings, or ingredients it cannot make out. If you already saved matching foods, saved meals, recipes, or recent diary rows, use Match ingredient nutrition to prefill calories and macros from those reviewed sources, then check every line before saving. The review names matched ingredient lines and still-unmatched lines so partial recipe nutrition is visible before you save. When you log a recipe, choose the servings you ate and it becomes a regular food diary entry on one day or selected upcoming days, so recipe tracking and daily calorie tracking stay on the same record path. Recipe starters are made only from saved meals, custom foods, and recipes you already created, so you can review or save a new template without using an outside recipe catalog or invented nutrition. Ojava Coach can also see a bounded summary of those user-owned recipe starters when your saved nutrition library is account-backed, so recipe ideas stay connected to the same reviewed foods. Coach can also name saved custom foods with the same barcode, or saved meals and recipes with the same name, when their reviewed calories or macros conflict, while identical duplicate nutrition stays quiet. Those prompts are cleanup notes only: Ojava does not merge, delete, overwrite, certify, or score saved foods. Each saved recipe can also be copied as reviewed share text or exported as a `.txt` file with servings, ingredients, per-serving nutrition, total nutrition, and a clear wellness boundary. Ojava does not post it publicly, send it externally, or turn it into an order.

For packaged foods, use barcode lookup. Scan a package barcode from a photo or type the numbers printed under the barcode, and Ojava searches public label data to pre-fill the food name, serving, calories, protein, carbs, fat, fiber, sugar, added sugar, sugar alcohol, sodium, including salt-to-sodium fallback when a public label gives salt but not sodium, saturated fat, trans fat, monounsaturated fat, polyunsaturated fat, omega-3, omega-6, cholesterol, potassium, calcium, iron, vitamin D, choline, iodine, caffeine, alcohol, and other supported label nutrients when those label fields are available. If you already saved or logged a reviewed correction for that barcode, Ojava uses your reviewed food first instead of replacing it with the public row. The photo reader uses the browser scanner when available and falls back to a client-side barcode reader in browsers without that API. Review the label match before adding it, because public package databases can be incomplete or stale. If the barcode is not found, save it as a custom-food draft, type in the package label once, and reuse it later. If you have the label but not a usable barcode, scan the nutrition label from the food form and save the reviewed numbers as a custom food. If the public lookup does find a useful result, you can still save the reviewed result into your custom foods after checking it, which keeps your corrected package row ahead of public label data in future searches.

The food log also includes a nutrition report that starts as a 7-day view and can be changed to any reviewed date range up to one year. It summarizes average daily calories, days logged, average protein on logged days, optional label-nutrient detail such as fiber, sodium, potassium, and vitamin D when you logged it, your highest logged day, daily calorie totals, source counts, and a same-length prior-period comparison when enough earlier entries exist. The report can stay on all days, focus only on days with food logged, focus only on diary days you marked reviewed, or leave out today when the current day is still in progress. It also reviews timestamp patterns from your own diary, including average first log, average last log, eating window, and calories after 6 PM when enough timed entries are present. When rows came from a reviewed MyFitnessPal CSV import or reviewed public restaurant menu import, the visible diary row shows the compact source chips. The report keeps a MyFitnessPal import-entry count where relevant, and the diary-entry export carries source, provider, import tag, and reviewed notes columns so the provenance follows the row into visit prep. From there, it copies reviewed share text, exports a `.txt` diary, creates an expiring private read-only link, opens a printable food-diary report, or exports the same view as a CSV when you want to review it in a spreadsheet or share the numbers in a visit-prep note. The link is a snapshot of the selected reviewed report and does not create a public feed, friend graph, external send, or live-updating diary. If someone opens a shared diary while signed in, they can copy the entries into their own food log for review and later editing, without linking accounts or writing back to the sender. Ojava Coach also receives a compact recent-period report summary as finished deterministic context, without raw entry text or diet-prescription language. For broader progress questions, Coach can now receive a Nutrition Progress Report that joins this diary summary with Nutrition Progress Overview, reviewed source-provenance counts, and body progress context, so the answer starts from the same reviewed records instead of recomputing them.

The Fitness side rail also has tracker exports. Download a multi-file ZIP with separate nutrition, exercise, progress, hydration, meal-plan, and full-tracker CSV files, download the whole record as one spreadsheet-friendly CSV, or choose smaller files for food, exercise, hydration and fasting, or body measurements and meal plans. Each export reads from the same owner-controlled tracker tables and supports a start date, an end date, or all time. When email delivery is active, the same ZIP can be emailed to your signed-in account address. If email delivery is not active, Ojava keeps the download buttons available and does not pretend the message was sent.

The diary card also shows a label-nutrient strip for the selected date when entries include those details. The strip is generated from the shared nutrient spec, including fiber, sugar, added sugar, sugar alcohol, sodium, saturated fat, trans fat, monounsaturated fat, polyunsaturated fat, omega-3, omega-6, cholesterol, vitamins, minerals, choline, iodine, caffeine, and alcohol where you logged them. Those values roll up from the food rows you already saved, so the daily view, weekly report, CSV export, and Ojava Coach all read the same nutrition record instead of separate nutrient trackers. When a food row has total carbs plus fiber or sugar alcohol, Ojava also derives net carbs from that same row and shows the value in the diary, export, and Coach context.

Those same label details now feed a weekly nutrient focus for Ojava Coach. It looks across the last 7 days for the expanded label-nutrient set, waits until at least three detailed days are logged before treating the pattern as meaningful, and names the clearest food-label focus. This is a logged-food review, not a prescribed diet or medical nutrition plan.

The diary also shows Food Analysis cards from the last 7 days: ranked top and lower logged-food contributors for calories, protein, carbs, net carbs, fat, and label nutrients when those values are present. Each nutrient card shows the food, total amount, and entry count, and Ojava Coach receives the same contributor context. It is a pattern review for your own diary, not a good-food or bad-food score and not a prescribed diet.

Diary food insights

As you log meals, the food diary can show a short, in-the-moment note beside a recently logged entry: a notable amount of protein, fiber, sodium, sugar, or saturated fat in that item, read against what is left of your saved daily target when one is set. Each note is a single sentence, and you can dismiss it. This is rule-based label and macro review from your own logged food, not a deficiency diagnosis, food score, supplement recommendation, or medical nutrition therapy.

Food suggestions

The Nutrition tab’s Coach & insights section can also name your single biggest current nutrient gap, protein or a saved micronutrient target you are furthest from, and suggest foods to help close it. It looks at your own food history first, so a food you already log for that nutrient shows up before anything else, then adds a small curated list of general food ideas with a plain prep tip. You can filter those general ideas to vegan, vegetarian, or pescatarian. This is general food-suggestion context, not a personalized diet plan, supplement dosing, or medical nutrition therapy.

This week’s habit

Each week, Ojava names one small, specific habit built from the same nutrient-gap review, such as adding a fiber source to four lunches this week, and tracks your progress against the week’s own logged entries. It rotates which meal it targets from week to week, and it is a single self-chosen habit, not the same thing as the user-initiated streak challenges you can browse and pick yourself. It is private habit-forming context, not an adherence score, prescribed diet, or medical nutrition therapy.

Food lists

Food lists let you pick one nutrient, such as calories, protein, fiber, sodium, potassium, calcium, or iron, and a window of 7, 14, or 30 days, then see your own logged foods ranked highest and lowest for that nutrient over that window. It reads the same underlying logged totals as the Food Analysis cards elsewhere in the diary, so the numbers never disagree, and it is pattern context for your own record, not a good-food or bad-food score.

The tracker also shows the same nutrition-target card that appears in Insights when your body and activity data are available. It uses the shared deterministic calculator for maintenance calories and macro targets, so the food diary, Insights, and Ojava Coach stay aligned.

Goal settings can use that same calculator as a guided starting point. Choose maintain, lose, or gain, or enter an optional goal weight to infer the direction, then review and save the suggested calorie and macro targets. When a current weight, goal weight, maintenance reference, start date, and target date are present, Ojava can also estimate the daily energy difference and macro target for that date path. That date math is self-guided diary context, not a prediction, diet plan, calorie prescription, weight-management treatment, or medical nutrition therapy. You can still set calorie, protein, carb, and fat goals by hand for every day, save a percentage macro split, tune a weekday, and choose whether 0 to 100 percent of logged exercise calories are added back into the day’s calorie goal. The diary ring and macro tiles update from account-backed nutrition settings when sync is available, with browser storage as the fallback.

Ojava Coach also receives a same-day energy-context line when food is logged: calories eaten, same-day estimated workout calories when weight and workout duration are available, the maintenance reference used for comparison, and calories remaining. This is food-diary context for coaching conversations, not a prescribed calorie budget or medical nutrition therapy.

If you import source glucose readings with precise timestamps, the Fitness side rail can also show whether your record is ready for metabolic pattern review. Ojava checks for imported glucose rows and timestamped meals, names whichever source input is still missing, then pairs your own timed food rows with nearby glucose rows when both are present. It can show matched meals, post-meal peaks, and peak changes for pattern review. This is food, activity, sleep, visit-prep, and Ojava Coach scaffold-readiness context only, not direct glucose device connectivity, diabetes diagnosis, diabetes management, glucose scoring, alerts, insulin or dose guidance, medication advice, treatment, emergency detection, care escalation, or medical nutrition therapy.

When those meal-glucose rows line up with nutrition-recovery associations and active goals, Ojava Coach also gets a reactive metabolic coaching readiness line. It names the signal groups that are present, the missing inputs, the next review cadence, and the first thing to inspect next. That context is still general wellness review readiness, not real-time monitoring, glucose control, clinician messaging, medication advice, a prescribed diet, diabetes management, or medical nutrition therapy.

For cardiometabolic visit prep, reviewed food and macro rows can also join accepted glucose or A1c, lipid or ApoB context, blood pressure, body, activity, sleep, and recovery rows in Coach. The packet is a clinician-conversation summary only: ready domains, missing inputs, and questions to review, not a diagnosis, risk score, lab order, medication plan, prescribed diet, treatment, or medical nutrition therapy.

Ojava also summarizes your recent nutrition rhythm from the entries you already log: how many meals are on file, how many days they cover, your current tracking streak, average logged calories and protein per day, average eating window, and the meal you log most often. This is a diary pattern summary, not a prescribed diet, eating-disorder assessment, or nutrition therapy.

Food timestamps can also help Coach answer body-clock questions when you ask about eating windows, late caffeine, late meals, circadian rhythm, or sleep timing. The body-clock readiness packet combines reviewed food timing, late food or drink clues, fasting windows, source sleep timing, daylight exposure, and recovery context, then names what is ready and what is still missing. It stays descriptive: no exact eating schedule, fasting prescription, diet prescription, circadian diagnosis, alarm scheduling, or real-time monitoring.

When a diary day looks right, you can mark it reviewed. Ojava keeps a simple completed-diary streak beside that day’s entries, calorie rows, and review status, and you can reopen the day if you add or correct an entry later. If your record also has a current weight and maintenance calorie reference, reviewed days can show a rough five-week consistency estimate from that day’s logged calorie balance. It is a diary math check only, not a prediction, nutrition score, diet plan, or medical nutrition therapy. Those completed-day dates can sync into the same settings row as your nutrition goals, so Ojava Coach can see reviewed-day status without reading a separate browser-only diary flag.

A weekly digest reviews the last 7 days of logged food, your calorie reference, often-logged foods, food-group coverage, active minutes, and step context when those rows are available. The older weekly nutrition check-in still compares this week with the prior week for logged-day coverage, average calories, average protein, and week-over-week movement. Ojava Coach reads the check-in against the shared macro reference when your body and activity data are available. Those same food and water rows can also feed the weekly healthspan habit report alongside biomarkers, sleep, movement, recovery, and self-tracked habits, without requiring an active goal first. This is adaptive food-log and habit review, not a diet prescription.

Nutrition Progress Overview compares the current 7 days with the prior 7 days for logged-day calories, protein, carbs, and fat. Fitness > Nutrition also charts the last 14 days of reviewed calorie, macro, label-nutrient, and private streak patterns from the same rows, and Ojava Coach receives those finished trend values without recomputing your diary. This is private food-log pattern review, not a diet prescription, macro prescription, calorie target, diagnosis, treatment, or medical nutrition therapy.

When protein grams are logged, Ojava also shows a protein anchor score from your latest protein-logged day. It counts how many food entries reached a 20g protein anchor, caps the day at three anchors for a 0 to 100 score, and sends the same number to Ojava Coach. This is logged protein distribution only, not a personalized protein prescription. The source basis stays visible:

Your calorie and macro targets

Ojava calculates targets from your own numbers rather than a generic one-size-fits-all plan. From your weight, height, age, sex, and activity it estimates your resting metabolic rate and your total daily energy expenditure, then suggests a maintenance calorie figure and a protein, carbohydrate, and fat split to aim for. You can see these on the Nutrition targets card in Insights, and Ojava Coach references the same figures so the number on your screen and the number it talks about are always identical.

Energy needs (BMR and TDEE)

Your basal metabolic rate (BMR) is the energy your body uses at rest. Your total daily energy expenditure (TDEE) adds your activity on top. Ojava estimates both from your body metrics and activity level, and uses TDEE as the anchor for your maintenance calories. If you have not logged your weight and height yet, Ojava says so rather than inventing a number.

Adaptive calorie target (Pro)

Once you have logged meals and weighed in regularly for a couple of weeks, Ojava can back-calculate your real daily burn from your own data: your average intake compared with how your weight trend actually moved. That estimate appears as the “Estimated daily burn” trend on the Progress tab, and with the adaptive calorie target switched on (it is on by default; the switch lives in Goal settings), your daily calorie target updates once a week from that estimate instead of the static formula. Targets carry a small Adaptive tag whenever the automatic adjustment is active.

Guardrails are built in: adaptive adjustments are for adults only, never suggest a target below a safe intake floor, never push a deficit faster than about one percent of your bodyweight per week, and pause honestly when logging is too sparse to trust. A calorie target you set yourself is always left alone. General wellness guidance, not medical or dietary advice.

Protein, carbs & fat

Ojava suggests a macro split, how many grams of protein, carbohydrate, and fat to aim for in a day, scaled to your calorie target and your goal (losing, maintaining, or gaining). Protein is anchored to your body weight because it is the macro most people undershoot and the one most tied to maintaining muscle as you age. These are concrete coaching targets for everyday wellness.

Your own saved goals can override the starting point. Weekday-specific targets are useful for training days, rest days, travel days, or any routine where one daily number is too blunt. Exercise add-back uses your logged workouts and body weight when Ojava has enough data to estimate a burn, then applies your saved 0 to 100 percent add-back setting; if it cannot estimate the workout, it leaves the goal unchanged rather than inventing calories. Ojava Coach receives the same saved weekday schedule as a finished context line, including today’s target, upcoming override days, meal-goal count, nutrient target count, add-back setting, and carb display mode, so it can answer goal-calendar questions without calculating new targets.

When you have enough recent food days and body-weight entries, Ojava Coach can also prepare a small adaptive target-change draft for review. The draft carries the number of logged days, food entries, body weights, calorie gap, protein-reference percent, and weekly weight-rate evidence it used. It does not save anything automatically, and it does not appear when the recent history is too thin. Treat it as a check-the-settings prompt, not a prescription, medical nutrition therapy, or weight-management treatment.

Adjusting targets for pregnancy or breastfeeding

Calorie and nutrient needs change during pregnancy and while breastfeeding, and Ojava’s default targets are not built for either. If this applies to you, raise your saved calorie, protein, and macro goals by hand on the Nutrition targets card rather than relying on the weight-loss or maintenance default, and revisit them with your clinician as your pregnancy stage or breastfeeding routine changes. Ojava can still log meals, track patterns, and answer general nutrition education questions during this time, but it does not set a pregnancy or breastfeeding calorie target itself, does not diagnose a nutrient deficiency, and does not replace prenatal or postpartum guidance from your clinician.

Nutrition app imports

If a connected nutrition app writes calorie and macro totals into Apple Health, or you import a nutrition-app CSV with those columns, Ojava can summarize the source-provided totals beside your wearable context. Those imported totals stay separate from the food diary you review and log in Ojava, so they do not become verified meal entries or a prescribed nutrition plan.

MyFitnessPal meal-detail exports have their own reviewed import path in the Food Log. You export the CSV, upload it to Ojava, preview the parsed batch, and confirm the import. The preview names skipped-row reasons such as unreadable dates, implausible values, missing usable nutrition, missing water, empty progress rows, and row-limit overflow before anything is saved. Confirmed nutrition rows preserve serving detail when the export provides it, then behave like other Ojava food-log entries for nutrition rhythm, protein anchors, daily energy context, exports, and Coach context. Confirmed exercise rows can feed the same activity-adjustment explanation Coach uses for same-day energy context, and strength rows with sets, reps, and load save into the same strength log as manually entered lifting sets. Confirmed water rows save into your Water log as reviewed hydration entries.

Re-importing the same MyFitnessPal file is duplicate-safe. Before Ojava saves food, exercise, water, or progress rows, it checks your existing rows across the import date span and skips matching reviewed MyFitnessPal entries. Manual Ojava rows are left alone, even when they happen to share a similar date or nutrition value.

When a reviewed MyFitnessPal mobile nutrition export contains dated meal rows, Ojava Coach can also read a compact import summary: logged export days, latest-day calories and macros, serving examples when present, reviewed net-carb detail when the export includes fiber or sugar-alcohol clues, sample foods, meal-level totals, and missing fields. It is still a reviewed file import, not live MyFitnessPal account sync, native health-platform sync, a prescribed diet, or medical nutrition therapy.

Ojava also tracks the connected-app floor around MyFitnessPal. Setup answers can name MyFitnessPal, Fitbit, Apple Health, Google Fit, Health Connect, Garmin, Strava, Polar Flow, TrainingPeaks, MapMyFitness, MapMyRun, MapMyWalk, MapMyRide, Renpho Health, Withings, and Dexcom as cataloged source paths while still separating file import that works now from native or partner sync that needs activation.

For setup questions, Coach can also explain the source path itself: nutrition-app CSV import is ready when you have an export file, Apple Health and Health Connect nutrition paths are native-gated, and live partner sync or writeback stays off until partner access, destination-account consent, and audit trails are active. That setup status never turns imported totals into reviewed meal entries.

For MyFitnessPal, Fitbit, or Health Connect field questions, Coach can also read a reference-only partner sync contract. It explains that MyFitnessPal to Health Connect food is meal-summary context, custom MyFitnessPal meal headings map to Health Connect’s Other bucket, and water is one-way from MyFitnessPal to Health Connect. It also explains that MyFitnessPal to Fitbit food sync is link-date forward, individual food names are limited to MyFitnessPal Premium and Premium+ provider behavior, historical meals do not backfill, water is one-way from MyFitnessPal, and weight is a Fitbit and MyFitnessPal field behavior. Ojava uses this to answer what those providers document, not to open OAuth, store credentials, activate live sync, write to another app, auto-log food, or create medical nutrition therapy.

The same reference packet also keeps the current MyFitnessPal marketplace featured-app snapshot in view. It can name Fitbit, Garmin Connect, Strava, MapMyRun, and Runkeeper as featured entries from the June 30, 2026 snapshot, including the Fitbit GET link that points to MyFitnessPal's own authorize endpoint and Garmin Connect's marketplace INSTALLED label. Those labels are source-page facts only: they do not mean your Ojava account has connected those apps, and Ojava still does not open partner authorization, store credentials, or turn on live sync.

Ojava can also prepare a local food-name writeback readiness packet from reviewed diary rows for a future user-approved partner sync. The packet filters unsafe or generic names, removes duplicate candidates, leaves calories and macros out, and tells Ojava Coach that external writeback is still off. Ojava does not send food names to MyFitnessPal, Fitbit, Apple Health, Google Health, or any partner until partner access, destination-account consent, and an audit trail are active.

The Nutrition sync status card also shows a source-readiness slice for MyFitnessPal, Fitbit, and food-name writeback. It lists the local substitutes that are ready now, such as reviewed MyFitnessPal imports, reviewed Ojava Food Log rows, local food-name review, and source-total reconciliation, then names the owner or provider rails still needed before any live source sync, external writeback, or auto-log path could be reviewed.

Meal planner

The meal planner is the forward-looking companion to the food log: instead of recording what you already ate, you sketch what you intend to eat. Plan a day or a week by meal (breakfast, lunch, dinner, snack), note a focus for each (higher protein, lighter dinner, more vegetables), and use it as a simple structure to shop and cook against. It keeps planning and tracking in one place rather than scattered across notes apps.

Planned meals also generate a grocery list from the meals and ingredient notes you entered. The planner can keep serving, prep, diet preference, budget, cooking-time, cuisine, prep-mode, household count, shared-with notes, named portion splits, leftover portions, foods to avoid, allergy notes, pantry items already on hand, and optional calorie, protein, carb, and fat details with the planned meal. Ojava also reviews the meals, recipes, and custom foods you saved and can prefill user-reviewed prep ideas or swap ideas for repeated planned meals. You can generate a reviewed 2 to 15 day meal-plan draft from those saved items, with occupied meal slots skipped and existing avoid or allergy notes respected. Those ideas do not auto-save without your action: review the draft slots, edit anything you want, and then decide whether to add them. Those same preference, avoid, and allergy notes now filter Nutrition Coach food ideas before they reach Coach, so matching saved items can be omitted instead of replaced by model-invented foods. The filter removes matching ideas rather than declaring any food safe. This is a review aid, not a food-safety guarantee. When you actually eat a planned meal, log it to the food diary from the planner. Ojava writes that as a normal food-log row with the planned serving, preferences, household context, and nutrition numbers you entered, so it stays in the same diary, reports, exports, and Coach context as everything else you eat. If the planned meal has a date, that log action keeps the planned date so the planner can compare what was planned with the food rows logged for that same date and meal slot. You can also log the selected day of planned meals in one batch. Ojava skips planned meals that already match a same-day diary row and copies only that selected day into the same private food log for review, so a prepared day can move from plan to diary without one row at a time. The grocery panel can mark pantry matches as already on hand, keep reviewed amounts such as cups, cans, or pounds beside grouped grocery items, copy the reviewed needed/on-hand list as share text, or export it as a `.txt` file for your own shopping note. The same area also has an editable shopping list for groceries that are not attached to a planned meal yet. Type items line by line, mark pantry items as on hand, check items off while shopping, copy the reviewed list, or export it as a `.txt` file. When account-backed nutrition settings are active, the list follows your account and Ojava Coach can see a bounded grocery-list context line. Ojava also computes local grocery readiness from the same reviewed list: how many items still need a shopping pass, whether amounts are present, and whether share text is ready. Live provider status comes only from the server-backed connected-grocery card. When the Kroger runtime is active, that card can prepare one reviewed, consented cart handoff after you choose the exact store products. It can also show an export preview: an overall completeness percent, per-column coverage (item name, amount, normalized unit, planned meals, on-hand flag), which items still need an amount, and your amounts consolidated where they share a measure (for example two tablespoons plus one tablespoon become three tablespoons; one cup becomes 236.6 ml). It only combines same-measure units and never converts volume to weight, since that would require guessing an ingredient density, so mixed or unrecognized amounts are surfaced for your review instead. Ojava Coach can read the same completeness summary when you ask about your grocery list. Ojava does not create a public feed, send PHI, check out, charge, schedule delivery, accept substitutions, or place a grocery order.

As you add planned meals, Ojava summarizes plan coverage: how many meals are planned, how many days are covered, the next planned meal, prep-note count, recurring focuses, recurring preferences, household details, restrictions, and shopping ideas pulled from the meals and notes you entered. Household portion review can use a named split such as me 1, partner 1.5, child 0.5, plus leftover portions, to estimate how much to prep before anyone logs food. The Prep sessions card groups upcoming planned meals by date range, prep mode, repeated ingredients, and grocery readiness so the same meal-prep context is visible before you ask Ojava Coach. The planned vs actual card reviews recent dated meal slots, matched logged rows, open planned slots, and calorie or protein differences when both sides have numbers. Ojava Coach also gets a bounded meal-plan history review plus grocery readiness: recent planned meals, repeated meals, open slots, needed items, on-hand items, share-text readiness, named portion context, leftovers, standalone shopping-list items, simple store-section hints, and adjustment prompts such as reviewing an unlogged slot, rotating a repeated meal for variety, or adding planned calorie or protein details when comparisons are incomplete. Those same plan, prep-session, history, grocery-readiness, and planned-vs-logged summaries are available to Ojava Coach as general wellness meal-prep context when you ask nutrition questions. Prep ideas and swaps are based only on food items you saved or meals you entered. This is a planning aid, not a grocery order, prescribed diet, or medical nutrition plan.

The planner and Ojava Coach can also organize seasonal or event meal-pack readiness from the same user-owned materials. If you have holiday, travel, busy-week, training-day, or other occasion notes in your planned meals, Ojava can combine those notes with saved recipes, saved meals, custom foods, saved preferences, allergy notes, pantry context, and nutrition targets to name review-ready pack candidates. The packet is deliberately bounded: it does not copy a recipe catalog, scrape recipe sites, create an automatic meal plan, verify food safety, create a cart, prescribe calories, or provide medical nutrition therapy.

Fasting rhythm

The fasting log tracks the eating windows you choose for yourself and turns them into a recent rhythm summary: average completed fast length, longest fast, target-hit rate, streak, and in-progress timer progress against the saved window label. Ojava Coach sees those finished timing numbers too, so fasting questions use your logged windows and active timer without inventing a schedule. Ojava uses those numbers as context for your food timing and recovery patterns, not as a prescribed fasting protocol.

Start and stop controls make the fasting timer usable without typing timestamps, and preset chips such as 12:12, 14:10, 16:8, 18:6, and 20:4 fill the window label before you save. The active timer refreshes while the screen is open, so elapsed time stays visible without a page reload. If ending a fast cannot sync immediately, Ojava keeps a minimal pending end-time update for that fast and retries when the tab is online or focused again. The presets are labels for your own log, not recommendations to fast or change how you eat.

Fasting reminders use the same local-planning pattern as food and water check-ins. Ojava can plan an end-fast checkpoint from an active timer and schedule start reminders for the fasting windows you configured, while respecting quiet hours. If an end-fast retry is already pending for that timer, the checkpoint is suppressed so Ojava does not keep asking you to close a fast you already ended. Local reminder drafts use PHI-free copy such as opening Ojava to review your fasting timer. They are planning context only, not remote push delivery, medical fasting advice, adherence scoring, diagnosis, treatment, or medical nutrition therapy.

Ojava can also compare your own food timestamps with your saved fasting windows before the context reaches Coach. It flags food entries that overlap a completed or still-open fast, open fasting windows, and rows with unreadable times so you can clean up the diary before relying on it in a conversation. This is a timestamp review for your own wellness log, not a fasting prescription, diet plan, adherence score, diagnosis, treatment, or medical nutrition therapy.

When a fasting, eating-window, hydration, body-clock, or nutrition-rhythm question needs the bigger picture, Coach can now receive one fasting readiness recap. It combines your logged fasting rhythm, food-window consistency, reviewed water rows, same-day food timing, and source recovery or body-clock evidence into a bounded review packet with gaps and review questions. The recap does not tell you when to fast, eat, or drink, assess dehydration, monitor you in real time, diagnose, treat, or provide medical nutrition therapy.

Those same fasting-window rows can contribute to body-clock readiness when the question is about circadian rhythm, sleep timing, daylight, or eating windows. Coach receives them as source context only, alongside sleep timing, daylight, food timing, late intake clues, and recovery rows when present. Ojava does not tell you when to eat, when to fast, or when to sleep from that packet.

Water log

One-tap hydration logging with a running daily total. Hydration is easy to forget and easy to track, and seeing the total climb through the day is a small, low-friction habit that supports energy, recovery, and how you feel overall.

Ojava also turns same-day water entries into a simple hydration score against your optional daily water target, or a broad adult beverage reference when you have not set one. It only scores drinks you record and does not treat the number as a medical hydration assessment.

MyFitnessPal water CSVs can be reviewed in the same import panel as nutrition, exercise, and progress exports. Ojava converts supported units such as mL, liters, fluid ounces, ounces, and cups into manual Water log rows only after you confirm the preview.

Local reminder checkpoints show whether your morning, afternoon, and evening water habits are met, upcoming, due, or muted during quiet hours. The same saved target drives those checkpoints and the hydration streak card. When you ask Ojava Coach about nutrition, recovery, or daily habits, recent manual water entries and the same checkpoint status can appear in the patient snapshot as general wellness context. These are habit prompts, not push alerts or dehydration warnings.

Coach also receives a hydration digest from reviewed Water log rows, including recent row count, total and average mL per logged day, same-day progress against your saved target or a broad adult beverage reference, the latest entry, reminder status, and missing inputs. The digest is hydration habit context only: no dehydration assessment, fluid prescription, alerting, medical advice, diagnosis, treatment, or medical nutrition therapy.

Body metrics & weight trends

Log your weight, body-fat percentage, and waist measurement over time. Reviewed MyFitnessPal progress imports can also bring in extra measurements such as neck, chest, hips, thigh, arm, calf, forearm, and shoulders. Ojava shows compact history bars for each available measurement once readings exist, so you can see the direction instead of reacting to a single morning’s number. Body weight bounces around with water, food timing, and sleep, so the trend is the honest signal, not any one reading.

Where it has enough data, Ojava also puts body-fat percentage in a general healthy-range context and reflects your body-mass index (BMI), waist-to-height ratio, relative fat mass, body roundness index, and A Body Shape Index back to you. These are broad wellness reference points, not a diagnosis or clinical risk score, and BMI in particular is a population estimate that does not account for muscle mass, so read it as one data point among several.

Ojava Coach now receives those supported body-composition signals as a single readiness packet. It combines accepted body measurements, source-provided smart-scale rows, BMI, body-fat range context, body-shape indices, weight trend, missing inputs, and the boundary before the model responds. The packet is measurement context only, not a score, target, body judgment, diagnosis, treatment, weight-loss prescription, or medical nutrition plan.

The Body tab also supports progress photos. Add a JPG, PNG, or WebP check-in photo with a date and optional caption when visual context is more useful than another number. These photos save privately to your Ojava account in a private storage bucket, with a browser-only fallback if an upload, metadata save, or signed preview fails. They are for your own review and do not replace the body-measurement rows Ojava uses for trends and Coach context.

When photos are saved to your account, Ojava Coach can see only bounded metadata from that photo log, such as how many check-ins are present, recent check-in dates, and safe short captions. It does not receive image bytes, storage paths, signed links, or image files, and it cannot interpret the photos or judge body composition from them.

Coach also receives one body progress report when those rows exist: accepted measurement rows, reviewed MyFitnessPal progress-import context, compact measurement changes, and account-backed photo metadata. The report is self-tracking context only, not a target, body judgment, diagnosis, treatment, weight-loss prescription, or medical nutrition plan.

The Body tab also accepts manual outside aging-clock, pace-of-aging, and appearance-age result metadata. Those entries are optional, user-entered, and clearly labeled as outside results. Coach can use them only when you allow it, and it does not validate the outside method, infer anything from photos, or merge those values into Ojava's lab-based biological-age estimate.

Activity & calories burned

When you log a workout, Ojava can estimate the calories it burned from the activity type, duration, intensity, and your latest body weight, then fold that into your daily energy picture. Use exercise lookup when you want to start from a common activity such as a run, walk, ride, yoga, strength training, or a sport. Ojava fills the workout form with a starting duration, category, effort, and calorie estimate for review. The workout form previews the estimate before you save, and saved workout rows show the same estimate when enough data is available. Paired with your wearable activity and your food log, this rounds out the energy-in versus energy-out view without you having to do the arithmetic. When you repeat a familiar session, recent workout shortcuts can log it again from your own history through the same workout record path. The Workout tab also highlights recent bests from your loaded log, such as longest loaded session, longest loaded distance, fastest logged pace, and recent estimated strength 1RM when the entries support those numbers. Ojava Coach reads those same highlights as workout context, not as a prescribed target, performance prediction, or exercise clearance.

Coach also receives a workout-entry review packet from your recent workout and strength rows. It names which entries have duration, category, distance, reviewed source calories, reviewed step provenance, reviewed MyFitnessPal exercise-import context, and usable strength details, then names the gaps without turning them into a training plan, exercise clearance, performance prediction, or medical monitoring.

The Workout tab also has a weekly exercise view. It compares your logged active minutes and strength days with broad movement references, shows supported saved fitness goals such as weekly minutes, workout count, or strength days when they have numeric targets, and names the missing side when the week is partial. It is a tracker view for your own record, not a prescribed training plan or exercise clearance.

You can also save workout routine templates that you write yourself. Fill the workout fields, add optional strength items such as sets and reps, then save the routine for later. Those templates now follow your account when you are signed in, with browser storage as the fallback when account access is unavailable. Ojava Coach can see a bounded summary of the routines you authored, and when you ask about routine follow-through it can compare saved routines with recent workout and strength rows to show which templates have recent, stale, or missing log context. You can also place user-authored planned workouts on the Workout calendar, fill them from a saved routine, and later log them into the same workout and strength rows so Coach can review matched and open planned-vs-completed slots when you ask. Logging a routine still writes a normal workout row and its saved strength items back into your own tracker, so it is a faster way to repeat what you already authored. Repeated logged workouts can also appear as reviewable routine starters that you can save before logging again. Ojava does not score adherence, prescribe exercise, create load targets, predict performance, or clear activity.

Nutrition in Ojava Coach

Because your food log, targets, body trends, and goals all live in your record, Ojava Coach can read a finished adaptive macro review instead of doing the math in the answer. When enough history exists, Ojava combines your last week of logged food with the smoothed body-weight trend and the current macro reference, then names whether calories, protein, alignment, or missing history is the clearest focus. It also keeps the simpler context: your current goal, saved meals, recipes, account-backed custom foods, planned meals, recent steps when present, meal-balance signals from complete logged macro rows, saved per-meal calorie-goal progress when those meals have reviewed calories, same-day meal macro ratios from reviewed protein, carb, and fat rows, daily macro remaining from your saved daily targets, how your protein intake compares to its target, how a week of eating lines up with your training load, whether your logged protein is clustered into enough protein anchors, whether later caffeine, alcohol, or heavier meal clues line up with recent recovery rows as association-only context, which label nutrients have a 7-day focus, whether recent accepted food rows have complete sources, servings, macros, and label nutrients, and which foods contributed most or least to logged calories, macros, net carbs, and the expanded label-nutrient set. Browser-local favorites stay local unless the same food also appears in your account-backed saved templates or recent food log. The Nutrition Coach review panel shows those deterministic signals before you hand the question to Coach. When your own meal-plan notes include preferences, foods to avoid, or allergy notes, Coach sees that as a review filter on saved food ideas. It cannot certify that a food is safe, medically appropriate, good or bad, or allergy-safe. When exact HEI-2020 constituent rows are reviewed, Coach can receive the finished Healthy Eating Index 2020 score or missing-input list from Ojava’s deterministic calculator, but it does not infer HEI from ordinary food logs. It gives confident, plain wellness coaching grounded in your own numbers, and when something is missing it tells you what to log rather than guessing.

When you explicitly ask for broader Nutrition Coach food ideas, Coach can also receive request-scoped public food-label candidates from the public food database. Your own custom foods, saved meals, recipes, and planned meals stay primary. Public label rows are idea candidates only, may be incomplete or stale, and should show their source plus missing serving, macro, or label-nutrient fields before you decide whether to save or log them. They are not medical nutrition therapy, a diagnosis, a treatment plan, a calorie prescription, or a safety guarantee.

Coach also gets the same deterministic activity-adjustment state as the diary: add-back off, partial 0 to 100 percent add-back, missing same-day context, wearable active calories already representing activity, signed source adjustment including negative source adjustment, activation gated, or active with reviewed workouts. When food rows, workouts, or wearable movement days are present, it can also read association-only meal timing and movement context. That context may describe nearby food, calories, protein, and missing inputs, but it does not grade food, infer causation, prescribe timing, or create a workout fueling plan.

Nutrition Progress Overview compares the current 7 days with the prior 7 days for logged-day calorie and protein averages, logging consistency, expected meal-slot coverage, and simple direction trends. A Nutrition Progress Report can also compose that overview with the printable diary report, reviewed source-provenance counts, and body progress context before Coach answers. It fails closed when the diary is too thin and stays descriptive: no adherence score, calorie target, diet prescription, weight-loss treatment, or medical nutrition therapy.