Back to corpus
architecturetechnical paper candidatescore 56

Motion Training Data Pipeline Protocol

> **Version**: 1.0 > **Status**: DRAFT > **Scope**: End-to-end data architecture for motion capture, processing, and training

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> **Version**: 1.0 > **Status**: DRAFT > **Scope**: End-to-end data architecture for motion capture, processing, and training This document defines the complete data pipeline from sensor capture to ML training corpus. The system is designed as an **infinite training grind** - a perpetual motion data collection environment that: 1. Captures motion from multiple sensor sources 2. Synchronizes with audio/phrase playback 3. Processes and normalizes data in real-time 4. Stores for immediate and future training 5. Supports upstream (generation) and downstream (analysis) tasks | Source | Data Type | Frequency | Landmarks | Priority | |--------|-----------|-----------|-----------|----------| | **MediaPipe (Webcam)** | Holistic pose | 30 fps | 33 pose + 21×2 hands + 468 face | Primary | | **Mocopi** | Full body IMU | 50 fps | 27 bones (Sony BVH) | Primary | | **Dual Phones** | Accelerometer + Gyro | 100 Hz | 2 devices (hands) | Secondary | | **Apple Watch** | Motion + Heart Rate | 50 Hz | Wrist orientation + HR | Secondary | | **Headphone Sensors** | Head orientation | 100 Hz | 3-axis rotation | Tertiary | | **LIDAR/Depth** | Point cloud | 30 fps | Sparse body points | Experimental | | Body Region | Primary | Fallback 1 | Fallback 2 | |-------------|---------|------------|------------| | Head | Headphones | MediaPipe | Mocopi | | Torso | Mocopi | MediaPipe | - | | Arms | Mocopi | MediaPipe | Phones | | Hands | MediaPipe | Phones | Mocopi | | Legs | Mocopi | MediaPipe | - | | Feet | Mocopi | MediaPipe | - |

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.