[xqli]

That matches our experience pretty closely. A lot of “memory” issues we saw weren’t about storage capacity, but about what kind of information is allowed to persist and how it’s structured. Once everything is flattened into one blob, retrieval strategy becomes the only lever left — which is where vectors often get overused.

In Mneme, updates are intentionally asymmetric: – Facts are append-only and explicitly curated (they’re meant to be boring and stable). – Task state is rewritten as work progresses. – Context is disposable and aggressively compacted or dropped.

The idea is that only a small subset of information deserves long-term durability; everything else should be easy to overwrite or forget.

This reduces the need for heavy retrieval logic in the first place, since the model is usually operating over a much smaller, more explicit working set.