Skip to main content

18 posts tagged with "Architecture"

Deep dives into Almadar's architecture

View All Tags

Learning from Interruptions: How Our AI Remembers Your Preferences (Without Being Creepy)

· 5 min read
Osamah Alghanmi
Co-Founder & Technical Lead

Every time you approve or reject an AI's action, it learns. After 5 approvals, that action happens automatically.

Recent Posts

One Schema, Five Apps: How We Built a Government Tool, an AI Platform, and Two Games with the Same Language

· 15 min read
Almadar Team
The Almadar Team

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.

Recent Posts

S-Expressions: The JSON of Functional Programming (That Actually Makes Sense)

· 4 min read
Osamah Alghanmi
Co-Founder & Technical Lead

S-Expressions, JSON, and the Functional Renaissance

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?

Recent Posts

State Sync Across Browser Tabs: The Hardest Problem We Solved (That You Didn't Know You Needed)

· 5 min read
Osamah Alghanmi
Co-Founder & Technical Lead

State Synchronization Across Browser Tabs: The Orbital Approach

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.

Recent Posts

Three Execution Models, One Truth: How We Solved the 'Write Once, Run Anywhere' Problem

· 6 min read
Osamah Alghanmi
Co-Founder & Technical Lead

Three Execution Models, One Source of Truth

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."

Recent Posts

Why Your Next App Should Be a State Machine

· 4 min read
Osamah Alghanmi
Co-Founder & Technical Lead

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.

Recent Posts