Our seed memo to build a change control system and SDK

Hi hn crowd,

founder of opral here. we seem to have stumbled on an easier and better way to build collaborative apps by leveraging "version control as a backend":

- collaboration for file-based software (a real-time layer can be added)

- data ownership for users and companies because file-based (no lock-in)

- open source like pull request collaboration for design, engineering & co

feedback and questions are welcome. directly commenting on the google doc is enabled

i love the idea of bringing "permissionless collaboration" 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/trust?

perhaps the catalyst here is AI. as you write, if you want AI agents to interact with your systems, "you need a controllable and auditable mechanism for observing an agent's changes and accepting or rejecting them."

so if you build with lix, your app is "agent-ready." that's pretty cool.

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