90% there with this. It _actually_ works, just needs a bit of tightening up. But... it works! It's good.
  * Change "self" in id, and write two layers: one for store changes in general, and another one which piggy backs and provides
    real-time configuration changes.
  * Add app-wide tabId, workspaceId, userId as they are just so often used. Maybe, I say maybe, make a namespace
  * Add an aspect to the store's put method to add tabId, and then take it out just before writing, so that the server always knows
    who to notify for config changes