Originally, it had to do with board games and running them in a web/cloud environment. Using websockets made building the game easier, but now there is excepti

Originally, it had to do with board games and running them in a web/cloud environment. Using websockets made building the game easier, but now there is exceptionally complex state within the process (await/async). Generally speaking, the cloud is unforgiving place to hold state within a process. I can speak deeply about streams at scale ( https://dl.acm.org/doi/10.1145/3477132.3483572 https://dl.acm.org/doi/10.1145/3477132.3483572 ). Adama emerged as a tool to help define a "transactional document schema" which I could use to emit deltas to a logger (like Kafka), and once I added a notion of "privacy polices with code"... the potential exploded. I believe I'm onto something with this platform, so I've decided to start hiring to build digital products that fit the thesis. I would say I'm over-engineering in that I'm making the service available to others rather than leveraging in a portfolio of products, but I'd rather keep it open rather than have secrets. (It's a good thing I'm retired because this is a large endeavor)