Motion Control Studio — Architecture Aligned to Computational Choreography & Echelon

# Motion Control Studio — Architecture Aligned to Computational Choreography & Echelon ## What This Is (and Isn’t) - **Instrument-grade control surface** that routes embodied input (phone/watch/IMU) into a real-time action layer with <10 ms reflex latency. - **Computational choreography-native**: built around `cc-core` (LIM‑RPS/DELL) equilibria, not hardcoded gesture thresholds. - **Plugin‑first & offline‑first**: everything runs locally; cloud sync is optional and never required for performance. - **Echelon optional (future)**: today it can run standalone with the action adapters; when Echelon lands, we swap the execution sink without redesigning the control plane. ## The Missing Layer We Add Now Introduce an explicit **Embodied Latent & Choreography Engine** between fusion and gestures. This is cc-core (LIM‑RPS/DELL) producing a shared latent “moment” that all consumers read, so we do not rebuild Echelon at lower power or bypass computational choreography. Supporting packages: - `cc-core/` — JAX/Flax equilibria (LIM‑RPS + DELL, learned geometry, implicit diff). Export models to ONNX/StableHLO for Rust inference. - `cc-studio/` — existing Python runtime utilities (logging, DJ agent glue); keep as sidecars until everything is ported. - `configs/` — gesture/mapping/profile TOML/JSON; keep user profiles here so Studio + Echelon share the same contract. ## Computational Choreography Contract (what the runtime must honor) - **Two time scales**: - Fast loop (frame rate 100–200 Hz): LIM‑RPS/DELL fast `x*` for reflex control; target <4 iterations, <5 ms end-to-end including IPC. - Slow loop (beat rate 2–4 Hz): DELL slow `y*` for phrase/scene control; scheduled on beat using Link clock; keep coupling energy φ stable. - **Phase-aware control**: expose ψ from the phase head; UI shows ψ vs θ (beat phase) and re-lock time after dropouts. - **Contractive operators**: retain cc-core spectral-norm constraints and step fields; log contraction ratio/headroom in telemetry. - **Fallbacks**: if DELL stalls, hold last `x*`/`y*`, keep template matcher alive, and keep scheduler safe (never block audio).