See Motion for the decided part of this page.
Known issues
Divergences are where code and design intent disagree; open decisions are where nothing
has been decided yet. Neither is resolvable by inference.
Gaps in the current rules
This foundation has more gaps than settled rules. Do not infer answers.
- No reduced-motion handling exists in the token layer. No token, no media query, no
documented pattern. This is the most significant gap in Foundations — see
Constraints Titan should enforce below.
- No Invoca intent is recorded for any value. Whether 300ms is right for Titan’s
surfaces has not been asked.
- The duration-to-use mapping on this page is proposed, not transcribed. Nothing binds
a named duration to a component, so which duration a Drawer actually uses is a
component-level fact this page cannot assert.
- No curve is named for what it does. The easings are named by shape, not by purpose,
so there is no shared vocabulary for “how Titan moves.”
- No guidance exists on animating layout properties. Nothing says whether to prefer
transform/opacity over height/top, which is a performance decision with a visible
cost on long tables.
Constraints Titan should enforce
These are real, currently-true rules. Nothing in code stops a builder from violating them today — each is a placeholder for a guardrail Titan hasn’t built, not a decision still being made.
Last modified on September 17, 2026
