mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Measured against the route declarations on this tree: The health-background section names allergies, family history and the profile facts, and omits visits, the practices behind them and the vaccination record — all three of which `scope.ts` puts in that section, so a grant is narrower on the page than it is in the product. "Aggregate surfaces appear only on a whole-record grant" is true and incomplete: a whole-record grant does not open them equally either. The daily digest and the dashboard's snapshot answer at read, the health score, the dashboard's summary and the insights need manage. The write level lists seven creates against twelve WRITE declarations. A visit, a practice, a vaccination dose and the booster reminder it suggests were missing, and the guide said nothing about the creates that need manage inside a section a write grant can otherwise add to, or about the vault taking no delegated write at any level. "Exports, the health-record archive" sat under what a delegate cannot reach, while `POST /api/export/health-record` answers at manage on a whole-record grant and its own comment says why. The row is about the full exports and the encrypted archive; the doctor report is named as the exception it is. The sharing-denial guard's docblock carried the same class of stale claim — 116 fenced modules, 26 never published — and that gap is closed on this tree. The caveat becomes an assertion: a new leg recomputes the fenced modules from the route sources and requires every one to be published, and it names no number, because a hard-coded figure is what turned the paragraph into a false statement about the contract. It fails when a published path is withheld from it.
docs/ — internal reference + operator playbooks
The user-facing documentation lives at https://docs.healthlog.dev — that's the canonical surface for self-hosting guides, integration walkthroughs, AI-provider setup, and the doctor-report workflow.
The files in this directory are the internal operator playbooks, audit notes, and machine-readable specs that ship alongside the source:
api/— the OpenAPI 3.1 spec for the native-client subset (iOS DTO codegen target). Seeapi/README.mdfor the preview commands. Also home to the MCP-server contract:api/mcp-capabilities.md(tools, resources, prompts, write model) andapi/mcp-skills.md(building a connector / skill).ops/— operator runbooks: deploy, backup / restore, encryption-key rotation, password reset and account recovery, env checks, TLS pinning, data repair. These are what an operator reaches for during an incident.self-hosting/— horizontal-scaling notes (HEALTHLOG_PROCESS_TYPE=web|worker|all) and the deploy-pipeline recipe. Routine install steps stay ondocs.healthlog.dev. Includesself-hosting/mcp.md— enabling the off-by-default MCP connector and pointing Claude.ai / ChatGPT / Claude Desktop at it, andself-hosting/sso.md— OIDC SSO login: IdP setup, the identity-pinning security model,OIDC_ONLYconsequences, and the break-glass runbook. Alsoself-hosting/geolite2.md— bringing your own offline GeoLite2 databases viaGEOLITE2_DIRinstead of sending login IPs to a third-party lookup. Andself-hosting/account-sharing.md— letting one account on the instance open another's health record: the three access levels, the eight sections a grant can be narrowed to, managed profiles for somebody with no login and the guardians who look after them, what revocation does and does not undo, and which trust properties of the instance are unchanged by any of it.migration/— migration notes. Currently only v1.3 to v1.4; later releases are covered byCHANGELOG.mdand https://docs.healthlog.dev.integrations/— per-integration reference (Withings, Fitbit, Google Health, WHOOP, Apple Health, AI providers, data import).adr/— architecture decision records.security/— threat-model notes.diagrams/— architecture diagrams rendered through docs.healthlog.dev.releases/— release imagery.apple-store-connect-checklist.md— the iOS submission gate.codex-protocol-spec.md— Codex / ChatGPT OAuth protocol reverse-engineering notes.ui-guidelines.md— UI / a11y house style.
If you're a self-hoster looking to spin up an instance, start at https://docs.healthlog.dev or jump to the Quick Start in the project README.