System Architecture
The 4-Layer Institutional
Control Plane
Orquestra isolates UI from logic, logic from state, and state from persistence. This strict topology guarantees determinism and safe AI blueprint compilation.
Client Layer (Surface)
The public-facing components, generated UIs, and Next.js applications that end-users interact with. Completely decoupled from underlying workflows.
Landing Pages
Student Portals
Admin Forms
Mobile Apps
Application Layer (Control Plane)
The deterministic rule engine. Parses incoming events, triggers workflow transitions, and validates state changes against schemas.
Workflow Engine
Schema Validator
FEML Middleware
AI Compiler
Service Layer (Event Backbone)
Handles side-effects, third-party integrations, and streaming. Every state transition emits a structured domain event here.
Redis Streams
WebSockets
Notification Hooks
RBAC Guard
Data Layer (Persistence)
Immutable storage of events, workflows, and current entity states. Strictly segregated by tenant ID.
PostgreSQL
Event Store
Redis Cache
S3 (Blueprints)