Skip to content

FitCrew / BodyOS V2.0

Latest
Latest

Choose a tag to compare

View all tags
@flicy flicy released this 09 Aug 05:00
v2.0.0
192eb23
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

FitCrew V2：把身体数据、感受与科学知识接进 BodyOS / FitCrew V2: Body data, perception, and scientific knowledge in BodyOS

中文

FitCrew 与 BodyOS 是什么

FitCrew · AI 健身管理专家。BodyOS 是用户在飞书中接触到的私人生活方式教练。

FitCrew V2 不只是“接入更多数据”。它把 Apple Watch、鱼跃血糖仪、用户当下的身体感受和科学知识放进同一段持续对话，让 BodyOS 帮助用户理解可能的生活方式关系，并把复杂信息转化为今天能执行的小行动。

V2 新增的四项能力

  1. Apple Watch 与鱼跃血糖数据：经用户授权，iPhone HealthKit Bridge 读取已经进入 Apple Health 的 Apple Watch 与鱼跃 Anytime 5 Pro 数据。
  2. 食物 × 血糖 × 身体感知：在 BodyOS 私聊中，把今天吃了什么、血糖如何变化和主观感受放在一起讨论，获得生活方式层面的解释与行动建议。
  3. 群聊通用健康互动：在群聊中回答通用饮食、训练、睡眠与控糖知识问题，也参与打卡和日常健康互动。
  4. 三本科学书籍指导：私人知识库收录《控糖革命》《百岁人生行动手册》《睡眠优化完全指南：科学与实践》，在系统可取得来源时用于辅助回答。

群聊与私聊怎么分工

  • 群聊用于通用知识、共同打卡和健康互动。群聊不会读取个人健康数据、私聊内容或私人知识库，也不会公开原始健康数值。
  • BodyOS 私聊用于对应用户的个人分析。只有用户主动授权后，BodyOS 才会在最小必要范围内使用其数据，讨论食物、血糖、睡眠、训练与身体感知。

数据、隐私与医疗边界

  • Apple Health 与 Apple 设备不是使用 FitCrew 的前提；健康授权始终可选、可撤回。
  • 用户、设备和健康类别同意分别绑定；跨用户上传与调用会被拒绝。
  • 原始健康字段加密保存；模型只接收完成回答所需的聚合特征、意图与知识摘录。
  • BodyOS 提供生活方式指导，不提供疾病诊断、治疗或用药建议，也不能替代医生。

已验证的工程状态

  • Python / policy、Swift Core 与 iOS Simulator CI 已通过。
  • 生产严格 HTTPS 健康检查已验证；https://124.156.218.104/healthz 当前报告后端版本 v2.0.0-alpha.1。
  • 受控邀请、一次性配对、按用户隔离、授权撤回以及群聊隐私边界已进入代码基线。

这些证据验证的是构建、策略、隔离与部署连接性，不代表任何个人健康结果。

尚未完成

  • TestFlight 外部分发尚未完成。
  • 受邀测试者的完整真机验收尚未完成。
  • 真实世界的 16 天实验尚未完成，当前没有可对外宣称的实验结论。
  • 真实健康数据、身份、设备令牌、配对信息和私人书籍原文不会进入公开 Release 或 Git。

English

What FitCrew and BodyOS are

FitCrew is the AI fitness management expert. BodyOS is the private lifestyle coach people meet in Feishu.

FitCrew V2 is not simply “more data integrations.” It brings Apple Watch, Yuwell glucose-monitor data, a person's in-the-moment body perception, and scientific knowledge into one continuous conversation. BodyOS helps explore possible lifestyle relationships and turn complicated information into a small action for today.

Four new V2 capabilities

  1. Apple Watch and Yuwell glucose data: with permission, the iPhone HealthKit Bridge reads Apple Watch and Yuwell Anytime 5 Pro data that has reached Apple Health.
  2. Food × glucose × body perception: in a BodyOS DM, a person can discuss what they ate, how glucose changed, and how they felt, then receive a lifestyle explanation and practical next step.
  3. General health interaction in groups: group chat can answer general questions about food, training, sleep, and glucose management, as well as support check-ins and everyday health interaction.
  4. Guidance from three scientific books: the private knowledge base includes 《控糖革命》, 《百岁人生行动手册》, and 《睡眠优化完全指南：科学与实践》 and uses available source material to support answers.

How groups and DMs divide the work

  • Groups are for general knowledge, shared check-ins, and health interaction. A group never reads personal health data, DMs, or private knowledge, and it never exposes raw health values.
  • BodyOS DMs are for the corresponding person's analysis. Only after explicit permission does BodyOS use the minimum necessary data to discuss food, glucose, sleep, training, and body perception.

Data, privacy, and medical boundaries

  • Apple Health and Apple hardware are not prerequisites for FitCrew. Health permission is always optional and revocable.
  • People, devices, and health-category consent bind separately; cross-user ingestion and access are rejected.
  • Raw health fields are encrypted at rest, and a model receives only the aggregates, intent, and knowledge excerpts needed for the answer.
  • BodyOS provides lifestyle guidance, not disease diagnosis, treatment, or medication advice, and it does not replace a clinician.

Verified engineering state

  • Python / policy, Swift Core, and iOS Simulator CI are green.
  • Strict production HTTPS health checks are verified. https://124.156.218.104/healthz currently reports backend version v2.0.0-alpha.1.
  • Controlled invitation, one-time pairing, per-user isolation, consent withdrawal, and the group privacy boundary are in the code baseline.

This verifies builds, policy, isolation, and deployment connectivity—not an individual health outcome.

Not complete

  • External TestFlight distribution is not complete.
  • Full physical-device acceptance for an invited tester is not complete.
  • The real-world 16-day study is not complete, and there is no study conclusion to publish yet.
  • Real health data, identities, device tokens, pairing artifacts, and private book text are not included in the public Release or Git.
Assets 2
Loading