Capitalize on complexity

One of the, maybe main, problems with understanding complexity is that we, for historic reasons, have been entirely focused on fighting it rather than utilizing it. Our way of looking at complexity is focused on evading the consequences it has on our way of thinking on our route of rational on our ability of deterministic deconstruction - With other words we have been focused on sharpening our prime weapon - Abstraction. Safety related systems are focused on giving an acceptable risk of failure and the prime means has been “maximize determinism” - functional, procedural, temporal, organizational. With the ever increasing levels of abstractions being piled on top of each other, KISS (Keep it simple, stupid) is starting to be more wishful thinking than an implemented reality. The prime thesis of this paper is that if one changes the perspective and looks at complexity as a resource then it well may be feasible to find technologies that can enhance safety through utilizing complexity. This seemingly paradox approach is motivated by starting at the root cause of faults in digital systems, then looking at classical mitigation and extending this classical mitigation to profit from system complexity through loose coupling. Finally we generalize this approach and use it to describe a (maybe) novel concepts we call dynamic data types which shows that one can protect against faults effectively by capitalizing on complexity. In this paper we introduce an implementation of the principle of ”capitalize on complexity” and outline some practical example ”proof-of-concept” level implementation rather than trying to continue the long lost battle against complexity.