Everything Nodes - Modifier Stack - could do as node tree

I originally thought of this while thinking how to attack geometry nodes from a perspective of avoiding large node graphs.

The whole concept is that this is really just 1 big procedure. So, just like in programming, let's break this down into tiny little chunks, as much a possible.

Using Groups is certainly a great way to do that for creating functions (that return values), and using a modififer stack is a good way for procedures (overall steps to build out the thing). But there's kind of another level here, and that is being able to introduce logic into the modifier stack and take different branches.

So, instead of being a stack, I'm suggesting a node graph for the modifier stack, which might find a lot of uses outside of geometry nodes. Perhaps it's in the works already - haven't followed details of Everything Nodes.

I additionally wanted to suggest a "Prior GN Mod Attr" node which would contain a list of all the outputs of the prior modifier in the geometry nodes stack. It serves 2 purposes: 1) clarity - if there's a bunch of GN mods in a stack, you might want to know if the attribute you're accessing was from the prior step, or possibly way back. If it was from the prior step (modifier in the stack), then it will be accessible from this new node. Just helps to see where it's coming from.

And I guess the ability to "save a group to an asset" (new or existing asset - if existing, it just appends the group (function) to the list of functions in that "functions asset". That way you could have libraries of functions to use as assets. A new asset type...

Same overall concept of breaking down into chuncks applies to materials as well, but different over there since there's no modifier stack involved, but certainly could introduce some logic graph at a higher level, with actual material nodes inside those nodes.