It was just a quick, rather undeveloped idea. Regarding (2), I think categorical database schemas might be an answer. But it still pretty much theoretical. I

It was just a quick, rather undeveloped idea. Regarding (2), I think categorical database schemas might be an answer. But it still pretty much theoretical. I am not really sure about (4). I think it would be a mix of both, although the actual Terraform operations would be treated as primitives. I think (5) doesn't have to be a constraint solver, it might be just a language where you marry the resources (and the way they scale, also described in (4)) with the actual computation, even if it was all explicitly specified. (Constraint solving it is another level.) Basically, (5) describes the final architecture of the system, while (2) specifies what needs to be computed and (4) specifies what resources are available to do any computation.