Memory & context
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
Memory & context
Section titled “Memory & context”LM Nexus treats what is remembered and what a model sees right now as two different decisions.
That distinction matters. Something can be worth storing without being useful—or safe—to send with every request.
Memory
Section titled “Memory”Memory stores useful information that should survive beyond one chat turn.
A memory record keeps metadata such as its scope, where it came from, its state, and whether it is still active, so LM Nexus can decide when it remains relevant.
Memory is not meant to be a dump of every chat token, log line, or runtime metric.
Context Builder
Section titled “Context Builder”Context Builder assembles the limited set of context that is actually sent to a provider.
Depending on the task, that can include:
- user or project context;
- durable work state;
- selected files or Knowledge;
- memory;
- Agent/profile instructions;
- other explicitly registered context sources.
The important point is that stored somewhere does not automatically mean sent to the model.
Scope and privacy
Section titled “Scope and privacy”Context building must respect where information is allowed to go.
A source marked local-only or private should not silently become eligible for a provider path that is incompatible with that restriction.
Memory Reconciliation / Dreaming
Section titled “Memory Reconciliation / Dreaming”Memory Reconciliation / Dreaming is planned as a future Memory-owned maintenance layer.
The accepted direction is:
- propose changes before applying them;
- start with small, deterministic reconciliation passes;
- stay within the same scope by default;
- protect pinned or user-edited memories;
- do not automatically Forget;
- add optional semantic proposals later;
- fail closed when semantic, locality, or privacy rules are unclear.
Dreaming source implementation has not started. It should not be presented as a Current or Preview implementation yet.
Why not one giant memory store
Section titled “Why not one giant memory store”Durable Work, Memory, Experience, Temporal State, Notes, Knowledge, and Context Builder have different jobs and different rules for how their data is kept and updated.
LM Nexus keeps them separate and composes the relevant pieces when needed instead of hiding everything behind one universal “brain” database.