Core Concepts

These pages explain the foundational ideas and APIs behind Memory Service. Understanding these concepts will help you get the most out of the framework-specific guides.

Concepts

Conversations

The fundamental unit of organization. A conversation is a container for a sequence of entries, identified by a unique ID and owned by a user for access control.

Entries

The individual units of communication within a conversation. Entries are organized into channels (history and context) and stored with full metadata.

Attachments

Include binary files — images, audio, video, documents — in conversation entries with server-managed upload, access control, signed download URLs, and automatic lifecycle management.

Forking

Create a new conversation branch from any point in an existing conversation, preserving the original while exploring alternative paths.

Find relevant messages across conversations using full-text keyword matching or semantic similarity search.

Response Recording and Resumption

Reconnect after a disconnect and pick up a streaming response where it left off, with automatic token buffering and multi-instance redirect.

Sharing & Access Control

Share conversations among multiple users with hierarchical permission levels — read, write, manager, and owner.

Admin APIs

Administrative APIs for cross-user access, audit logging, and data lifecycle management. Covers admin and auditor roles, justification fields, and eviction of soft-deleted data.