Medications, allergies, conditions, symptoms, appointments, procedures, labs, vaccinations, vitals, measurements, sleep, activity and attachments. One coherent home for a history otherwise scattered across portals, apps, bottles and memory.
Most health apps interpret. They take what you logged and hand back a verdict, a score, or a suggestion whose reasoning you cannot see. BodyLore records the thing that happened and keeps the interpretation separate from it, because the record is what you will still need in ten years and the interpretation is not.
Suggestions run condition to symptom and never the reverse, which is the enforceable direction. A record is keyed on the person it is about rather than on whoever is holding it today, so it can change hands without moving.
It is one of three apps that talk to each other directly, and that list is closed. What an integration is permitted to see is enforced rather than described: enabling one is not the same as handing over a category.
The data layer, the API over both credentials, the observation log, scoped tokens with the permission model enforced, the identity split with handover, insights, the injection map, encrypted attachments, the emergency card, an export of the whole record, and an OpenAPI document generated from the schemas that validate the requests, so it cannot describe a field the handler will not accept.
What remains is the deploy directory as a runbook, and the open findings in a security review that says what it did not cover.
Handling of data is covered in the Locke Werks Privacy Policy. For access, or a conversation about what it would take to use this, write to nyx@lockewerks.com.