Motion Token Foundry is for product motion designers maintaining animation behavior across a web design system. The recurring job arrives after every interaction study, component revision, or accessibility pass: translate approved movement into consistent timing tokens, verify the result, and give the stylesheet build deterministic CSS.
The usual workaround is browser devtools plus scattered design notes. Designers copy cubic-bezier values by hand, recalculate durations and stagger delays, then author a separate reduced-motion override and hope the two versions stay aligned. Motion Token Foundry turns that brittle ritual into one authored compilation pass.
Load a motion inventory, adjust curve tension, duration scale, stagger interval, overshoot distance, and reduced-motion factor, then apply the pending controls. The app reports which declarations each control changed. Normal and reduced motion run together on one synchronized transport, making the behavioral difference visible before export.
Project marker: motion-token-foundry-2026-08-09.
The visible CSS source and downloaded stylesheet come from the same applied state. The committed validator checks deterministic ordering, canonical easing values, duration and stagger declarations, overshoot metadata, and the complete prefers-reduced-motion policy.
Live verification opens the deployed app, runs the canonical motion-inventory workflow, writes fresh CSS bytes, and reruns that validator against the result. The release only passes when the deployed workflow produces the stylesheet a browser and design-system build can actually consume.