Momentum gets teeth, and your wearables come home

Momentum — tasks and goals — went from a flat to-do list to something with actual structure this week: a detailed task view with due dates, notes, priority, checklists, and people. That last one matters more than it sounds. A task like "follow up with Sarah about the lease" is not really about a checkbox, it's about a person, and Momentum can now match that person against Kin — the module tracking who matters — or just hold a name as plain text if they're not in there yet. Tasks stop being abstract strings and start being connected to the rest of what Neeos already knows.

Getting the wearables out of my own account

The bigger unlock this week is less visible: per-user WHOOP OAuth, including webhook routing, and per-user Oura OAuth right behind it. Up to now, health data sync had effectively been wired against my own accounts during development — fine for one person building the thing, useless for anyone else who'd ever want to use it. Now anyone can link their own WHOOP or their own Oura ring, and the webhook routing makes sure their data actually lands against their account and nobody else's.

Alongside that: a real sleep-source priority order — ring first, then Apple Watch, then iPhone or any other third-party source. Multiple devices reporting sleep at once used to mean picking one arbitrarily or averaging them into something meaningless. Now there's an explicit hierarchy, and Soma always knows which number to trust when more than one shows up for the same night.

Why this is the actual unlock

Individually these read like small integration tasks. Together they're the first proof that Neeos can be more than a single-user project — that the account model, the OAuth flow, and the data-priority rules all hold up once there's more than one person's devices talking to the backend at once. That's a prerequisite for the private beta, not a nice-to-have.