# Axiom R9

## Motion implementation and acceptance

Implement the interactions specified in the brief. The catalogue recording is a visual reference and the poster is a loading, error or reduced-motion fallback. Implement the moving scene separately from both.
- Catalogue recording (reference only): https://media.scrollhaus.ai/previews/axiom.stream-79b0bba2.mp4
- Poster (still fallback only): https://scrollhaus.ai/thumbs/axiom.webp
- Frame sequence: https://scrollhaus.ai/sites/axiom/assets/sequence-1/{frame}.webp (frames 1–96, zero-pad to 3 digits)
- Frame sequence: https://scrollhaus.ai/sites/axiom/assets/sequence-2/{frame}.webp (frames 1–96, zero-pad to 3 digits)
- Frame sequence: https://scrollhaus.ai/sites/axiom/assets/sequence-3/{frame}.webp (frames 1–96, zero-pad to 3 digits)

Additional source assets. For each grouped list, prepend its base URL to each filename or path exactly as written.
- Base URL https://scrollhaus.ai/sites/axiom/ → assets/sequence-2/001.webp · assets/sequence-2/121.webp · assets/sequence-3/001.webp · assets/sequence-3/097.webp

For scroll-scrubbed video, use a muted inline video, wait for loaded metadata, and map section progress in both directions to the video timeline. Seek when the target changes and coalesce seeks while one is pending. For a frame sequence, draw the indexed frame to canvas as scroll progress changes. For scripted, CSS or 3D motion, recreate the triggers and transforms in the brief. Use normal playback for clips described as loops.

Test at two different scroll positions and then scroll back. Confirm the video time and visible frame change, or confirm the specified canvas, CSS or 3D state changes. If a required source fails, report its URL and the missing motion before calling the build complete.

Create a responsive React + TypeScript + Vite + Tailwind CSS website. Use small components for navigation, hero, interactive stage, content sections and footer. Put media URLs in src/lib/assets.ts and animations in cleaned-up hooks. Do not output a giant HTML file, an iframe, or a screenshot pretending to be the website.

## Design direction
A black, full-screen product film for a 6.1 kg road bike, driven by a 1250vh scroll runway. Three different clips, each a WebP frame sequence on its own canvas, take turns: clip 1 plays first; clip 2 wipes in from the right edge as a widening vertical panel; clip 3 rises from the bottom as a growing horizontal panel on white. Over the film, two "screens" of type (hero, then the spokeless wheel) fade in and out with a weight badge that drifts with parallax. Then a transparent cut-out of the bike fades in over the film, the film dissolves to white, the bike dives down and blurs away, and a centred specification sheet fades up. Every text element (.pol) samples the brightness of the frames behind it from a 32×18 probe canvas and flips its ink between white and near-black so it stays legible.

Palette and type: --font: 'Inter Tight', -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif; --ease-expo: cubic-bezier(.16,1,.3,1); --ease-strong: cubic-bezier(.23,1,.32,1); --ink: color-mix(in srgb, var(--w), var(--k) calc(var(--pol) * 100%)); --ink-fade: color-mix(in srgb, var(--ink), var(--plate) 35%).
Font families: Inter Tight, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif.
Font stylesheet: https://fonts.googleapis.com/css2?family=Inter+Tight:wght@400;500&display=swap

## Layout and copy
“Axiom R9” → “A wheel withouta single spoke” → “Six point onekilograms.”
Preserve that section order (for a one-screen concept, preserve that one-screen composition), real text and distinctive composition. Use the asset map below for additional labels, body copy, colors and asset roles. Do not add unrelated dashboard sections or generic filler.

## Motion and interaction
## 5.stage#stage (fixed, inset 0, z 0, black, opacity 1 − --stage-out): video#v1 + canvas#c1 (1280×720, cover).reveal--a#ra (fixed, top/right 0, full height, width = --reveal × 100vw, black, z 5): video#v2 + canvas#c2 anchored right, 100vw wide. A 1px hairline on its left edge, visible (--edge 1) only mid-wipe.reveal--b#rb (fixed, bottom/right 0, full width, height = --reveal × 100vh, white, z 7): video#v3 + canvas#c3 anchored to the bottom, 100vh tall, opacity 1 − --dissolve; hairline on its top edge mid-wipe.plate-out#plateout (fixed white, z 8, opacity --vidfade).outro#spec (fixed, z 8).cutout#cut.runway (height var(--runway)) creates the scroll.pill (fixed, z 50). The elements stay empty (no src); only the canvases paint. Canvases fade in (opacity 0 → 1, 420ms) on their first painted frame.
Use React refs for canvas/video/3D and effects with cleanup for listeners and animation frames. Keep scroll progress reversible and independent of React rerenders. Match the demonstrated interaction, not just its opening still.

## Exact media
Asset and content map (JSON, not HTML): https://scrollhaus.ai/build-assets/axiom.json
Visual demo: https://media.scrollhaus.ai/previews/axiom.stream-79b0bba2.mp4
Thumbnail / loading poster: https://scrollhaus.ai/thumbs/axiom.webp
- AXIOM R9 road bike in the product showcase: https://i.ibb.co/SDws9KFm/bike-rock-transparent-1.png
- asset: https://scrollhaus.ai/sites/axiom/assets/sequence-1/001.webp
- asset: https://scrollhaus.ai/sites/axiom/assets/sequence-1/096.webp
- Sequence: https://scrollhaus.ai/sites/axiom/assets/sequence-1/{frame}.webp; frames 1–96, 3-digit zero padding (001, 002…). Load the first frame immediately, then progressively fill the range; do not wait for every frame.
- Sequence: https://scrollhaus.ai/sites/axiom/assets/sequence-2/{frame}.webp; frames 1–96, 3-digit zero padding (001, 002…). Load the first frame immediately, then progressively fill the range; do not wait for every frame.
- Sequence: https://scrollhaus.ai/sites/axiom/assets/sequence-3/{frame}.webp; frames 1–96, 3-digit zero padding (001, 002…). Load the first frame immediately, then progressively fill the range; do not wait for every frame.
Read the JSON map before implementing; its referenceNotes contain the full design and motion details. Follow this React/TypeScript instruction when historical notes mention a different stack or standalone HTML. Keep source media at neutral saturation and contrast; do not add colour boosts. Use its exact URLs, including query strings. Resolve every asset independently; do not turn the thumbnail into the full-screen hero. Do not replace missing media with stock pictures. Report a failed URL and keep a useful loading/error state.

## Responsive behavior and finish
At 1440×900 keep the reference's text/image balance. At 390×844 stack content deliberately, use touch equivalents for hover/drag, keep faces/products uncropped, and avoid horizontal overflow. Videos that loop must be muted and playsInline; do not hide real scroll motion behind an autoplay loop. Honor reduced motion, keep keyboard access, and pause offscreen/hidden-tab rendering.

Run the production build. Check desktop and phone layouts, every supplied image/video/model, the main interaction in both directions, navigation and CTAs. Keep demo-only forms/cart UI local unless a backend is explicitly requested. Compare against the reference; report any unverified differences rather than claiming a guaranteed match.