I was two years post-military, forty-something, and dealing with two herniated discs from a combination of parachute landings and the general accumulated abuse of a career spent doing things that are hard on spines. I had movement restrictions. I knew what I could and couldn't do. I just needed help programming around it.
I tried using a general-purpose AI assistant as a training coach. First session: I gave it my full background. Herniated discs at L4-L5 and L5-S1. No loaded spinal flexion. Limited loaded extension. No heavy deadlifts. It absorbed all of it and put together a program that actually worked around those restrictions. I was impressed.
Second session, new conversation: "Let's start with some barbell squats."
It had forgotten everything. There was no memory. The restrictions I'd spent time explaining were gone. Every conversation started from zero, which meant I was either re-explaining my entire medical history every session or trusting that this session's program was built for a healthy spine that didn't exist.
That's why I built Body by AI.
The Memory Problem With General-Purpose AI
General-purpose AI tools like ChatGPT, Claude, and Gemini are designed for conversations that reset. This is fine for most use cases — you ask a question, you get an answer, you close the window. The statelessness is a feature in most contexts.
It's a safety problem in fitness coaching.
Your medical history is not something that should need to be re-explained every session. Your herniated disc doesn't go away between Monday and Wednesday. Your knee replacement from three years ago doesn't magically unhappen because you started a new chat window. Your allergies, your medications, your injuries, your physician-imposed movement restrictions — all of it is relevant to every single workout and nutrition recommendation, forever.
When a general-purpose AI forgets these things, it's not a minor inconvenience. It's a gap between what it thinks it knows about your body and what's actually true. And in that gap, you get programs that are wrong for you. At best, you catch them and re-explain. At worst, you trust the recommendation and get hurt.
What Persistent Memory Actually Means
BBA is built on a different architecture. Your health history is stored in your profile database, not in the conversation context. Every time you start a coaching session, that profile is injected into the coach's context. The coach starts every conversation knowing your herniated discs, your medications, your food allergies, your current injuries, your surgical history, and your physician restrictions — because that information is always there.
This isn't a technical nicety. It's the foundation of what makes coaching safe.
The difference in practice: on day 1,825 of your BBA account, your coach knows about your herniated discs just as clearly as on day 1. Not because it "remembers" in a human sense — because the information is in your profile and is present in every interaction. The coach never has a session without it.
When your situation changes — a new injury, clearance from your PT to return to a movement, a new medication — you update the profile. From that point forward, every recommendation reflects the updated reality. The history doesn't disappear. It accumulates.
What Gets Stored
It's not just injuries. Your BBA profile stores:
Medical history: current injuries with prohibited movements and pain levels, surgical history with movement implications, active medications with exercise and nutrition relevance, physician-imposed restrictions with clearance timelines
Nutrition context: food allergies and intolerances stored as hard exclusions, dietary restrictions (religious, ethical, medical), nutrition goals and targets
Training history: your exercise history, what equipment you have access to, your performance benchmarks over time, your progression through previous programs
Personal context: your schedule constraints, your training preferences, your goals and how they've evolved
All of this is present in every conversation. Not as a summary you have to provide. As a structured profile that the coach uses automatically.
The Conversation I Should Have Had
Here's what the coaching conversation looks like in BBA when I report my herniated disc history at intake:
"You've mentioned herniated discs at L4-L5 and L5-S1. I'm marking these in your profile permanently. In practice, this means: no loaded spinal flexion — so no good mornings, no conventional deadlifts from the floor, no sit-ups or crunches. Limited loaded extension — so we'll be careful with any exercises that compress the lumbar spine under load. I'll build your lower body work around hip hinge patterns that you can perform with neutral spine, box squats with reduced depth if squatting is comfortable, and single-leg variations that reduce spinal loading. Can you tell me what ranges of motion are currently comfortable and which movements cause symptoms? I want to build from what's actually working for your spine right now."
That conversation happens once. The restrictions it establishes are there forever, unless you tell the coach something has changed.
Compare that to the general-purpose AI experience: that conversation happens every session, or not at all, because you got tired of having it and hoped the AI would figure it out.
The Stakes of Getting This Wrong
Fitness is one of the domains where incomplete information about a person leads to real physical harm. A nutritionist who doesn't know about your shellfish allergy is dangerous. A physical therapist who doesn't know about your previous ACL repair is dangerous. A fitness coach — AI or human — who doesn't know about your herniated discs and programs loaded spinal flexion is dangerous.
The fact that AI tools exist that will enthusiastically prescribe exercise programs without any knowledge of the user's medical history, and that reset that non-knowledge every session, is a design choice that prioritizes ease of development over user safety.
BBA was built specifically to solve this. Not as a feature — as the foundational premise. The coach works from your complete history, always, because coaching without your history isn't coaching. It's guessing.
Your coach never forgets. Ever.