Which brings us back to why I’m building this platform and designing it the way I am.

It was originally a traditional policy engine, with an event system, tightly integrated into internal platforms. Very useful! But that only solves the scaling issue with implementation, not with legibility

Automating the rest (legibility, transparency, certification, …), as it turns out, is the overwhelming majority of the pain: proving that you fulfil an obligation, proving you can’t bypass the automation, providing the evidence to auditors, along with measurements and testing plans…, and so on

PAIN

Now, people have tried to solve this before, many times. It’s never really been successful (to my knowledge) because the required building blocks haven’t been in place to make this possible

(Unless you pull an AWS and rewrite everything from the hardware up and vertically integrate it all together)

Solving this in the industry requires several specific and unusual things that all must be computationally verifiable, constructable, and composable

Even worse, they need to be standardised and easily implemented at every layer, all the way down to hardware, all the way up to code on the client
In the last year, all the moving parts seem to have come together just enough to make this a bit less absurd to attempt. But some of the standards are drafts, there are unsolved questions, and how to put it all together remains unknown

Naturally, solving that unknown is exactly what I’m attempting

Imagine: dynamic procedures, processes, and actions that are (by construction) attested, evidenced, transparent, and trustworthy

In other words… Dynamic? No problem. Legible? Absolutely. Reusable? Of course. Regulation got tweaked? Seamless adaptation

I’m idealistic, but I’m also optimistic