Formalize static/dynamic behavior order

[hulsed]

Function execution order should differentiate dynamic behaviors (which should run at the end of each time-step according to specified run order) from static behaviors (which can still run/propagate in an un-directed sense)

Ideally this should result in a time-step running as follows:
1.) Run dynamic behaviors in specified order
2.) Run static behaviors (if any) in specified order, and then execute remaining blocks until it converges (current behavior)

Functions should be given helper methods for this which are called at different times. Ideally allows one to use the current behavior() and condfaults() interfaces while making the default dynbehavior() and statbehavior() (or whatever makes sense)