How sotsf/conjurer works
The system architecture should be represented in multiple layers, focusing on these key components:
Frontend Architecture (Client-Side)
• Pages (/, /viewer, /portal, /playground, /beatMapper)
• Components hierarchy (showing major components like Canvas, Timeline, PatternPlayground)
• State Management (MobX stores: AudioStore, BeatMapStore, ExperienceStore, etc.)
• Rendering pipeline:
• ThreeJS/React Three Fiber integration
• Pattern/Effect shader system
• WebGL rendering flow
Backend Architecture
• API Layer:
• tRPC routers (experience, beatMap, playlist, song, user)
• API endpoints for file uploads
• Database Layer:
• Turso/SQLite (show both production and local configurations)
• Drizzle ORM integration
Real-time Communication
• WebSocket layer showing:
• Connection to Unity bridge
• Voice command handling
• Frame data transmission
Use these visual elements:
• Blue: Frontend components
• Green: Backend services
• Purple: Database
• Orange: WebSocket/real-time features
• Yellow: External services (Unity, LED Canopy)
[Client Browser]
• React Frontend
• Pages Layer
• Component Layer
• State Management (MobX)
• Rendering Pipeline (ThreeJS)
• WebSocket Client
• Frame Data Transmission
[Server]
• Next.js API Routes
• tRPC Routers
• WebSocket Server
• Database Layer (Turso/SQLite)
[External Systems]
• Unity Bridge
• LED Canopy
Important architectural patterns to highlight:
Real-time data flow for LED control
Special considerations:
• Data flow for audio-visual synchronization
• Pattern/effect pipeline
• Demonstrate how parameter variations affect the rendering
• Database schema relationships
• Deployment architecture (Vercel hosting)
Remember to:
Both development and production configurations
This architecture should emphasize the real-time nature of the application and its ability to handle complex audio-visual processing while maintaining performance.