Back to corpus
architecturetechnical paper candidatescore 46
Parallel Architecture Patterns
The old page said "N'Ko CTC and LIM-RPS" as if both were equally canonical runtime architectures. That was misleading. The corrected comparison is:
Full HTML reader
Read the full artifact
Extracted abstract or opening context
The movement stack and the N'Ko ASR stack are related by pattern, not by shared implementation.
The old page said "N'Ko CTC and LIM-RPS" as if both were equally canonical runtime architectures. That was misleading. The corrected comparison is:
| Aspect | Movement / MotionMix / LUME CC | N'Ko ASR / inscription | | --- | --- | --- | | Input | camera, IMU, mocopi, watch, depth/body evidence | audio/acoustic frames | | Current runtime anchor | EchelonCore + LatentUpdater + SAN/ClaimBridge lanes | trajectory-biased Transformer CTC ASR anchor | | Routing/correction | SAN layers, BodyTruth, AirDeck safety, future routing work | MAOE-style post-ASR correction/admissibility routing | | Output | body state, audio params, visual params, DJ intent, motion claims | character sequence, telemetry, correction decisions | | Cultural grounding | embodied movement and performance practice | Mande/N'Ko phonology and writing |
- body motion is continuous but must produce stable command/audio/visual intent; - speech is continuous but must produce stable N'Ko text.
- temporal context; - confidence/freshness; - boundary handling; - recovery when tracking or recognition fails; - protection against generic priors overwriting the source signal.
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.