Back to corpus
research noteexperiment writeup candidatescore 42
Strudel Integration Plan - Option A
```bash cd apps/desktop/cc-echelon/apps/echelon-tauri npm install @strudel.cycles/core @strudel.cycles/webaudio @strudel.cycles/tonal tone ```
Full HTML reader
Read the full artifact
Extracted abstract or opening context
## Overview Wire existing Rust components (Conductor, Rehearsal, LIM-RPS) to Strudel.js for real-time pattern-based music generation.
## Current State - ✅ LIM-RPS latent physics (Python + Rust) - ✅ Computational rehearsal (`cc-brain/rehearsal.rs`) - ✅ Conductor with section state machine (`cc-brain/conductor.rs`) - ✅ Strudel-IR types complete (`cc-protocol/strudel_ir`) - ✅ Audio engine with synths/effects - ✅ Tauri frontend with real-time visualization - ❌ No Strudel runtime executing patterns - ❌ No bridge from Rust PatternEdit → JavaScript execution
- [ ] Run `echelon-tauri` with `--local-mcs` - [ ] Start EchelonCapture iOS app, connect to local backend - [ ] Dance with phone in hand - [ ] Observe latent state updating in Tauri console - [ ] Hear Strudel patterns change based on movement - [ ] Check console for "📨 Received PatternEdit" messages - [ ] Verify section transitions (Intro → Groove → Build)
1. **Add Rehearsal Integration** (Week 2) - Wire `RehearsalEngine` to predict future latent states - Use trajectory shape to pre-schedule edits
2. **Expand Pattern Vocabulary** (Week 3) - More complex Strudel patterns (polyrhythms, euclidean, etc.) - Track-specific transforms (stutter, reverse, degrade) - FX automation (filter sweeps, delay throws)
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.