The private-language problem · what the door opens

What a readable
export unlocks.

Your wearable already collects the data. The only thing standing between you and any of the projects below is a schema you can actually read. None of this is an Oriya feature — it's what people build, and want to build, once the numbers come out of the walled garden.

Provenance: the "seen in the wild" cards are recurring project genres from the builder community — r/QuantifiedSelf, Hacker News, the Home Assistant forums, GitHub. The "build idea" cards are our own wishlist. No affiliation, no endorsement, no made-up numbers.

Pick what gets built first

Tap ▲ on what you'd actually use — as many times as you mean it. Counts are your votes on this device, nothing crowd-faked; the list re-ranks live and your order rides into the build queue.

The door we're building

Every project above dies at the same wall: the data comes out — when it comes out at all — in a device-specific schema only the vendor can read. The fix is one consented, versioned, normalized export: your scores on the Oriya Index, your baseline, your raw signals where the device allows it. Your data in a language you can read — no device to protect, no proprietary score to defend.

GET /v1/me/export → one schema, every device { "date": "2026-07-07", "oriya_index": 75, "par": 71, "source": "whoop", "native": { "recovery": 83 }, "signals": { "hrv_ms": 62, "rhr": 51, "sleep_stages": … } }

Roadmap-honest: this endpoint is not shipped. It's what the vote above is for — the list gets built in your order, and voters get the door first.