Back to corpus
research noteexperiment writeup candidatescore 30

EchelonCapture: Current State vs. Vision

**EchelonCapture is currently a sensor data streaming & recording app.** **It needs to become the visual performance dashboard for Computational Choreography.**

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**EchelonCapture is currently a sensor data streaming & recording app.** **It needs to become the visual performance dashboard for Computational Choreography.** Based on your performance loop diagram and UI vision documents, EchelonCapture should be **the real-time visual manifestation of the entire CC system** - showing the dancer what the machine sees, what it's generating, and where the performance is going. It should display: 1. **Latent Orb** - Living visualization of LIM-RPS equilibrium (the machine's perception of you) 2. **Phrase Spine** - Current generative phrase as topological object 3. **Generative Horizon** - Predicted future latent states (what's coming) 4. **Phrase Reservoir** - Cloud of upcoming musical possibilities 5. **Embodied Control Band** - Real-time modulation parameters (tension, grounding, etc.) 6. **Somatic Timeline** - Compressed history of latent evolution 7. **Audio Vessel** - Musical form visualization 8. **Ambient Aura** - Global performance state atmosphere ### Current Tabs: 1. **Stream** - Connect to cc-mcs-headless, stream sensor data, view FPS/latency 2. **Record** - Save sensor sessions locally 3. **Sensors** - Configure which sensors are active 4. **Sessions** - Browse saved recordings 5. **Settings** - Backend URL, device role, debug mode ### Current Visualization: - ❌ No latent visualization - ❌ No music/phrase visualization - ❌ No generative prediction display - ✅ Raw sensor debug view (accel, gyro, attitude) - ✅ Motion energy meter (simple) - ✅ Network stats (FPS, latency)

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

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.