The crystal-clear breakdown of diabetic compute

Privacy first. Not as a setting — as the foundation. A diabetic node is sovereign compute pointed at one job: helping a diabetic, on hardware we own, with their private health data never leaving their box. Every choice below — the GPUs, the storage, the edge — exists to keep that true. DiabeticNode is the honest, hardware-by-hardware breakdown of what runs where, and why.

🐝 It takes a swarm to run the node. No single device does the job — the hive cooks, the vault holds, the edge runs, the wearables reach you. Six limbs, one node.

Three tiers, one law. LIVE = running & verified · IN BUILD = partly done · FRAMEWORK = designed, not yet a service. No vaporware, no black box.

The one law

Private health data never leaves the box. Models flow down, receipts flow up, PHI crosses never. Every hardware choice below exists to honor that law. → The Firewall

Privacy first — by construction, not by promise

Privacy-first only means something if it's structural. On a diabetic node it's enforced by how the hardware is wired, not by a policy you have to trust:

Guarantee	How the hardware enforces it
Records never leave	PHI lives only on the Synology vault on the home network; the cloud has no path to raw records
Inference stays local	the Jetson Orin edge brain runs the model on-box; queries never round-trip to a cloud
No PHI at rest off-box	the edge brain processes records in RAM only and persists none
Only non-PHI crosses	devices receive generic nudges; the hive receives receipts — never records
Everything is provable	every action mints a hash-chained, non-PHI receipt — auditable without exposing data

The three tiers of a diabetic node

Tier	Hardware	Job	Status
The Hive (cook)	RTX PRO 6000 Blackwell GPU fleet	Slow-cook the diabetic models on owned silicon. Models flow down from here.	IN BUILD
The Vault (store)	Synology NAS boxes	Hold the diabetic's records — the only place PHI lives at rest. Filing cabinet, not a cloud.	LIVE
The Edge (run)	Jetson Orin + consumer devices	Run the model on-box; reach the diabetic via watch, phone, sensors, voice.	LIVE

→ The Fleet breaks down the cook + vault hardware (why Blackwell, why Synology). → The Edge breaks down Jetson Orin and the real-world devices (Apple Watch, iPhone, IoT sensors, Home Advisor, Whisper).

How compute flows — and what never flows

THE HIVE  (Blackwell GPUs, owned)          cooks models  ─┐
                                                          │  models flow DOWN
THE EDGE  (Jetson Orin, on the diabetic's desk)  ◄────────┘
   runs the model on-box · processes records in RAM · persists NO PHI
        │                                   ▲
        │ generic nudges + receipts          │ the diabetic speaks / taps / wears
        ▼                                   │
CONSUMER EDGE  (Apple Watch · iPhone · CGM/IoT · voice)
        │
        ▼
THE VAULT  (Synology NAS) ── PHI lives here, at rest, and ONLY here
        ▲
        └─ receipts flow UP to the hive (non-PHI) · PHI crosses NEVER

Why sovereign — why we own the silicon

Why we own it: a diabetic's health data is the most personal data there is. You cannot rent that trust from a cloud. We own the GPUs, the storage, and the edge boxes — so PHI has no reason to ever leave, our marginal cost is just kilowatt-hours, and every claim is verifiable on hardware we control. Sovereign isn't a buzzword here; it's the only way the one law can be true.