# Core Message Extraction **Momentum through linear progression.** Code → Tests → Release is a *directional flow*, not a static state. The motion must visualize unstoppable forward motion: particles or elements advancing left-to-right, gathering pace, crossing a finish line. Hover should *accelerate* the pipeline, press should trigger a full cycle. No loops—this is a journey, not idle breathing. --- --- ## Motion Rationale **Momentum through sequential, directional flow.** The three pipeline stages fill left-to-right with staggered 120ms delays (cubic-bezier(0.16, 1, 0.3, 1)—a snappy ease-out that conveys acceleration), while simultaneous particles stream across at 1.2s total duration with 150ms inter-particle spacing. This creates **visual momentum**: each stage completion triggers the next, and overlapping particles reinforce the sense of unstoppable forward motion—code → test → release. On hover, the glow bloom (radial-gradient, opacity transition 400ms) softens the card's presence without distracting; on click, `isActive` resets particle animations (simulating a fresh deploy cycle). Duration totals 1.2s end-to-end, slow enough to feel deliberate (momentum requires time to *see*), fast enough to feel snappy. Status dot gains emphasis (opacity 1, glow) on hover, signaling readiness. No loops—this is a one-way journey, aligned with the irreversibility of shipping code.