Here’s a diagram from that epic page on scaledagileframework.com:

Not the “<Solution>” and “<something — the ‘how’>” sections where the expected solution is defined specifically.

Also when you look at the examples of epics given on that same page (before they are decomposed) they look like this:

• Multiple user profiles
• Implement new artifact in search results
• Implement single sign-on across all products in the suite
• Internationalize all end-user facing screens
• Implement opt-in functionality
• Implement filtering search results by complex user-defined expression

All of these examples are specific about how they expect the problem to be solved. The details of implementation might be flexible but the nature of the solution itself isn’t left open ended. The team is expected to achieve the value in whatever way is already defined in the epic .