You don't need an AI. A client for automated interaction will hard-code assumptions about content rather than URIs. If the client cannot find a link inside a do

You don't need an AI. A client for automated interaction will hard-code assumptions about content rather than URIs. If the client cannot find a link inside a document, it should just throw an error. A good service would keep links as long as possible, even when deprecated or provide redirects to new resources. A client for human interaction though (like a native application or a SPA), can just implement the visitor pattern to display the UI. Instead of moaning about the architecture principles, we must implement solutions / examples of how to write good clients against REST-based services!