Delete Memory

Define Scope First

Before deletion, identify:

Question	Description
Whose memory	Confirm Project, user, and Session boundary.
What to delete	Message, Facts, Summary, or all content under a Topic.
Why delete	User request, compliance, data error, expiration, or business policy.
Whether to keep audit	Some cases require an audit trail while excluding content from recall.

Recommended Flow

1. Locate related Memory by user, Session, query, or source ID.
2. Find Facts and source Message input supporting the Summary.
3. Move related content to deleted or archived.
4. Update retrieval indexes or filters so Query Memory no longer recalls it.
5. Keep necessary audit records, such as deletion time, actor, and reason.

Management States

State	Use case
active	Current and recallable.
deprioritized	Retained but less likely to be recalled.
archived	Retained for archive, normally not recalled.
deleted	Deleted or soft-deleted, should not be recalled.

Deletion requests should usually move related Summary out of active. If Facts or Message input must remain for audit, they still should not enter ordinary Agent context.

Do Not Delete Only Topic

Topic is a recall entry point, not the fact itself. Deleting only Topic can leave Summary or Facts reachable through another path.

Handle deletion from provenance upward:

Message / Facts -> Summary -> Topic

This covers evidence, long-term memory, and topic relationships together.

Interface Boundary

This public page does not promise a stable DELETE /memory endpoint. Deployments may implement deletion through admin APIs, retention jobs, forget pipelines, or operator tools. Regardless of interface, the product should guarantee:

• The deletion request maps to a clear scope.
• Deleted content no longer enters ordinary recall.
• The operation is auditable.
• Strongly consistent business data is removed or redacted by the business system.

Checkpoint

After deletion or archive, query Memory again. Expected behavior:

• Ordinary Query Memory no longer returns deleted content.
• Audit data, if retained, does not appear in Agent context.
• Topic summaries no longer imply deleted user facts.

Next Step

Read WebHooks to add cleaning, audit, and sync logic during memory processing.