Never lose the reason today is not yesterday.
When a detail changes, MemState records a new version instead of erasing the old one. The agent always sees the current answer first, but you can still trace how you got there — critical for trust, debugging, and regulated workflows.
Why history beats overwrite
Overwrites make databases look neat but hide mistakes. History keeps accountability: every value carries when it became true and where it came from, so the agent can explain its conclusions.
How you work with fields
- Model each stable attribute as a named field on the topic.
- When something changes, send an update for that field only; MemState appends a revision.
- When you need the narrative, ask for temporal context so older values return alongside the current one.