Back to corpus
proposalexperiment writeup candidatescore 24
📱 EchelonCapture Restructuring Plan
**Date**: December 21, 2025 **Status**: 🔄 Planning Phase **Context**: Multi-sensor ecosystem with Mocopi + Strudel music generation
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Date**: December 21, 2025 **Status**: 🔄 Planning Phase **Context**: Multi-sensor ecosystem with Mocopi + Strudel music generation
With the addition of Sony Mocopi sensors (6 body-mounted IMUs) and the existing **Strudel music generation engine**, we need to restructure **EchelonCapture** to fit into a coherent multi-sensor, multi-app ecosystem.
### Current Situation - **3 iOS Apps**: EchelonCapture, cc-handguard, TrajectoryOS - **Sensors**: iPhone (2x), Apple Watch, AirPods, **Mocopi (6x new)** - **Music Generation**: Strudel (JavaScript/Web Audio) + optional Neural Audio Server - **Backend**: cc-mcs Cloud Run (Rust) for latent physics + Computational Rehearsal
### Key Question from User > "what's also to be considered from the iOS perspectives how many iPhone applications are to we to be creating as you know we have Strudel and the music generation just wondering if that should be all together"
### Answer **Strudel music generation runs in JavaScript (browser or WKWebView).** We have 3 distinct iOS apps with different purposes:
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.