Just one question, the tracker depends on the max history parameter of the training policies right? maybe it should be possible to do hot/cold switch to reduce the footprint. two KV stores perhaps with the hot store emitting x events which depends on the max history size. I would hate to lose the conversations in the tracker store if deleted after a user session without proper archiving as such. I am assuming most folks are using RDMS to store the tracker and later use it for analytics.a