A user deletes a conversation, but a durable preference distilled from it still appears in future sessions. What architectural fact explains this behavior?

1. Session state and retained long-term memory are separate stores with separate lifecycles.
2. A session identifier itself contains every preference as encrypted text.
3. All user preferences are permanently encoded in HTTP status codes.
4. Deleting a conversation automatically retrains the foundation model.