Our seed memo to build a change control system and SDK

Hi hn crowd,<p>founder of opral here. we seem to have stumbled on an easier and better way to build collaborative apps by leveraging &quot;version control as a backend&quot;:<p>- collaboration for file-based software (a real-time layer can be added)<p>- data ownership for users and companies because file-based (no lock-in)<p>- open source like pull request collaboration for design, engineering &amp; co<p>feedback and questions are welcome. directly commenting on the google doc is enabled

i love the idea of bringing &quot;permissionless collaboration&quot; to standard SaaS apps. but the question i kept on asking myself while reading this was...what will get developers to start building with lix vs. what they know&#x2F;trust?<p>perhaps the catalyst here is AI. as you write, if you want AI agents to interact with your systems, &quot;you need a controllable and auditable mechanism for observing an agent&#x27;s changes and accepting or rejecting them.&quot;<p>so if you build with lix, your app is &quot;agent-ready.&quot; that&#x27;s pretty cool.

hey, felix from the inlang team here — we&#x27;re already building on top of lix with Sherlock (VS Code extension) and I can&#x27;t imagine an easier way to build collaborative apps.