Back to corpus
architecturetechnical paper candidatescore 54

Comp-Core: Computational Choreography Platform

1. [Executive Summary](#executive-summary) 2. [System Architecture Overview](#system-architecture-overview) 3. [Core Subsystems](#core-subsystems) 4. [Application Layer](#application-layer) 5. [Data Flow Architecture](#data-flow-architecture) 6. [API Reference](#api-reference) 7. [Deployment Architecture](#deployment-architecture) 8. [Current Status](#current-status)

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Version:** 2.0.0 **Last Updated:** December 26, 2024 **Status:** Production Development 1. [Executive Summary](#executive-summary) 2. [System Architecture Overview](#system-architecture-overview) 3. [Core Subsystems](#core-subsystems) 4. [Application Layer](#application-layer) 5. [Data Flow Architecture](#data-flow-architecture) 6. [API Reference](#api-reference) 7. [Deployment Architecture](#deployment-architecture) 8. [Current Status](#current-status) Comp-Core is an integrated motion-to-music platform that transforms human movement into generative audio experiences. The system combines: - **Real-time Motion Capture**: Dual-source tracking via MediaPipe (camera) and Mocopi (IMU sensors) - **Audio Synthesis**: Conductor-orchestrated Strudel patterns driven by body movement - **Machine Learning**: CC-MotionGen diffusion models with RAG++ retrieval for motion generation - **Multi-Platform Applications**: iOS, Desktop (Tauri), and Web interfaces | Capability | Technology | Status | |------------|------------|--------| | Camera-based pose tracking | MediaPipe Holistic | Production | | IMU-based skeleton tracking | Sony Mocopi (6 sensors) | Production | | Real-time audio synthesis | Strudel/Tidal Cycles | Production | | Motion-conditioned generation | CC-MotionGen Diffusion | Development | | Semantic motion retrieval | RAG++ with FAISS | Development | | Cross-platform apps | Tauri, SwiftUI, Next.js | Production |

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.