NKo — Notation, Memory, and Future Routing

NKo's role in the LUME stack has two layers. The first is what to build now. The second is what to build after. NKo is the durable naming and inscription layer for movement phrases. This is the immediate role, and it should be built before anything else. Every proven movement phrase should have: - A technical name (`left_hand_raise_play`, `wave`, `weighted_hold`) - A body description (landmarks, zone, timing, intent) - An evidence record (session hash, clip count, gate result) - A claim status (defined / observed / confirmed / promoted) - Optional: a NKo name assigned after the phrase is stable This is the movement alphabet. The archive of body inscriptions is how the system stops treating movement as ephemeral sensor data and starts treating it as a vocabulary with history. The NKo writing system (Solomana Kanté, 1949) fits this role because it was invented precisely to give Mande languages a durable computational structure: a notation system, a memory layer, and a cultural claim about who the language belongs to. Body movement — especially Mo's specific movement vocabulary — deserves the same treatment.