Control attribute rule execution order

[Bud]

From @JohannesLindner : 

If multiple rules trigger on the same table, you have no control over the execution order, which can give unwanted results if a rule depends on a field that is calculated by another rule. 

Lessons Learned — Attribute Rules 

Could attribute rules be enhanced so that we can control the execution order? That would allow us to split huge attribute rules into smaller more manageable rules.

[SSWoodward]

@EstherSmith_Dev 

In regard to:

In database speak, are they similar to "after <event> for each row" trigger? e.g. if we want to check count of child features using FeatureSetByRelationshipName, it will include current feature being added as child feature?

Yes, the rule fires after the triggering event.