Skip to content

Persistent Memory Infrastructure

Local layered memory for assistants.

status
local

An assistant that remembers more is not automatically a better assistant. Memory asks what is durable enough to retain, what should never be retained, which source produced it, whether it is still current, and which tool is allowed to retrieve it.

This is private memory infrastructure for those questions. General project and preference context lives in one bounded store. Medical learning lives in a separate store with a more restricted tool surface. The separation is architectural. Tags organize data; they do not isolate it.

Retention is a decision. Secrets, credentials, PHI, patient identifiers, raw records, and unverified guesses do not belong in durable memory. A retrieved memory can route the next investigation. It is not proof. Drift-prone facts have to be re-checked against a current source or live state.

Access is local and private. This page does not publish endpoints, tokens, provider configuration, or operational counts.

What I learned: the most important feature of memory is not recall quality. It is knowing the scope and authority of what was remembered.

Related: How I Build, Claims and boundaries.