KAEL Memory

KAEL supports recent conversation history and persistent keyed memory. They are separate systems with different behavior.

Conversation history

History stores ordered user and assistant messages associated with a session. Signed-in histories can be associated with a Passport subject. Anonymous histories depend on the session identifier supplied by the client.

Public history operations include:

• Save a conversation.
• List available sessions.
• Load a session.
• Delete a signed-in user’s session.

The streaming runtime also keeps a bounded recent context window rather than sending unlimited prior history to the model.

Persistent memory

Memory stores key/value facts associated with either:

• A signed-in Passport subject.
• A visitor or session identifier when no Passport identity is available.

Public memory operations include:

• List memory.
• Save or replace a key.
• Delete one key.
• Clear the current identity or session scope.

Identity precedence

When a signed-in Passport subject is available, it becomes the primary memory scope. Otherwise KAEL uses the visitor or session identifier supplied by the client.

Do not reuse one anonymous session identifier across unrelated users.

What belongs in memory

Appropriate examples:

• Preferred name.
• Communication preference.
• Active project context.
• A user-approved long-running goal.

Do not intentionally store:

• Passwords or authentication codes.
• API keys, tenant keys, operator tokens, or cookies.
• Payment details.
• Government identity documents.
• Private information about another person without a legitimate purpose.

User controls

Clients should expose:

• A visible indication when persistent memory is active.
• A list of stored keys.
• Delete controls.
• A clear-all action.
• An explanation of whether the user is signed in or using visitor-scoped memory.

API

See KAEL API for request contracts and KAEL Safety for privacy and authorization requirements.