mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-16 23:33:29 +00:00
Merge branch 'feat/v125-self-description-docs' into release/v1.25.0
# Conflicts: # docs/api/mcp-capabilities.md
This commit is contained in:
commit
fb580f4725
17 files changed
+248
-11
No files matched your search
@@ -28,7 +28,10 @@ them up front):
|
||||
4. **Data and context only.** The server ships facts; it never returns a
|
||||
diagnosis, clinical verdict, risk score, or treatment change. The
|
||||
assistant narrates the facts and leaves clinical judgement to the
|
||||
user's clinician.
|
||||
user's clinician. This mirrors HealthLog's project-wide self-description
|
||||
standard: the app is a personal health record-keeping and wellness tool,
|
||||
not a medical device, and nothing it surfaces — here or in the UI —
|
||||
diagnoses or treats.
|
||||
|
||||
Discover before fetching: call `list_metrics` (or read the
|
||||
`healthlog://measurements/inventory` resource) first to see what exists,
|
||||
@@ -106,7 +109,10 @@ surfaces a signal only when the user has recorded it; `fetch metric:<KEY>`
|
||||
hydrates it). Each carries its unit and population reference band from the
|
||||
single signal registry; absence is the usual `{ present: false }`. They
|
||||
sit off the Coach data inventory by design, so `list_metrics` /
|
||||
`get_metric_series` do not enumerate them — use the reads above.
|
||||
`get_metric_series` do not enumerate them — use the reads above. A new
|
||||
signal is declared once in the in-app signal registry and shows up across
|
||||
the metric tools, correlations, and the FHIR map together, so the MCP
|
||||
surface never advertises a signal the record can't return.
|
||||
|
||||
The **longevity lab panel** (ApoB, Lp(a), hs-CRP, HbA1c, fasting glucose,
|
||||
fasting insulin, eGFR, GGT, ferritin, omega-3 index) is reached like any
|
||||
@@ -118,10 +124,18 @@ curated biomarker catalogue.
|
||||
**Off the MCP surface by construction.** The PHQ-9 / GAD-7 mental-health
|
||||
screeners (item content and totals) are excluded from AI / MCP, and the
|
||||
environmental-context signals (`ENV_*`: temperature, sunshine, daylight,
|
||||
precipitation, barometric pressure) are off MCP in v1. None of them
|
||||
resolve through any read tool — they are not on the MCP exposure
|
||||
precipitation, barometric pressure) are off MCP in v1. The structured
|
||||
records (allergies, family history) and the inbound-document store are
|
||||
deliberately not exposed either: the document pipeline extracts facts for
|
||||
the user to confirm in-app rather than streaming them to a model. None of
|
||||
them resolve through any read tool — they are not on the MCP exposure
|
||||
allowlist.
|
||||
|
||||
This mirrors HealthLog's project-wide self-description standard: the MCP
|
||||
surface ships data and context, never a diagnosis, clinical verdict, or
|
||||
treatment change — the assistant narrates the facts and leaves clinical
|
||||
judgement to the user's clinician.
|
||||
|
||||
## Resources
|
||||
|
||||
Read-only context the assistant can attach alongside tool results. Like
|
||||
|
||||
@@ -198,6 +198,30 @@ The Coach drawer surfaces a "Local" badge when generation resolves
|
||||
to the local provider, so users who pinned a local endpoint can see
|
||||
at a glance that their context stayed on the host.
|
||||
|
||||
## What the Coach is — and isn't
|
||||
|
||||
The Coach is an informational assistant that works from your own
|
||||
logged data. It is not a doctor, what it says is not medical advice,
|
||||
and it does not diagnose, prescribe, or change treatment — those
|
||||
boundaries are written into its system prompt as safety contracts, not
|
||||
left to chance. It describes patterns observationally ("your resting
|
||||
heart rate has been rising over 14 days"), never as a verdict about a
|
||||
named condition, and it defers diagnosis, dose, and drug-interaction
|
||||
questions to a healthcare professional. This is HealthLog's
|
||||
project-wide self-description standard: a personal health
|
||||
record-keeping and wellness tool, not a medical device. The same
|
||||
non-diagnostic framing governs the daily briefing, the insights, and
|
||||
every surface that turns your data into words.
|
||||
|
||||
The Coach can also reach out proactively — a calm, once-a-day morning
|
||||
check-in when there is something genuine to surface (a recovery trend
|
||||
easing off, blood pressure running a touch high). The nudge is warm
|
||||
and localized, references the focus by category rather than quoting
|
||||
your own words back, and stays silent when there is nothing real to
|
||||
say or when you have engaged the Coach recently. It is an invitation,
|
||||
never a streak-guilt prompt, and it inherits the same non-diagnostic
|
||||
boundaries as the chat.
|
||||
|
||||
## Caching contract
|
||||
|
||||
Two caches sit in front of every provider call so generation budgets
|
||||
|
||||
@@ -16,6 +16,10 @@ already installed, longer if a TLS-fronted public hostname is in scope
|
||||
hold a 1.5 GB upload in `/tmp` while it parses.
|
||||
- **Outbound HTTPS** to `ghcr.io` (image pulls) plus whichever
|
||||
integration endpoints you plan to enable (Withings, OpenAI, etc.).
|
||||
The opt-in environmental-context module additionally reaches
|
||||
`api.open-meteo.com` for weather and daylight; it stays off until you
|
||||
enable it and set a home location, and every outbound call goes
|
||||
through the SSRF-guarded egress wrapper.
|
||||
- **Optional but recommended:** a reverse proxy that terminates TLS
|
||||
and forwards to `http://localhost:3000` (Caddy, Traefik, Nginx
|
||||
Proxy Manager, Coolify, or bare Nginx — see `reverse-proxy.md`).
|
||||
|
||||
Reference in new issue
Block a user