LMCache - Bryant McGill

# LMCache **Aliases:** LMCache L2; LMCache encryption boundary; LMCache tenant encryption **Entity class:** Memory infrastructure **Integration priority:** P1 **Collections:** [[collections/Consciousness Continuity|Consciousness Continuity]] · [[collections/Neurotech|Neurotech]] · [[collections/Machine Succession|Machine Succession]] **Canonical source article:** [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]] ## Definition **LMCache** — L0/L1/L2 KV hierarchy, tenant-scoped encryption and durable shared context. ## Relationships  This entry is routed through [[collections/Consciousness Continuity|Consciousness Continuity]], [[collections/Neurotech|Neurotech]], and [[collections/Machine Succession|Machine Succession]]. Its source context is developed in [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]] and [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]]. Status-qualified source edges are preserved in the terminal Research Edges section. ### Key Relationships - **LMCache** is associated with KV cache across L0 GPU / L1 host / L2 durable tiers. Explicit hierarchical cache architecture. - **LMCache** is associated with L2 KV cache with AES-GCM. At-rest protection. - **LMCache** is associated with L2 encryption keys by tenant cache_salt. Per-tenant derivation. ### Connections in this corpus - The technical comparison identifies a convergence: **LMCache** is connected in the corpus with [[wiki/Platform Custody|Platform Custody]]. Tenant memory can be encrypted at rest while active runtime remains visible to serving process. - The technical comparison identifies a convergence: **LMCache** is connected in the corpus with [[wiki/Residual Sovereign|Residual Sovereign]]. Shows concrete distinction between durable-state custody and runtime trust. ### Additional Documented Relationships - **LMCache** is connected in the corpus with [[wiki/Neural Data Sovereignty|Neural Data Sovereignty]]. Durable personal context can be encrypted by tenant. although active runtime remains exposed.  ## Related Work in the Corpus  - In [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]], **X. Memory became infrastructure** provides the narrative context for **LMCache**: Underneath, the memory hierarchy has been elaborating for years in ways that map with uncomfortable precision onto what a person would need. - In [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]], **Host-infrastructure crosswalk** provides the narrative context for **LMCache**: The active-state hierarchy is becoming infrastructure in its own right.  ## Research Edges  #### Host–residual infrastructure patch — 2026-09-10 **Resolved aliases:** `LMCache L2`, `LMCache encryption boundary`, `LMCache tenant encryption` **Collections:** [[collections/Consciousness Continuity|Consciousness Continuity]] · [[collections/Neurotech|Neurotech]] · [[collections/Machine Succession|Machine Succession]] **Canonical source article:** [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]] **Related acquisition source:** [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] **Relationship source:** [[research/Mind Uploading and AI Host-Residual Ecosystem Relationship Graph - 2026-09-10|Mind Uploading and AI Host-Residual Ecosystem Relationship Graph — 2026-09-10]] #### Host-infrastructure integration L0/L1/L2 KV hierarchy, tenant-scoped encryption and durable shared context. #### Outgoing typed edges - **HR-0123 — `stores` → `KV cache across L0 GPU / L1 host / L2 durable tiers`** — **VERIFIED EXTERNAL**; evidence `WEB_LMCACHE_ENCRYPT`, `WEB_LMCACHE_L2`. Explicit hierarchical cache architecture. - **HR-0124 — `encrypts` → `L2 KV cache with AES-GCM`** — **VERIFIED EXTERNAL**; evidence `WEB_LMCACHE_ENCRYPT`. At-rest protection. - **HR-0125 — `scopes` → `L2 encryption keys by tenant cache_salt`** — **VERIFIED EXTERNAL**; evidence `WEB_LMCACHE_ENCRYPT`. Per-tenant derivation. - **HR-0126 — `can_use` → `S3`** — **VERIFIED EXTERNAL**; evidence `WEB_LMCACHE_ENCRYPT`. Durable shared backend. - **HR-0127 — `can_use` → `filesystem`** — **VERIFIED EXTERNAL**; evidence `WEB_LMCACHE_ENCRYPT`, `WEB_LMCACHE_L2`. Durable shared backend. - **HR-0128 — `can_use` → `RESP store`** — **VERIFIED EXTERNAL**; evidence `WEB_LMCACHE_ENCRYPT`. Durable shared backend. - **HR-0129 — `does_not_protect` → `plaintext L0 GPU and L1 host memory`** — **VERIFIED EXTERNAL**; evidence `WEB_LMCACHE_ENCRYPT`. Explicit threat-model limit. - **HR-0130 — `cross_threads` → [[wiki/Platform Custody|Platform Custody]]** — **ANALYTIC CONVERGENCE**; evidence `WEB_LMCACHE_ENCRYPT`, `WIKI_ARCHIVE`. Tenant memory can be encrypted at rest while active runtime remains visible to serving process. - **HR-0131 — `cross_threads` → [[wiki/Residual Sovereign|Residual Sovereign]]** — **ANALYTIC CONVERGENCE**; evidence `WEB_LMCACHE_ENCRYPT`, `WIKI_ARCHIVE`. Shows concrete distinction between durable-state custody and runtime trust. - **HR-1405 — `cross_threads` → [[wiki/Neural Data Sovereignty|Neural Data Sovereignty]]** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Durable personal context can be encrypted by tenant, although active runtime remains exposed. - **HR-1406 — `cross_threads` → [[wiki/Platform Custody|Platform Custody]]** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. At-rest encryption narrows but does not eliminate host power because GPU/host plaintext remains.