Remember preferences in a per-customer memory store

Goal

Attach a customer-scoped memory store to sessions so approved preferences persist across visits without mixing tenants.

Steps

1. Create one memory store per customer and attach it to sessions.create(resources=...) with the intended read/write access level. [source17]
2. Use the Memory API to inspect or seed approved preferences under a bounded path such as /mnt/memory/preferences.md. [source17]
3. Test two customer IDs in isolated sessions; verify retrieval is tenant-scoped, edits are auditable, and deletion follows retention policy. [source17]

How to verify

Seed different preferences for two customer IDs and query each session; verify no cross-tenant result, edits are auditable, and deletion removes the selected customer’s memory.

Troubleshooting

If one session returns another customer’s preference, stop writes and check resource IDs and access levels at sessions.create before resuming.