Back to corpus
technical notebacklog referencescore 22

LUME Rehearsal Bundle Hub Implementation

```text C:\lume\dance-sessions\_incoming C:\lume\dance-sessions\_manifests C:\lume\recordings\pose-coach\sessions C:\lume\data\bodytruth_motionmix_mocopi_k11.jsonl C:\lume\data\bodytruth_k11.jsonl C:\lume\data\sensorlogger_k11.jsonl ```

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

The hub is storage/indexing only. It does not send Rekordbox keys, does not send MIDI, does not restart the AirDeck bridge, and does not modify MotionMix live services. Archives are extracted from `_incoming` into `_processed/<bundle_id>` only after SHA-256 verification against the transport manifest. NKo here means motion-language semantics first. Actual NKo-script inscriptions can be added after labels and meanings stabilize. The request points Mac5 to the Mac4 session root, video, and labels. Recommended worker command: DEMON is treated as a future audio-generation output lane, not a body tracker and not a Rekordbox controller. The request maps reviewed motion labels such as `wave_color`, `burst_high_energy`, `weighted_slow_power_hold`, and `airdeck_platter_spin` into candidate time-varying audio-generation controls.

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

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.