I honestly can't see the problem with "Serialize", or "RW" or "IO".
Why the OP is choosing "Literate" can only mean one of two things:
1. They have no idea what they are doing and didn't get the joke
2. It just so happens they are serializing the alphabet or dictionary terms. Which is still not a good idea.
In any case, referring back to post #7 (and assuming I understood the requirements):
Are you really, really, really sure you want to do this?ObjectLiterator (for both ObjectWriter and ObjectReader),
LiteratorDispatcher (ReaderDispatcher and WriterDispatcher), Literator (Reader and Writer) and LiteratingMapper (WritingMapper and ReadingMapper) seems just right.
Odds are you will want to eventually break the two actions apart. It will probably become inevitable as soon as you start adding to your serialization framework. Instead of simplifying ahead of time, I suggest you perhaps leave read and write operations separated. 1) Because they are indeed different actions even if they share code, 2) Because almost certainly they will stop sharing code sometime in the near future and 3) because users of your framework expect different calls for different actions.
There's also such a thing as premature simplification. I suggest you do not fall for it.