Memory lifecycle operations work at project, end-user scope, topic, and raw-record levels. Choose the smallest destructive boundary that matches the user request.
#Data hierarchy
| Level | Contains | Typical operation |
|---|---|---|
| Project | All Memory for one product/environment | Environment teardown |
| Scope | One end user's summary, topics, and raw records | User erasure |
| Topic | A semantic summary and its linked records | Forget one subject |
| Raw record | One captured user/assistant exchange | Remove one source |
#Disable retrieval
A topic may remain stored but be marked retrieval-disabled. Normal retrieval excludes it unless the administrative caller explicitly asks for disabled topics.
#Deletion operations
DELETE
/api/v1/memory/projects/:projectKey/scopes/:scopeIdDelete one end-user Memory scope.
DELETE
/api/v1/memory/projects/:projectKey/topics/:topicIdDelete one topic and apply the requested raw-data policy.
DELETE
/api/v1/memory/projects/:projectKey/raw/:rawEntryIdDelete one captured raw exchange.
DELETE
/api/v1/memory/projects/:projectKeyDelete the complete Memory project boundary.
#Stable identity
Reuse a stable application user identifier asendUserKey. Do not use a transient device token or browser session ID, or the same person will fragment into multiple Memory scopes.