Latent Representation Overview

Full HTML reader

Read the full artifact

Extracted abstract or opening context

The representation layer is where raw body data becomes a compact state that the rest of the system can use. The current source does not justify saying there is one canonical "LIM-RPS" runtime brain. The verified names are: - `EchelonCore` - `LatentUpdater` - `SimpleLatentUpdater` - `LearnedLatentUpdater` - `DellLatentUpdater` - `SANPipeline` - `DiffusionService` - `ClaimBridge` `LIM-RPS` remains a real term in older/research code, especially `motion-bridge/src/lim_rps.rs`, but docs should treat it as historical/research vocabulary unless discussing that file directly. - mocopi bones are high-dimensional; - camera pose can drop or mirror; - watch data arrives at a different rate; - phone IMU and camera features have different noise; - MotionMix BodyTruth can stall if the hub is overloaded.

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.