Almadar
The Physics of Software: Declare your application, compile to production
Welcome to the Almadar programming language documentation. Almadar is a declarative approach to building full-stack applications through state machines, entities, and traits.
Quick Navigation
Getting Started
- Introduction - What is Almadar and why should you use it?
- Install the CLI - Get the Almadar CLI on your system
- Build a Task Manager - Build a task manager in 10 minutes
- Core Concepts: Entities - Entities, traits, and state machines
Language Reference
- Entities - Data structures and persistence
- Traits - Behavior as state machines
- S-Expressions - Guards and effects syntax
- Effects & Standard Library - Server and client effects
- Patterns - UI pattern library
Guides
Technical
- Guards & Business Rules - S-expression conditions on transitions
- Cross-Orbital Events - Emits, listens, and payload contracts
Business
- Why Almadar? - Enterprise use cases and ROI
- Case Studies - Inspection and Trainer case studies
Tutorials
Beginner
- Anatomy of a Complete Orbital - Entity, traits, state machine, and pages
- Build a Task Manager - Full CRUD with lifecycle states
Intermediate
- UI Patterns & render-ui - All pattern types, slots, and action wiring
- Guards & Business Rules - S-expression conditions on transitions
- Cross-Orbital Communication - Emits, listens, and payload contracts
Advanced
- Building a Full Multi-Orbital Application - Three connected orbitals from a real schema
- Generating Schemas with an LLM - Prompting, validation, and fixing common mistakes
Reference
The Almadar Philosophy
The Closed Circuit Pattern
Every user interaction in Almadar follows a guaranteed flow:
Event (User Action)
↓
Guard Evaluation (Permission Check)
↓
State Transition (Behavior Logic)
↓
Effects Execution
↓
Response to UI
This pattern ensures:
- Security by design - Guards enforce permissions at the transition level
- Predictable behavior - State machines can only exist in valid states
- Testability - Every path is enumerable and testable
Three Pillars
- Entities - What your application manages (data)
- Traits - How your application behaves (state machines)
- Pages - Where your application appears (routes)
Why "Almadar"?
Like planets in orbit around a star, application components in Almadar follow predictable, law-governed paths. The laws of physics ensure stability; Almadar's state machines ensure application consistency.
Community
- Discord - Real-time chat and support
- GitHub Discussions - Technical discussions
- LinkedIn - Updates and announcements
Built with passion by Almadar