Status: Phase 1 stub. Phase 2 token shipment landed (see §7.6 maturation log below). Matures in Phase 5 per §8.1.

§7.6 maturation log

Per the Phase 1 go-condition in Design/0000-hig-diagnostic.md §7.6 step #4, the named-motion token shipment proceeded in four commits:

8f0a785 — Phase 1 P1: motion.duration.* and motion.named.* entries added to tokens.json; tokens.css + Tailwind extends regenerated. The illustrative vocabulary in this stub (motion.enter / motion.exit / motion.shift / motion.attention / motion.handoff) is now resolvable as token names.
b3cdfc2 — Phase 1 P2: globals.css retrofitted to consume named motion tokens — signature transitions, loading dots, and message-in springs no longer carry raw transition-duration or raw cubic-bezier curves.
7023909 — Phase 1 P3 base: raw-rgba glow sweep on /app/page.tsx + /app/landing/page.tsx (companion sweep — glows pulsed via animate-pulse were the §7.2 follow-up trigger).
9bbe8ae — Phase 1 P3 extension: residual raw-rgba glow values across 6 component files tokenized.
fee2275 — Phase 1 P4: this maturation log added (F-2 + F-6 §7.6 stubs converted to maturation logs documenting the P1–P3 commits and remaining P5 follow-ups).
c2634c3 — Phase 1 P5: ESLint strict-fail rule epoch-shield/no-raw-motion-values shipped in eslint-rules/no-raw-motion-values.cjs. The rule bans three raw-motion shapes inside src/**: (1) Tailwind arbitrary durations duration-[Nms] / duration-[N.Ns]; (2) inline CSS transition-duration: / animation-duration: literals; (3) the transition: shorthand with a raw duration component, including the React inline-style object form style={{ transition: 'opacity 200ms ease' }} and style={{ transitionDuration: '200ms' }} (detected via Property AST visitor on the transition / transitionDuration / animation / animationDuration keys). Carve-outs: src/components/design-system/generated/** (token output) and **/*.stories.{ts,tsx,js,jsx} (Storybook fixtures retain literals by design). Sweep at landing: 0 violations — the §7.2 globals.css retrofit and the named-token shipment had already drained the surface. The rule is now hard-enforced.

Phase 1 P5 is complete for motion. The contract this stub stipulates is enforced at the build gate.

Statement

Motion is named by meaning, not duration. A token like motion.enter or motion.dismiss carries the semantic intent; the duration and easing curve are implementation details that may shift across phases. Components reference motion names. Raw transition-duration and raw timing curves are forbidden in src/**.

Why

The audit found 23 transitions across the app at four different durations (140ms, 180ms, 220ms, 260ms) for nominally the same intent ("element enters the viewport"). The inconsistency is invisible in any single screen but cumulatively the app feels uncalibrated. Naming motion by meaning forces the calibration question once, at token-definition time, instead of repeatedly at every transition site.

It also makes the reduced-motion fallback contract (A-2) tractable: every named token has a single reduced-motion equivalent. Raw values can't be mapped that way without case-by-case audit.

How

Phase 2 ships motion tokens as part of tokens.json (§2.8). Vocabulary entries (illustrative, full set decided in Phase 5):

motion.enter — element appears
motion.exit — element dismisses
motion.shift — element repositions in flow
motion.attention — element pulses to draw the eye (rare; gated by motion-preference)
motion.handoff — element transforms across routes (e.g. shared-element transitions)

Until Phase 2 lands, primitives shipped in Phase 1 use raw values that ESLint will flag at the Phase 2 cutover; §7.4 documents the planned retrofit.

Phase 5 deepens this stub with the full vocabulary, easing curves per token, and per-component citations.