Back to corpus
architecturetechnical paper candidatescore 22

Machine Roles

- Rekordbox foreground/focus handling. - Keyboard/MIDI command dispatch. - Pose Coach camera view. - AirDeck gesture detection. - Recording raw camera, overlay, keyframes, and training JSONL. - Storing `body_motion.sqlite3`. - Running self-play and promotion audits.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

- Rekordbox foreground/focus handling. - Keyboard/MIDI command dispatch. - Pose Coach camera view. - AirDeck gesture detection. - Recording raw camera, overlay, keyframes, and training JSONL. - Storing `body_motion.sqlite3`. - Running self-play and promotion audits. - Unity DYK. - Femto Mega depth/RGB. - Sony mocopi intake when sensors are on. - Local mocopi-to-Unity feed. - Optional MotionMix relay. - Session manifests. - Multi-camera data. - SensorLogger intake. - BodyTruth endpoint. - Dataset organization. - Future sensor fusion. - SensorLogger watch data. - MotionMix iPhone camera/SAN data. - Optional wrist motion and heart-rate alignment. - Additional training perspectives. They should not directly trigger DJ commands until their data is validated through the same promotion gates.

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.