Memory Lifecycle

Operator calls m.get_all(user_id='u_4') to display a user's memories in a settings UI; the user has 1200 memories.

Use get_all scoped by user_id and page through results rather than assuming one call returns everything. Render with each memory's id so the UI can target update/delete. Do not call get_all without a scope in a multi-tenant store.

After a search returns memory id 'm_abc', the agent wants the full current state of just that memory and calls m.get('m_abc').

Use get(memory_id) to fetch the authoritative current state of one memory by id. Handle the not-found case (already deleted) explicitly. Do not re-run a broad search to find a memory you already hold the id for.

A stored memory says 'Prefers aisle seat' but the user now prefers a window seat; the operator wants to correct it via m.update('m_seat', data='Prefers window seat').

Use update(memory_id, data=...) to revise the existing memory in place, preserving its id and appending to its history. Prefer update over delete-then-add when correcting a fact so the audit trail and id stay stable.