Learning from Interruptions: How Our AI Remembers Your Preferences (Without Being Creepy)
Every time you approve or reject an AI's action, it learns. After 5 approvals, that action happens automatically.
Deep dives into Almadar's architecture
View All TagsEvery time you approve or reject an AI's action, it learns. After 5 approvals, that action happens automatically.
A government inspection system. An AI learning platform. A personal fitness tracker. A tactical strategy game. A 3D dungeon crawler.
Five applications. Five completely different domains. One language.
Here's how — and why it matters.

Why we chose Lisp-style S-expressions over JSON for logic definition, and why you might too.
Everyone loves JSON, but when you need logic, you end up with string templates or JavaScript. What if your data format was your logic format?

What if you defined your entire application in a single JSON file before writing any component code?

How we keep state perfectly synchronized across multiple tabs without WebSockets or complex backend logic.
Ever had two tabs of the same app open and they got out of sync? We fixed that at the framework level.

The same .orb file runs in the browser, on the server, and compiles to native code. Here's how.
Java promised "write once, run anywhere." We deliver "write once, run everywhere appropriately."
Your development team ships features fast. But bugs keep coming back. Deployments break on Fridays. The codebase grows, and so does the fear of touching it.
The problem isn't your team. It's the architecture.
State machines are at the heart of Almadar. In this post, we explore why we chose state machines as the foundation for application behavior.