Product 03 — the analysis inside BodyLytiX
BLX Data Science
The analysis being built inside BodyLytiX. It works out what is normal for one person, measures how far today sits from that, looks through the record for anything that might account for the gap, and attaches a confidence level to whatever it ends up saying.
What it is
Part of BodyLytiX, not a product of its own.
BodyLytiX is the product: a consumer health application that reads data from wearables and health apps, and the only one of these two entries a person could ever sign up for. BLX Data Science is the part inside it working out what the data supports and, more often, what it does not. It is in development along with the app, is not offered separately, has no customers of its own, and there is nothing here to sign up for.
It has a page here because the method is worth setting out in detail.
An example of how it is designed to work, rather than something observed. Say your resting heart rate this morning sits four beats above your own six-week average, further out than your usual day-to-day spread, and the record holds a flight two days ago with nothing logged for dinner. It would say the travel is consistent with the rise, mark the missing meal data as a gap, and put medium confidence on the whole thing. When nothing in the record fits, that is the answer it is designed to give.
The design principle underneath is a constraint rather than a feature:
The system produces the evidence. The language model puts it into words. Grounding, baselines, trend analysis, confidence scoring and anomaly detection all happen before a sentence is written.
The shape of the data
Six pillars, grouped by how they behave.
The correlations worth having run across pillars rather than within them, which is why the contextual and women's-health pillars cannot be stubs. A single-pillar reading is something a wearable already gives you.
Objective, continuous
Activity and movement. Sleep, including heart-rate variability and recovery. Nutrition and supplement intake.
Objective, periodic
Body composition, blood pressure, blood work — measured occasionally, and treated as a different kind of signal from a daily one.
Contextual
Mood, stress, energy, injury, illness, travel, bereavement. The pillar that carries the reason, and the one most often missing.
Women's health
Cycle, fertility, pregnancy, menopause — a first-class pillar, because the correlations it participates in cannot be produced without it.
The discipline
Four rules that decide what may be said.
- Grounding before inference. Reasoning uses data the system actually holds. If meal timing was never recorded, a late meal cannot be named as a driver; the correct output is that the data is missing and worth confirming.
- Confidence is a tier, not a tone. Every conclusion is classified high, medium or low confidence, or unknown, and unknown is a permitted answer.
- Correlation is not causation, in the wording too. "Likely contributed to", "is consistent with", "appears to correlate with" and "requires confirmation" are allowed. "Caused" is not, unless the data supports it.
- Unexplained is a result. When signals move sharply and nothing in the record accounts for it, the system flags the uncertainty instead of forcing a lifestyle story onto it.
Behind each conclusion sits an evidence trail: which signals moved, how far from that person's own baseline, which sources were used, what context was missing, whether this is one day or a repeated pattern, and how many earlier examples support it. A single day cannot be presented with the weight of a six-week pattern.
Honest state
Specified and under implementation.
The architecture standard is written down and locked; the build against it is in progress. No outcome, accuracy figure or customer result is claimed here, because none has been recorded in a form we would publish.
-
The reasoning architecture standard
Data grounding, confidence tiers, permitted and forbidden language, anomaly handling, the evidence trail, and the split between the deterministic layer and the language model. Locked as a technical specification and used to hold the build to account.
Written and in force -
The reasoning implementation
A coordinator over per-pillar context processing, with user history and context retrieval, replacing an earlier single-prompt approach. In implementation against a defined acceptance gate and a structured question-based evaluation.
Being validated -
Capability claims about the product
What BodyLytiX may publicly say it does is held in a product truth register. Capabilities are seeded as planned or draft, and one moves beyond planned only when a person has recorded observed behaviour and proof. At the last reading, none was approved.
Governed -
Availability of BodyLytiX itself
Pre-launch. Its roadmap, pricing and release dates are the product's own to announce and are not stated here.
Not announced
On data
No personal health data, user record or health research result appears anywhere on this site. The heart-rate example above is an illustration of the method, not a reading from anyone.
Built by Vivenso Labs · The product it sits inside: BodyLytiX