Continuity and memory
Compression is where meaning gets lost, and almost nothing in the stack records that it happened.
1 merged upstream fix · 1 case study · 2 tools · 1 paper · 4 terms
Claim 01
A memory layer that paraphrases what it stored can return something you never wrote, with no signal that it changed.
fidelis is a local-first memory substrate with no model call in its default recall path. What was stored is what comes back. That constraint is the whole design: a store that cannot paraphrase cannot silently rewrite a qualifier, drop a negation, or smooth an exception into a generality.
The trade is explicit. Verbatim recall does not compress, and it does not summarize. It gives up the thing that made summarizing memory attractive in order to remove the failure that made it dangerous.
What this does not show
fidelis installs from tagged source; the PyPI package of the same name is unrelated and is not ours. Independent install-to-recall verification by a third party remains open, so the verbatim guarantee is a property of the design as published, not an externally reproduced result.
Claim 02
A widely used framework silently deleted system prompts during history truncation, and long conversations lost their instructions without logging it.
Semantic Kernel's chat-history truncation reducer dropped the oldest messages once a conversation exceeded its window. The system prompt is the oldest message. Past a certain length, every conversation quietly continued without it.
This is the exact failure mode that memory work exists to prevent, occurring inside the memory machinery itself. The fix is merged upstream.
What this does not show
The merged fix covers the truncation reducer only. The case study states that the sibling summarization reducer carries the same defect; that remains an open follow-up and is not fixed by this merge.
Claim 03
A retained output can change how later steps interpret a task, even after its original wording is gone.
The Generative Horizon paper draws a distinction this path depends on. The generative horizon itself exists within a single generation and does not require persistent memory. Recursive interpretive conditioning is the separate, downstream process in which an output that was retained — as context, memory, policy, evidence, or authorization — changes a later horizon.
For a memory system the consequence is concrete: what you retain does not merely inform the next step, it can alter what the next step treats as already settled. A summary stored as a record becomes, on the next read, a premise.
What this does not show
This is the paper's conceptual account, illustrated with a worked example. It is not a measured rate of occurrence in any deployed memory system, and the paper reports no experiment of its own.
Claim 04
There are several distinct ways stored context goes wrong, and treating them as one problem is why they stay unfixed.
Retrieval mutation is a stored passage coming back altered. Reduction drift is a summary that changes meaning while shortening. Hermeneutic drift is different again: the question stays the same while the referent moves, because the most recently retrieved passage pulls the model's sense of which document is in play to the foreground.
These have different causes and different fixes. A verbatim store addresses the first. Nothing in this catalog currently addresses the third.
What this does not show
These three terms are illustrative-tier entries: they are named from practice, not measured incidence. No tool in the catalog currently addresses reduction drift or hermeneutic drift, and zer0dex is a reference implementation whose benchmark implications are not independently reproduced.
Every artifact on this path
| Artifact | Kind | What it establishes | Status |
|---|---|---|---|
| fidelis | Tool | Zero-LLM recall that returns stored passages verbatim | tagged source only |
| zer0dex | Tool | Human-readable index plus vector retrieval, as reference | source |
| Semantic Kernel PR 13610 | Fix | System-prompt deletion during truncation, fixed upstream | merged |
| When the system prompt vanishes | Case | How the defect was found, proved, and landed | published |
| The Generative Horizon | Paper | Single-generation horizon vs. retained-output recursion | preprint |
| Context integrity | Term | The property a verbatim store is defending | tool-addressed |
If this is the failure you are seeing, tell us the system and the symptom. Book a 30-minute call, or send a note and get a written read instead.