> For the complete documentation index, see [llms.txt](https://saviorofhealth.gitbook.io/saviorofhealth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saviorofhealth.gitbook.io/saviorofhealth-docs/overview/problem.md).

# 2. The Problem

**Health behaviour lacks immediate feedback.** The benefit of drinking enough water, sleeping properly, or eating better arrives slowly, if at all. A person who sleeps seven hours tonight feels much the same tomorrow as one who slept five. Nothing in the moment signals that the action mattered, so habits rarely survive an ordinary week. Reminders add noise without adding a reason to continue.

**Survey data is shallow and hard to trust.** Traditional health surveys are one-off questionnaires with no longitudinal context and no measure of whether a respondent read the question. A panel answers once and is dissolved, and the next study starts from nothing. Nobody can tell whether the answer was considered or a reflex tap, so researchers pay for sample size and hope that volume will wash out the noise. Volume does not fix a question that was never read.

**Everyday health data is scarce where it is most needed.** Hospital records describe episodes of illness, not daily life, and they are locked to one institution, one format, and one consent. The daily signals that precede illness, such as sleep, hydration, diet, movement, and mood, are generated constantly but captured almost nowhere in a structured, consented, and reusable form.

**Reward schemes attract the wrong participants.** Apps that reward presence rather than information attract automated accounts, because presence is easy to fake and information is not. Rewards flow to scripts, the data becomes unusable, and the members who remain are under-rewarded. Section 6 describes the scale of this problem on the Platform and how it is being addressed.

The Platform is built as infrastructure for the gap these three problems leave: a consented, longitudinal stream of self-reported daily health data, collected through a consumer app that members use every day, and made usable for organisations through threshold-suppressed outputs (Section 3).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://saviorofhealth.gitbook.io/saviorofhealth-docs/overview/problem.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
