Outborn Agent Platform · Manual
Memory
Separate short-lived conversation context from durable memory, company knowledge, and connected data.
Applied guidance
Best practices for memory
Recommended
- Keep short conversation context, durable memory, knowledge, and live source data distinct.
- Review what durable information is retained and how it can be corrected or removed.
Avoid
- Do not store protected source content in memory by default.
How it fits together
01
Conversation context
The immediate conversation provides short-term context for the current interaction.
02
Durable agent or user memory
Durable memory stores selected context for reuse beyond one conversation according to product controls and permissions.
03
Company knowledge
Knowledge Bases are governed organization content. They should not be treated as personal memory.
04
Connected data
Connected applications and Data Collections remain external or governed sources queried when needed, not copied into memory by default.
05
Controls
Memory behavior should be visible, permission-aware, and separable from source access.
06
Privacy
Do not place sensitive material into durable memory unless the product and organization policy allow it.
07
Lifecycle
Memory should have a clear creation, update, retention, and removal lifecycle distinct from source-system retention.
Related documentation