Back to corpus
architecturetechnical paper candidatescore 46
How It All Fits
This page is the architecture decision map after auditing the source. It replaces the older explanation that treated `LIM-RPS`, SAN, and diffusion as one completed trained stack.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
This page is the architecture decision map after auditing the source. It replaces the older explanation that treated `LIM-RPS`, SAN, and diffusion as one completed trained stack.
The system is built around an intermediate body state, not around raw sensors and not around a single opaque model.
This is still the right direction. The correction is that the current source does not prove one fully trained, end-to-end architecture. It proves several connected runtime pieces with different maturity levels.
- `EchelonCore`: Rust real-time brain state and latent/lexicon generation. - `LatentUpdater`: selectable update backend inside `cc-brain`. - `SANPipeline`: Rust neural pipeline exposed through FFI and wrapped by `SANService`. - `DiffusionService`: Swift/CoreML generation service with phone hub, CoreML, and rule-based fallback paths. - `ClaimBridge`: Rust/Swift bridge from dynamics to N'Ko-style motion claims. - MotionMix BodyTruth: shared body-state bus being stabilized for Mac4/K11.
The docs should say "these layers coordinate" rather than "one model learned the whole body-to-music system."
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.