The continuation of #Spritely Golem will be to explain how the paradox of "mutable" content can be done in such an immutable distributed system, allowing updates or even deletes (via switching the content to Tombstone objects).
Here's my reading list, in case you want to follow along:
https://tahoe-lafs.readthedocs.io/en/latest/specifications/mutable.html
https://github.com/tahoe-lafs/tahoe-lafs/compare/master...ccxcz:crdt-dirs-spec
(thanks to friends on #erights on irc.freenode.net for these links)