Back to corpus
architecturetechnical paper candidatescore 28
Full Stack Map
This map uses source-verified component names. It intentionally avoids old summary claims such as "SAN 135K", "5,408 pairs", "validation loss 0.028", or "LIM-RPS is the production brain" unless a source file proves them.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
This map uses source-verified component names. It intentionally avoids old summary claims such as "SAN 135K", "5,408 pairs", "validation loss 0.028", or "LIM-RPS is the production brain" unless a source file proves them.
- Rust `echelon_get_dynamics_128`. - Swift `EchelonBridge.getDynamics128()` overlay helper. - SAN flat input from Rust SAN FFI. - `DiffusionService.buildDynamicsVector()`.
These are not yet one perfectly invariant contract. The docs should state where each consumer gets its vector.
That path does not use the Swift overlay helper that injects pose/mocopi/watch slots. The overlay helper is still important, but it is not automatically the input to every downstream consumer.
- `san_manifest.json`: 76 tensors, 164,248 total parameters. - `san_weights.bin`: binary weights corresponding to that manifest.
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.