Back to corpus
research noteexperiment writeup candidatescore 24
Comp-Core Source Of Truth
This is the current grounding document for computational choreography. It follows the code and separates implemented runtime from research vocabulary.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
This is the current grounding document for computational choreography. It follows the code and separates implemented runtime from research vocabulary.
The implemented stack is not a single monolithic "model." It is a set of runtime bridges and crates:
> MotionMixApp gathers body and device signals, feeds them through the Rust > EchelonCore, reads latent/dynamics output, runs SAN and ClaimBridge, and uses > those outputs for audio, camera, training capture, and N'Ko motion inscriptions.
- `EchelonBridge` is `@MainActor`. - Brain access is single-threaded by design. - Audio uses a separate `AudioHandle`. - `isEnabled` must be true or `step(dt)` returns immediately. - `SANService` is owned by `EchelonBridge`. - `ClaimBridgeService` runs after `echelon_get_dynamics_128`.
- a pluggable `LatentUpdater`; - `SectionStateMachine`; - `LexiconController`; - sensor frame buffer; - current `LatentState`; - current `SectionState`; - current `Lexicon`; - current `UIState`; - `WindowAligner`; - `AnticipationAdapter`; - pose/gesture caches; - temporal integrator; - pocket FFT tempo source; - Femto skeleton encoder.
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
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.