You might also want to check out how #IPFS is trying to solve a similar issue of providing a static address for dynamic content in a decentralized way.
As I recall, a major solution is called IPNS.
In short, IPFS is decentralized, and all content in IPFS is immutable and addressed using a hash. But how do you update to a new hash when there's a new version of content, without doing it in a centralized way?
They're using DNS, controlled by the user, to provide the pointer to the latest version, similar to what you describe here.