tiny

tiny is the app

How the ring becomes part of tiny.technology: gateway, worker, agent — and which piece lives where.

• tiny users — what your ring does on your account
• 2 min read
• 280 words

In 10 seconds

The ring cannot speak HTTP, so a gateway you already own (the tiny phone app, or ring-cli bridge) holds the BLE link and posts to the health platform on your account; your agent reads it and reaches back through a command queue. LoraFit's cloud is replaced end to end; the ring keeps no identity beyond its MAC.

flowchart LR
  R((ring)) -- BLE 56FF --> G
  subgraph G[gateway]
    direction TB
    P[tiny iOS / Android<br/>RingGateway]
    M[ring-cli bridge<br/>Mac · Pi]
  end
  G -- "/api/health/ingest<br/>/api/health/media" --> W[tiny worker<br/>health · media · inbox · ring_commands]
  W -- health_summary · health_query · ring_command --> A[agent]
  W --> UI[/health page · iOS · Android · chat cards/]
  A -- "find · measure_hr · memo_pull" --> W -- claim / result --> G

piece	where	what it does
Phone gateway	tiny iOS (OTA 106) RingGateway.swift · Android fleet/RingGateway.kt	finds SR…/JY-… rings, handshakes, streams HR, pulls history and memos, claims agent commands. The default for a ring you wear → Phone gateway
Mac / Pi bridge	this repo, ring-cli bridge	the same contract from a desk machine — the reference → Bridge
Health platform	tiny worker /api/health/*, D1 + R2	devices, samples, day summaries, media, rules, the /health page → Health platform
Voice memos	/api/health/media → inbox ring_memo	file → transcript at ingest → one agent turn, answer pushed → Voice memos
Agent tools	health_*, ring_command	reads your vitals; reaches the ring through a queue the gateway claims → Agent tools
Fleet endpoint	health-endpoint.ts	"Silver ring" / "Black ring" appear as devices; use_device invoke works → Ring as endpoint
Takeover matrix	takeover.md	every LoraFit feature vs tiny, with status and proof

Identity

field	value
gateway → worker	the gateway's fleet device token (~/.tiny/device.json; Keychain / encrypted prefs on a phone), never a session cookie; revocable from Devices
ring → account	one health device row hd_… per MAC with a label you choose — the agent says "silver ring", never the MAC
ring itself	no identity beyond the MAC, no secret at all; two rings on one phone keep separate rows, summaries and memos