Stage 2: COMPOUND -- Sequential Synthesis

| Conflict | Resolution | Reasoning | |----------|-----------|-----------| | Who owns visual reactivity? | K11 Unity, locally (Path A/F win over C) | Visual latency budget is ~13ms. Remote control adds 20-40ms round trip. Unacceptable. | | Who owns music intelligence? | MotionMix iOS (Path C wins over A/D) | EchelonBridge + SAN + ParamMapper is 5,000+ lines of battle-tested motion-to-music. No port. | | Who coordinates across mesh? | Multicam server :9404 on Mac1 (Path B insight, simplified) | Already exists, already has director loop + WebSocket hubs + session management. | | Message bus for sensor data? | Direct UDP, no NATS (Path F wins over E) | Real-time sensor data needs <2ms local, not 15ms through a broker. | | Message bus for control plane? | HTTP/WebSocket via multicam server (Path E insight, existing infra) | :9404 already handles /echelon, /bar-fire, /director/ws, /session/*. | | Does Unity publish outward? | Yes: LUMS derived state (Path D insight) | Unity publishes scene state so remote consumers get processed features, not raw data. | | Where does ML inference run? | cloud-vm or Mac5, REST API via Tailscale (Path B) | K11 has no CUDA. One-step diffusion stays remote. | **Data Plane (real-time, UDP, sub-50ms):** All sensor data and derived features flow as UDP datagrams using the LUME wire format family. Publishers bind [ip]. Consumers listen on well-known ports. No middleware. No broker. No acknowledgment. Fire-and-forget with graceful degradation on loss. **Control Plane (coordination, HTTP/WS, 100ms+ tolerance):** Session management, director cuts, echelon state sync, health checks, and configuration flow through the multicam server :9404 HTTP API and WebSocket hubs. Reliable delivery. Request-response for commands. Event streams for state changes. **Domain 1: K11 -- Visual Sovereignty** K11 owns everything between sensor input and HDMI output. It runs the Python publishers, Unity scene, and all visual processing components. It does NOT make music decisions. It does NOT coordinate other machines. It publishes derived visual state (LUMS) for remote consumers. **Domain 2: MotionMix iOS -- Musical Sovereignty** The iPhone owns the motion-to-music pipeline. It consumes LUMM (skeleton) and LUMF (audio environment) from K11 via Tailscale UDP, fuses them with local CoreMotion/Vision data into the 128D canonical vector, runs the SAN pipeline, and drives Strudel.js audio synthesis on Mac5. It does NOT control K11 visuals directly.