Comparative Analysis: Two Computational Choreography Documentation Sets

**Set A** — `Desktop/computational-choreography/` (45 files) Implementation-grounded, production system documentation. **Set B** — `Desktop/MotionMix/research/computational-choreography-nko-2026-05-27/` (38 files) Research-architectural, K11 AirDeck DJ control + movement language. **Set A** is the full production stack written from the inside out — reading real source files. It documents EchelonBridge, SAN, DELL, LIM-RPS, the 128D canonical vector, training data, KARL reward, the distributed camera mesh, and NKo synthesis as a future arc. The primary output is music/audio: the body drives sound through a learned latent space. **Set B** is a research design pack written from the outside in — describing what the system should become. It documents the K11 AirDeck gesture control pipeline, BodyTruth as a sensor contract, camera-first as a design requirement, the movement lexicon as a teachable dictionary, and NKo as the notation and memory layer. The primary output is DJ command dispatch: the body controls Rekordbox. Set A: The body produces a learned latent state (z*) through fixed-point convergence. That state is a compositional representation, not a button press.