From first write to steady-state operation.
This page is the narrative glue: how an observation becomes durable memory, how later questions pull relevant context, and how MemState performs hygiene and fading without the agent orchestrating revise or forget. Share it with program managers who need the arc without the code.
The story in five beats
- An agent turn emits an observation; MemState ingests it under policy.
- Later turns ask for relevant context with natural language.
- Salience updates keep active threads near the top.
- Background revision collapses obvious duplicates.
- Background forget soft-archives quiet topics out of default retrieval.