Organize memory¶
Memory operations¶
Memory is governed derived knowledge with an explicit lifecycle. Begin with source evidence, admit candidates, validate mutation decisions, and let the host persist accepted changes. Organization and consolidation consume those same revisions.
Use dependency-aware updates as the shared maintenance mechanism for memory, retrieval, and graph projections. Keep raw text reuse separate from revision-bound evidence and access policy. The library supplies decisions and immutable values. Your application supplies models, durable storage, authorization, and execution.
Stage |
Decision |
|---|---|
Admission |
Accept, defer, reject, or quarantine a candidate |
Mutation |
Add, update, delete, or no-op against existing memory |
Organization |
Link notes, rank salience, or produce evidence notes |
Consolidation |
Select bounded offline work by utility and cost |
Scope promotion |
Propose a broader-scope artifact linked to its origin |
Experience |
Turn observed work and expert corrections into evidence-bound knowledge proposals |
Actual memory-retrieval snapshot
LongMemEval case |
Required sessions |
Retrieved within top five |
Recall-all@5 |
|---|---|---|---|
|
1 |
1 |
1.0 |
|
4 |
1 |
0.0 |
Retrieving one useful session is insufficient for a question whose answer spans four sessions.