Back to corpus
architecturetechnical paper candidatescore 34

Echelon Capture Architecture

``` Left iPhone Right iPhone Apple Watch (optional) │ │ │ └─────────── WebSocket: /visualization?device_id=<role> ───────────┐ │ cc-mcs │ WebSocket: /ws/latent │ Perform tab ```

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

1. **Motion capture** - `MotionStreamer` reads CoreMotion at the configured sample rate - `ComprehensiveSensorManager` can add extra sensors when enabled 2. **Streaming** - Sensor frames are encoded with cc-protocol models - `WebSocketService` sends frames to `/visualization?device_id=<role>` 3. **Perform mode** - `LatentStreamService` subscribes to `/ws/latent?device_id=<role>` - `StrudelEngine` generates audio from `strudel-engine.html` 4. **Recording** - `SessionManager` + `StorageService` write JSONL motion and WAV audio - Sessions stored under `Documents/Sessions/<sessionId>/` - **Views**: Perform, Stream, Record, Settings - **Core services**: MotionStreamer, NetworkService, WebSocketService, LatentStreamService - **Local storage**: SessionManager, StorageService, AudioRecorder

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

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.