Back to corpus
architecturetechnical paper candidatescore 32
Generative Output Overview
Generative output is the part of the system that turns body state into sound, visuals, camera decisions, DJ control, and inscriptions.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
Generative output is the part of the system that turns body state into sound, visuals, camera decisions, DJ control, and inscriptions.
The old version of this page overstated SAN training and treated the output layer as if one trained model controlled everything. The current source shows multiple lanes with different maturity levels.
- Rust Echelon audio handle renders audio. - MotionMixApp bridges brain state to audio. - SAN can produce adaptive output parameters. - `DiffusionService` can generate token grids through phone hub, CoreML, or fallback paths.
- Unity/LUME receives skeleton/body/motion data. - Mac4 currently feeds Unity from mocopi locally. - DYK/LUME visuals should eventually consume stable BodyTruth, but direct local mocopi feed is currently the more stable visual path.
- K11 owns Rekordbox command safety. - Gesture detection can use camera pose even when mocopi is off. - mocopi improves accuracy but must not be a hard requirement for basic camera gestures.
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.