One cited-fact spine runs through every surface. Each does one job, honestly. Together they form a loop where facts become datasets become models that flow down to a diabetic's own box — and PHI never flows back.
The sovereign compute + trust foundation. The rigs we own, the cooks we run, the receipts we mint. OpenDiabetic is where models are crockpot-cooked on hardware we control, funded by recycling compute income back into the people it serves. IN BUILD
→ opendiabetic.com · how cooks run
The home vault + the on-device helper (the bee on your shoulder). A diabetic's records live here, on their own box, and only here. The nudge engine reminds without reading; the edge brain organizes in RAM and persists no PHI. This is where the models flow down to. LIVE
The truth layer: cited, guideline-grounded patient facts (NIDDK / IWGDF-sourced). The rule is absolute — no source, no publish; educate, never diagnose. DiabeticTruth is the spine the datasets and models inherit their verifiability from. LIVE
Open, deeded, crystal-clear datasets donated free to builders. Every set shows its schema, samples, size, and SHA-256 so you can verify it yourself. No PHI — open education + synthetic instruction sets only. This is the corpus layer every cook draws from. LIVE
→ diabeticdatasets.com · how to use them
Show + host. Every model that beats base ships here with its weights, flightsheet, and beat-base receipt together — the visible record of how it was cooked. The plated dishes from the Diabetic Crockpot Cooks menu live here. IN BUILD
→ diabeticmodels.com · the menu & the cook
The verifiable backbone. Every dataset and every cook mints a deed and a hash-chained receipt — tribunal-graded, Merkle-rooted, publicly anchored. DiabeticLedger is where anyone can audit provenance independent of us: what the data is, where it came from, how the model was cooked, and that no PHI ever crossed. Verifiability is the moat. IN BUILD
→ diabeticledger.com · the deeded doctrine
The crystal-clear hardware breakdown of sovereign diabetic compute: the Blackwell GPU cook fleet, the Synology vaults, the Jetson Orin edge brain, and the consumer device swarm (watch, phone, sensors, voice). What runs where, and why — privacy-first by construction. IN BUILD
→ diabeticnode.com · it takes a swarm to run the node
Where the mission closes the loop with the people it serves. Sovereign-compute income is recycled back into diabetics as the human continuum of care — a ride to the doctor, diabetic shoes shipped, the things people actually need — at no charge, no strings. Give people what they need, not what you have. Dignity, not charity. Some of this is LIVE (reminders, organization); the ride network and shoe-shipping are FRAMEWORK — designed, honestly labeled, not yet a live service. → diabeticdonation.com
DiabeticTruth (cited facts)
↓ become
DiabeticDatasets (deeded corpora)
↓ cooked on
DiabeticNode / OpenDiabetic (sovereign compute) → Diabetic Crockpot Cooks (the 5-cap menu)
↓ published at
DiabeticModels (show + host)
↓ flow DOWN to
LocalDiabetic (the diabetic's own box)
↓ compute income funds
DiabeticDonation (rides · shoes · the continuum — no charge, no strings)
every step ──► DiabeticLedger (deeds + hash-chained receipts) ◄── audit it yourself
↑ only receipts flow up — PHI crosses never