Interesting. I like this a lot. All Code implements a process. If the requirements for that process change (due to shifting regulation, for example), the proce

Interesting. I like this a lot. All Code implements a process. If the requirements for that process change (due to shifting regulation, for example), the process is a liability until it adapts to those requirements, at which point it can again become an asset. If a process has no artifacts for implementing it, it can’t be a liability. That’s why we see so many companies offering regulatory compliance as a service, in the healthcare space for example (AHIP, NIPR). Because if every insurer had to write code that integrated with regulation, they would be writing a lot liability. Using a vendor allows them to offset that liability to a third party, whose whole purpose in existence is to maintain a nice liability:asset ratio. Perhaps we’ve found a utility for my theory, in contributing to the build vs buy discussion :)