The Fleet — where the models get cooked

The hive is the cook tier: owned GPUs that slow-cook the diabetic models, and owned storage that holds the data they're cooked from — and the records they'll never touch. Here's the hardware, and why each piece.

The GPUs — RTX PRO 6000 Blackwell

The cook fleet runs on NVIDIA RTX PRO 6000 Blackwell cards (sm_120, CUDA 13). Each card carries 97 GB of VRAM; a two-card rig gives 194 GB.

Why Blackwell: a clinician-grade 27B anchor model fits and cooks on a single 97 GB card with room for full-context training — no model-parallel gymnastics, no spilling to CPU. 194 GB on one rig means we cook the flagship in one place, deterministically, and keep the smaller edge models trivial. More headroom = bigger, more honest cooks. It's the most VRAM-per-box we can own.
SpecValueWhy it matters for diabetic cooks
VRAM / card97 GB27B anchor + activations fit on one card
VRAM / rig (2×)194 GBflagship cooks in one place, no sharding
Computesm_120, CUDA 13modern attention via SDPA; Triton JITs for the arch
Ownershipoursmarginal cost ≈ kWh, not cloud markup

Honest note: Blackwell is new silicon. Prebuilt flash_attn/xformers kernels don't ship sm_120 yet, so we cook with torch-native SDPA attention. We caught that at canary, not mid-burn — and wrote it down. → Crockpot Cook

Why sovereign GPUs — not the cloud

Why owned: we own the silicon and the electrons. A cook is judged on one axis — is it best-in-class? — never on the meter. We don't trim a 24-hour cook to save rental dollars because there are no rental dollars; the marginal cost is power at a sovereign basis. That's what lets the diabetic models be cooked slow and right. Energy is a receipt, never a constraint.

The storage — Synology NAS vaults

Records live on Synology NAS boxes — the diabetic's own vault, on their own network.

Why Synology: the vault is the whole point of the firewall. A NAS in the home is a filing cabinet, not a covered-entity cloud — PHI sits at rest, encrypted, on hardware the diabetic controls, and the network is structured so raw records have no path off the box. Reliable, owned, local, and git-trackable so every change is logged. The cloud only ever receives non-PHI receipts and models.
RoleWhat lives thereWhat never leaves
Home vaultrecords, meds, labs, foot-care logs, appointments (15-folder structure)all raw PHI
Cook stagingopen/deeded corpora, model weights, receipts(no PHI ever staged for cooks)
Receipts ledgerhash-chained, non-PHI proofs of every action—

How the fleet connects to the edge

The hive cooks a model, proves it beats base, and the model flows down to the edge brain on the diabetic's desk. Receipts flow back up; PHI never does. That hand-off is the whole architecture. → The Edge