Idempotence is the property of certain operations in mathematics and computer science whereby they can be applied multiple times without changing the result beyond the initial application. The concept of idempotence arises in a number of places in abstract algebra (in particular, in the theory of projectors and closure operators) and functional programming (in which it is connected to the property of referential transparency).
In this case if given the same input x into MDU -e (https://www.synergex.com/docs/index.htm#xfnl/xfnlChap2Methoddefinitionutility.htm) am I guaranteed to get the same output y? Specifically I am concerned about the order in which the methods are ordered. We are willing to take a performance hit in order to guarantee consistent ordering/idempotence.
It is critical that this property be preserved as this will allow us to implement a Tattler process to observe when code changes affect the SMC. Leveraging modern DevOps procedures we have thrown this process into CI and then attached a Tattler to alert us when a developer messed up. This is heavily reliant on our ability to quickly perform a diff against the committed version.