Design reviews are on-topic provided there is working code to review.
Take this other question, for example. It's a completely valid CR question because the design is an actual hard-implementation (I use hard pejoratively). There's clear source code that indicates just exactly what the intention was, and the design is completely fleshed out. This means we can go through the code and get an exact feel for how the asker intended the system to work. And this is very good for our community. Several of us learned about a design pattern known as ECS (Entity-Component-System) from an answer (accepted and highest upvoted at the time of this writing) on that question.
The problem with the question in question (https://codereview.stackexchange.com/q/117311/507) is that there is no actual source to review. One of the very first statements in the help/on-topic page:
If you are looking for feedback on a specific working piece of code from your project in the following areas
- Best practices and design pattern usage
The problem is that this question doesn't meet the first requirement (working piece of code).
Should the question be able to be rephrased into a working bit of code, then yes, we can review the code and the design. We cannot do a design review without code to match. If that is what the OP is looking for, then perhaps they should head over to Programmers and read the help/on-topic there. That site is very useful for the higher-level abstraction issues. The, "all I have right now is this thought process, how close am I?" questions.
If all the OP wants is an actual review of the high-level abstraction or design (with or without code), then this is not the place for it, unfortunately.
Disclaimer: the recommendation to Programmers is assuming that the question is reworded to fit within their guidelines. As SimonForsberg said, in it's current form:
It appears that this question would be too broad for Programmers.SE
See: Design review for a compiler question