Comment by btown

The problem, of course, is the moment you have some aspect of the model not representable by the basic primitives - do you make it impossible to switch back to the beginner interface?

I'm reminded of the concept of "ejecting" from e.g. Create React App a few years back - the idea was that if your beginner-friendly interface is actually built on the same underlying engine (in this case bundler and deployment assumptions) you can have full fidelity when you need customization, albeit with a one-way transition.

In the JS world things moved more towards build systems where beginner-friendly-DX and full-configurability could coexist. I'm not sure that CAD has the same dynamic.

Perhaps something like nested layers could work: you can use a complex model as a layer, but only opaquely, and build things around it with solids-and-holes; you can then lift that to itself a complex model, do things with professional CAD, and then treat the result itself as an opaque complex model if you switch back? That gets complicated fast.