Back to corpus
research noteexperiment writeup candidatescore 24

128D Dynamics Vector - Verified Contract And Caveats

The old page described one universal "canonical vector." The source is more complicated. There are several 128D-adjacent paths that overlap but are not identical.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

The old page described one universal "canonical vector." The source is more complicated. There are several 128D-adjacent paths that overlap but are not identical. - `Desktop/Comp-Core/core/audio-media/cc-echelon/crates/cc-brain/src/lib.rs` - `Desktop/Comp-Core/core/audio-media/cc-echelon/crates/cc-brain/src/ffi.rs` - `Desktop/Comp-Core/core/audio-media/cc-echelon/crates/cc-brain/src/san/mod.rs` - `Desktop/MotionMixApp/MotionMixApp/Services/EchelonBridge.swift` - `Desktop/MotionMixApp/MotionMixApp/Services/MocopiFeatureExtractor.swift` - `Desktop/MotionMixApp/MotionMixApp/Services/SANTrajectoryLogger.swift` - `Desktop/MotionMixApp/MotionMixApp/Services/DiffusionService.swift` This is the Rust-side dynamics vector. It is the base source for several Swift consumers. `EchelonBridge.getDynamics128()` calls `echelon_get_dynamics_128(...)`, then overlays Swift-side state: `flatten_latent(...)` writes a 128D vector from the Rust `LatentState` fields. Its comments reserve `[76:104]` for Swift-filled sensor fusion, but that function itself does not call `EchelonBridge.getDynamics128()`.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

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.