> Most importantly, you need to carefully engineer the learning process, so that you are not simply compiling an ever growing laundry list of assertions and traces, but a rich set of relevant learnings that carry value through time. That is the hard part of memory, and now you own that too!

I am interested in knowing more about how this part works. Most approaches I have seen focus on basic RAG pipelines or some variant of that, which don't seem practical or scalable.

Edit: and also, what about procedural memory instead of just storing facts or instructions?