```value``` usually references the module that serialized attribute uses, such as YAML or JSON. 

But I think you're right - it feels dirty to serialize an attribute while deserializing, just to be deserialized again upon usage. This was a quick fix that we implemented so that we can continue to use all the cached objects in our system already. I'd love to see someone fixing this on a serialization side in ```record_from_coder``` where it should be properly handled as suggested. 

Rails.cache was handling this issue properly. I wonder if there's an opportunity to just piggy back on Rails.cache write/read?