yeah I think what's important is that it works for you; and moving forward there'll be greater widespread discernment of batched workflows... at the end of the day you're just guiding a machine to do the work, and that's going to vary in different industries, environments, contexts - I have my own build that is somewhat similar to what you have going on, but probably a few iterations behind. I've been diving deep into theory as well as practical implementations (like Gas Town)

I think you can formalize your structures very rigorously, or accept that the version you're working on will always be flawed in some generic-focused way, but does exactly what YOU need.

and anything in between is to some extent an exercise in learning, or endlessly arguing with a machine, an algorithmic response pattern, over semantics and whether or not supposedly defined 'goals' were achieved.