Users express intent in natural language; agents plan and optimize business operations on top of a
deterministic scheduling and workflow engine. The whole system rests on one safety principle —
AI never mutates state directly. Agents propose plans, the policy engine validates and
risk-scores them, and only a deterministic executor is allowed to change anything.
◈ Execution-safety pipeline
The policy engine risk-scores every plan from low to critical, then routes it to autonomous, requires-approval or suggestion-only execution. Nothing reaches the database unvalidated.
◷ Deterministic scheduling engine
10-minute slot granularity, UTC storage with timezone conversion at the presentation layer, and double-booking prevented by pessimistic locking inside PostgreSQL transactions — modelling schedules, breaks, vacations, durations and buffers.
⛓ DAG workflow engine
Idempotent, retryable, fully audited steps with exponential-backoff retry policies and saga-pattern compensation on failure. Every execution history is persisted.
✦ LangGraph agent framework
Scheduling-optimization, cancellation-recovery, conflict-resolution, utilization-optimization and schedule-apply agents — plus a ReAct booking agent operating over a typed tool registry.
⌨ Natural-language command layer
Spans booking, CRM, catalog, payments, inventory, loyalty, marketing and clinical workflows — gated by a four-tier access-control matrix (client / staff / manager / owner) with per-data-category permissions.
▦ 48 domain modules
Bookings, memberships, subscriptions, gift cards, promo codes, retail POS, inventory, commissions, loyalty, referrals, reviews, analytics, billing, compliance, and a clinical suite (LIS, diagnostic codes, test results, questionnaires, intakes).
◱ Multi-surface delivery
A Next.js dashboard plus consumer and provider mobile apps built in React + Vite and packaged for iOS and Android via Capacitor, over an event-driven core with Socket.IO real-time updates.
✓ Engineering rigor
~2,000 test suites across the monorepo. Modular-monolith DDD boundaries designed for later service extraction, deployed on Vercel and Railway with Dockerized PostgreSQL 16 and Redis 7.