Cuemark EVI — Dev Wiki
Architecture, decisions, runbooks, and diagrams. Everything a future maintainer needs to understand why the system is the way it is.
📘 Architecture
System overview, module breakdown, data model, security, deployment
📝 ADRs (18)
Architecture Decision Records for every significant choice
🖼 Diagrams (7)
System, sequence, auth flow, data model, deployment
⚙️ Runbook
Deploy, rollback, migrate, secret rotation, incident investigation
📋 Changelog
Sprint-by-sprint release history (Sprints 1–9)
🔒 Security
Threat model, disclosure, secrets inventory
🧭 Platform strategy
iOS audio fix, voice-engine alternatives, scaling tiers
System architecture
Rehearsal session sequence
The end-to-end flow of a single rehearsal from setup through post-session analysis.
Three-layer auth flow
Cuemark uses three independent tokens: a Supabase JWT for API access, a Hume access token for the WebSocket, and an HMAC session token for the CLM hop from Hume to our server.
Data model
Script upload + emotion analysis
AI Director feedback generation
Deployment topology
Built from markdown source in /docs. Last updated 2026-04-15.