NIMOS / ENGINES / MPKL
← THE BUILD SYSTEMMPKL
THE MOTION ENGINE
Motion, Physics & Kinetic Layering
The runtime and patterns behind everything that moves — with a designed still for every move.
DRAWN BY THE HOUSE
One mark per engine, on one grid, in one hand.
15
TOOLS
PROJECT
WIRE
USED
THIS BUILD
GSAP + Lenis + Motion runtime; the build-table spec cites pattern #542.
THE PROOF LEDGER →WHAT
What it is
Fifteen tools: Framer Motion, GSAP, Lenis, Motion One, Auto Animate, Floating UI, use-gesture, framer-motion-3d, Recharts, canvas-confetti, Lottie, react-player and the vanilla gesture layer. Motion Menu supplies the patterns; MPKL supplies the runtime.
WHY
Why it exists
Motion is the difference between a page that feels authored and one that feels assembled. It is also the easiest place to make a page inaccessible, so every pattern ships with a reduced-motion state and an off-screen sleep.
HOW
How it runs
npm into projects; one scroll owner per page (Lenis → ScrollTrigger), pinned physics constants, a reduced-motion still, and cleanup on unmount. The pattern number is recorded in the build spec.
WHEN
When it runs
Scroll choreography, transitions, magnetic controls, chart reveals and conversion moments. Not ambient loops for their own sake.
WHO
Who owns it
CEO owns the motion language; Research watches the ecosystem; Build writes the choreography; Data checks frame timings and reduced-motion coverage; Ops walks 1440/768/390.
TOOLS
The registry
The engine manifest is the source of truth. These are its entries, including the ones that are not used on this build — the proof ledger says which is which.
framer-motion
npmThe industry-standard animation foundation for React and Next.js.
@gsap/react
npmHigh-performance timeline animation — sophisticated multi-stage sequencing.
gsap
npmThe GSAP runtime itself (ScrollTrigger included) — required by every transplanted motion-menu GSAP pattern.
lenis
npmSmooth scroll mechanics, completely uncoupled from the DOM.
@motionone/dom
npmTiny, hardware-accelerated animations on the native Web Animations API.
auto-animate
npmZero-config transitions for lists and layout shifts — one React hook.
@floating-ui/react
npmHigh-precision anchor positioning for custom menus, dropdowns, tooltips.
@use-gesture/react
npmMulti-touch, mouse and trackpad movement tracking hooks.
framer-motion-3d
npmBridging layer bringing Framer Motion syntax into React Three Fiber scenes.
motion
npmThe successor package to Framer Motion (Motion One lineage) — CUIFMARE registry items import `motion/react`.
recharts
npmComposable, responsive, fluidly animated SVG charting.
canvas-confetti
npmLow-overhead Canvas particle system for high-impact conversion frames.
lottie-react
npmVector motion animation playback engine for predefined sequences.
react-player
npmVersatile component infrastructure for complex video feeds.
@use-gesture/vanilla
npmFramework-agnostic gesture tracking — the vanilla sibling of @use-gesture/react.
15 registry entries. The proof ledger on the Gantry page says which of them this build actually used.
RUN
Run it
ENGCTL / THE ENGINE FLOOR
$ engctl show mpkl$ engctl awaken mpkl$ engctl install mpkl --dir ./site`engctl` is the registry control surface. `awaken` checks wiring before it activates a cell; `install` writes the parts into a project.
PROOF
On this build
GSAP + Lenis + Motion runtime; the build-table spec cites pattern #542.
N/A and PARTIAL are stated, not hidden. The ledger is generated from this project, not from a template.
LIMITS
What this does not claim
The proof file says USED for GSAP/Lenis/Motion. It does not claim every pattern in the library was used.
The engine is the how. The brief is the start.