Back to corpus
proposalexperiment writeup candidatescore 34
cc protocol
At the bottom: your body and the sensors. In the middle: LIM-RPS + latent field + a controller model. At the top: Strudel as the musical engine, plus (optionally) a neural texture engine.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
Let’s zoom out and treat this like we’re reviewing the design doc for “Echelon-as-an-instrument,” not just a toy.
You basically have a **four-layer architecture**, with a possible fifth “neural icing” layer.
At the bottom: your body and the sensors. In the middle: LIM-RPS + latent field + a controller model. At the top: Strudel as the musical engine, plus (optionally) a neural texture engine.
Phones, watch, AirPods, heart rate. They pump out accelerometer, gyro, gravity, orientation, HR, audio. That’s raw reality.
All those raw signals go into LIM-RPS. It does not output “gesture labels”; it solves for a fixed point in a latent space: a vector that encodes “what your whole embodied system is doing right now.”
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.