3 posts tagged with "Architecture"

Orb follows atomic design for behavior, not just UI. Standard behaviors are atoms — small state machines that own their topology. Your application composes them into molecules using uses imports and an override surface. The atom's states and transitions stay constant. You rebind the data, rename the events, and replace the effects.

orb validate does not just check syntax. It walks the state machine graph and proves properties that would normally require dozens of hand-written tests. Closed circuits, emission contracts, binding validity, and pattern prop requirements — all checked before any code is generated.

In Orb, every feature is a state machine. Not a component tree, not a bag of hooks — a state machine with explicit states, guarded transitions, and a closed circuit the compiler enforces before any code is generated.