Skip to content

v0.2.0 — WhatsApp Go bridge + Google Health system

Latest

Choose a tag to compare

@jigripokri jigripokri released this 02 Jun 00:23

Two architecture migrations and the docs/briefings around them.

Highlights

WhatsApp: Baileys (TS) → whatsmeow (Go) bridge. Native contact/group-sender name resolution — no more manual phone↔LID juggling. The late-March-2026 LID migration is now historically resolved: dual-JID tracking is retired. Plus new guidance on bridge durability (run it as a startup service so overnight briefings survive a reboot) and a bridge-liveness assertion (don't trust an empty scan — confirm the bridge is connected + has 24h of traffic first).

Health: Fitbit Web API → Google Health API. Reconciled multi-source wearable stream; briefings call the health MCP directly (sync script retired). Substitutable with Whoop / Oura / Apple Health / Garmin.

New health system (docs/health-system.md)

Daily health data is mostly noise — signal lives in deviations. Each metric now surfaces at the cadence it actually matters:

  • Morning chip — conditional & silent by default; fires only on a deviation, always implies an action.
  • Weekly section — always present: ~6 numbers + one pattern + one action.
  • Monthly Health Memo (new, 28th) — ~250-word trajectory read, with a twice-yearly pre-bloodwork prep section.
  • Bloodwork reminder (new) — twice-yearly nudge mapping wearable trends to a doctor ask-list.
  • health.md auto-updated (latest daily / rolling weekly / rolling monthly).

Plus an optional genetic-context layer (store risk priors, never raw reports) and an earned-praise system (scarce, must clear a real bar; all-green months pivot from metrics to purpose).

Notes

No personal data ships — all examples are generic and sanitized; .gitignore still excludes memory/.

Full changelog: https://github.com/jigripokri/POHA/blob/master/CHANGELOG.md · compare v0.1.0...v0.2.0