> For the complete documentation index, see [llms.txt](https://4heal.gitbook.io/4heal-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://4heal.gitbook.io/4heal-1/introduction/what-4heal-solves/three-core-components.md).
# Three Core Components
#### **1. Wearable & Sensor Ecosystem — The Real-World Interface for Multi-Source Data**
\
4Heal supports a wide range of wearables and health data sources, including:
* Smartwatches
* Fitness bands
* Rings
* Home medical monitoring devices
* Medical check-up reports
* Medication records, etc.
These devices and data sources are responsible for:
* Capturing bodily signals;
* Recording behavioral changes;
* Providing long-term trend data;
* Acting as the input side of the behavior–health feedback loop.
They are **not** the center of the system.They are the **interface layer** that keeps the body connected to the digital world.\
\
4Heal’s ecosystem does **not** depend on any single device.In the future, more types of health hardware and measurement capabilities will be supported.
***
#### **2. Health Intelligence Engine — Cognition & Reasoning for Individual Health**
\
To move beyond mere “logging and display”, 4Heal has designed a complete **health intelligence engine**.
This engine builds a **Digital Twin** for each userbased on their long-term health trajectory, data characteristics, and behavior patterns.
This Digital Twin has the ability to:
* Understand long-term trends;
* Reason about current health status;
* Model the causal relationship between behaviors and bodily responses;
* Identify risk directions;
* Plan personalized actions;
* Continuously optimize via feedback.
Every change in your daily life —
whether it’s sleep variability, stress fluctuations, dietary adjustments, or exercise patterns —is continuously fed into the learning process of your Digital Twin,
> allowing it to gradually build a **Personal Physiology Model** for you.
***
#### **3. 4Heal Depin Network — An Open Network that Turns Health Contribution into Value**
4Heal Depin Network is an **incentive-driven, global health intelligence construction network**.\
\
It is a health intelligence system **jointly built by users**.
Through a transparent incentive mechanism, we encourage users to:
* Continuously contribute **real health data and behavior signals** via wearables;
* Help improve the overall intelligence level of the 4Heal health concierge.
This is **not** the traditional Depin model\
that relies on device quantity, coverage, or raw compute.\
Instead, it is a new paradigm of:
> **“Health-Intelligence Depin”**
>
> Rewarding users → for contributing health data and behaviors → to co-build a global health intelligence system (AI Health Agent + Digital Twin).
In this network, wearables are **not “nodes”** —they are **tools that allow users to contribute real-world health signals**.
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://4heal.gitbook.io/4heal-1/introduction/what-4heal-solves/three-core-components.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.