0054. Native motion, morphs and skeletons live in the engine adapter, not crates/runtime
- Status: Accepted (Mik, 17 Nov 2026)
- Date: 2026-11-14
- Decided by: native render domain (wave 5), pending Mik's approval
- Planning item: WP12 (motion and islands)
Context
WP12's brief gave the native motion solver and skeleton sizing to crates/runtime (src/motion/**, src/skeleton/**), and decision 0059 said crates/runtime/src/skeleton would draw native skeletons. Meanwhile the native target became ReactLynx behind the engine adapter (decision 0045). The engine already draws presets, glides, boundaries and skeletons, and now morphs and islands too, in TypeScript running in the bundle. Nothing on the native side loads Rust: rung 2 waits for its spike (decision 0076).
Decision
Native motion, morphs, islands and skeletons stay in the engine adapter (packages/engine/src/motion.tsx, morph.tsx, island.tsx, boundary.tsx, shapes.ts). crates/runtime keeps what it has: the execution ladder's runtime side and the list-move solver (decisions 0076 and 0077). The WP12 brief's owner paths and the runtime README say so.
A Rust solver would be worth porting only if measurement on a device shows a motion or sizing path is too slow in the bundle's script, and once a native target can load Rust (decision 0076's spike).
Alternatives considered
| Option | Why not |
|---|---|
Port the solver and sizing to crates/runtime now | Nothing on a phone can call it; the code would be untested on the device and duplicated in the engine |
| Keep the brief as written and leave native motion unbuilt | Native would keep refusing morph and lack islands |
Consequences
- One implementation on native, in the only place Lynx is imported.
crates/runtime's README no longer promises a motion solver or skeleton sizing.