LUME Full System Architecture -- K11 as Central Hub

Full HTML reader

Read the full artifact

Extracted abstract or opening context

_Generated 2026-04-27 via Evo3 (4-stage recursive creative evolution)._ _Full evolution output: Desktop/evo-cube-output/lume-full-system-architecture/_ **Two communication planes:** - **Data Plane** (UDP, real-time, <50ms): Sensor data and derived features flow as LUME wire format datagrams. Publishers bind [ip]. Fire-and-forget. No broker. - **Control Plane** (HTTP/WS, 100ms+ tolerance): Session management, director cuts, echelon state. Reliable delivery via multicam-server :9404. **Three sovereignty domains:** - **K11** owns visual rendering (sensors -> Unity -> HDMI) - **MotionMix iOS** owns musical intelligence (128D canonical -> SAN -> Strudel) - **Mac1 multicam-server** owns coordination (director, sessions, beat quantizer) No machine crosses its sovereignty boundary. K11 does not make music decisions. iOS does not control visuals. Mac1 does not process sensor data. - Bar-fire relay path: iOS -> HTTP :9404 -> WS broadcast -> echelon_relay -> LUMH -> Unity - Estimated latency: ~100ms end-to-end - This is adequate for bar-aligned events (bars = 1-4 seconds) - NOT adequate for beat-aligned events (beats = 200-500ms) - Beat-aligned visual hits use LOCAL LUMF transient detection instead (Path B, ~8ms) - Result: bar transitions are server-coordinated, beat hits are locally detected

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.