I like this change. I think I'm following it correctly. So TK is managing the mutable context, derefing it before it's passed into the lifecycle functions. Good stuff. So if an app wanted to have some state changed by a lifecycle event, we would have our own stuff and would update it from the lifecycle callback, outside of TK's context, right?