A good stepping stone to exploring this space would be a useable complete system in which you layout high level concerns such as architecture, use-cases, and us

A good stepping stone to exploring this space would be a useable complete system in which you layout high level concerns such as architecture, use-cases, and user-interface behaviour using a "system 2" style, and can dive into code just for the details. A separation of which concerns are built using declarative modelling (the "system 2" stuff), infrastructure built using a normal imperative programming language, and the actual business logic when it can't be generated entirely from models being implemented in a functional programming language with a strict subset of the procedural code. And most importantly (and probably the most work) the user interface for this would have to be extremely polished and well-thought-out.