Current truth
Baseline not captured
Baymax can guide general next steps, but personal targets stay locked until the minimum baseline is entered.
A
AYUME · Consumer #1
M0 · session-only state
Body transformation · weight management · whole-person loop
Baymax works with you, every day.
AYU is now your single body-transformation surface. Baymax coordinates food, movement, strength, recovery, measurements and progress, then adapts from evidence instead of reacting to one bad meal or one scale reading.
Current privacy + safety boundary
This first implementation keeps your entries only in this page session and sends nothing from these controls to a health database. Refreshing or closing the page clears them. AYU does not diagnose, prescribe or change medication; urgent or emergency symptoms require appropriate professional or emergency care.
◉
Baymax · AYU Co-OperatorSense → plan → guide → verify → adapt
Today’s focus
Create the baseline
One useful action first: capture current measurements and routine. Do not start with an aggressive deficit.
Blocker
Missing personal baseline
Resume condition: complete the baseline in Today. Secure persistence is a separate gate and does not block this session.
Baymax Today
Your next best action
Complete your baselineAYU needs minimum current context before personalizing today.
Source: current session state
Baseline · first-consumer onboarding
Give AYU enough truth to personalize safely.
No target calories are created until this baseline is sufficient. These fields are session-only in M0.
Today plan
Waiting for baseline
Complete the baseline above. Baymax will then create a conservative first-day plan without pretending it knows your exact energy needs yet.
Food capture
Log what actually happened.
Use plain language or start from a photo. M0 stores entries only for this session and does not upload the image.
Camera-first capture is ready. This static M0 does not yet run an AI nutrition resolver, so AYU will not invent calories or macros from the photo.
No food photo captured.
AURA bridge
Verified food when AURA knows it.
AYU estimates only when verified food truth is unavailable. If an AURA Food Passport exists, it should become the food source and AYU adds only the private “for me” interpretation.
No AURA Food Passport bound in this session. M0 records a reference only; verified resolver binding remains a separate acceptance gate.
Default architecture
Protein + plants + controlled energy density
Baymax starts with ordinary Indian meals: protein at each main meal, vegetables/fruit/fibre, mostly whole foods, and portions adjusted from real progress rather than a crash diet.
Restaurant, festival or high-calorie meal? Recover at the next meal. No starvation or punishment workout.
Hydration
One-tap water
Keep hydration capture trivial. This is a session counter, not a medical hydration prescription.
0Glasses logged
Session meal log
What AYU has heard today
Nothing logged yet.
Strength
Preserve muscle while fat falls.
AYU’s default full-body pattern is squat/lunge, hinge, push, pull and core/carry. Progress load, reps or difficulty only when recovery and technique support it.
Your exact weekly structure will appear after baseline.
Daily movement
Build from your real baseline.
No automatic 10,000-step rule. Baymax progressively increases walking/activity from what you actually do, with short post-meal walks as an easy option.
Today movement
Log completion
No movement update yet.
Measurements
Trend, not one reading.
Baseline weight and waist will appear here after onboarding. Longitudinal trend requires accepted persistent storage.
Photo-First
V-taper lineage retained.
AYU’s existing Photo-First Body Intelligence remains part of this mission. M0 does not upload new body images because secure personal-health evidence storage must be accepted first.
Body update
Add a current session check
No session check recorded.
Recovery modifier
Bad recovery changes the plan; it does not create guilt.
No recovery check yet.
Current M0 evidence
Session progress board
NoBaseline
0Meals logged
—Movement
—Recovery
Longitudinal weight/waist/photo trends are deliberately not faked in M0. They begin only after secure authenticated persistence is accepted.
Today timeline
One chronological health context
Session events keep source/type visible instead of mixing user report, captured observation and AURA references.
No session events yet.
Adaptation rule
Change the smallest useful variable.
Appropriate trend + good recovery → preserve the plan. Genuine plateau + good adherence → small adjustment. Fast loss + poor recovery/performance → reduce aggressiveness. Adherence blocker → fix the blocker first.
Reusable extraction
Consumer #1 teaches the engine.
AYU extracts schemas, blocker patterns and decision logic—not your personal health payload—into the reusable Weight Management Core.
AYU YAMA
Health consequence gates stay stronger than ordinary automation.
AYU may support general wellness, weight management, preparation and follow-through. It must keep user report, device observation, model inference, medical evidence and clinician judgment distinct.
Professional gate
Do not auto-execute treatment changes.
Medication changes, treatment decisions, severe symptoms, pregnancy-related concerns, major disease constraints, eating-disorder concerns and other clinically material situations require appropriate professional involvement.
Data boundary
Personal health remains isolated.
Shared ZIVYAN infrastructure does not give unrelated PH domains access to personal health data. Blockchain-capable provenance may attest privacy-preserving eligible events, never expose raw health payloads on-chain.
Emergency note: AYU is not emergency care. If you have severe or rapidly worsening symptoms, chest pain, severe breathing difficulty, loss of consciousness, signs of stroke, serious injury, or another emergency, seek appropriate local emergency services or urgent professional care.