DEVELOPER DOCUMENTATION
Persistent memory
Build continuity with profiles, summaries and retrieval.
Persistent memory is the application layer that gives a character continuity across sessions. A stored document collection alone does not provide a complete personal memory system.
Three kinds of context
| Context | Typical purpose |
|---|---|
| Recent conversation | The immediate exchange and unresolved topics |
| Durable user profile | Explicit preferences, names and approved personal context |
| Character knowledge | Background information the character can retrieve |
Keep each source identifiable so the application can update or remove the right information.
Recommended data flow
- Resolve the authenticated user, workspace and character.
- Load recent messages and permitted profile facts.
- Retrieve relevant character knowledge when needed.
- Generate the response with that bounded context.
- Summarize or analyze the completed exchange.
- Save approved updates through the application's memory policy.
Isolation and control
Scope memory by workspace, user and character. A user's private conversation must not become another user's context. Support correction, deletion and retention settings in your product design.
Avoid treating every generated assumption as a verified user fact. Preserve unknown values until the conversation supplies usable information.
Configuration service
We help define profile fields, summary behavior, retrieval rules, storage and lifecycle settings for your deployment. Persistence, access controls and retention are implemented and verified as part of that project scope.
Talk to our team about your architecture, character and launch.
Discuss your integration ↗