# Mesa Alta

## 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/mesa-alta.stream-c9c89565.mp4
- Poster (still fallback only): https://scrollhaus.ai/thumbs/mesa-alta.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
Ten rooms and three pools at the foot of a mesa in northern New Mexico, told in five numbered chapters in warm adobe browns, clay orange and night blue, set in Fraunces with Space Mono labels. A film-grain overlay drifts over everything and a clay dot cursor follows the mouse. The hero is a dusk sky with a sun and two mesa silhouettes; its second paragraph block opens on first scroll. Chapters: the water (a pool plan that draws itself, three pool cards that swap an illustration and quote on hover), the year (four seasons), the rooms (three), "A day" (a 500svh pinned stage that steps through five times of day), and a closing "stay" footer. A floating pill dock in the header tracks the current chapter.

Palette and type: --bg: #1c150c; --bg2: #241a0e; --paper: #efe3ca; --paper2: #e6d5b4; --ink: #201809; --pad: clamp(22px,5vw,84px).
Font families: Space Mono, monospace`..
Font stylesheet: https://fonts.googleapis.com/css2?family=Fraunces:ital,opsz,wght@0,9..144,300..700;1,9..144,300..700&family=Space+Mono:wght@400;700&display=swap

## Layout and copy
“You will be met at the gate and after that nothing is asked of you.” → “The water was here first.” → “The bloom you arrived on lasts ten days.” → “Spring” → “Summer” → “Autumn” → “Winter” → “No architect drew these rooms. The land did.” → “El Mirador” → “La Madriguera” → “El Rincón” → “Every season hereends in the samewarm water.”
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.2s, infinite.7) ring.35.6s) and show random digits every 120ms for 2000ms, then "000". Hides at 2150ms or 550ms after window load, whichever first (350/0ms under reduced motion).28em uppercase paper2), baseline-aligned, gap 10px.5) with blur(10px).4). Active item = the chapter whose section is between top 55% and bottom 25% of the viewport (ScrollTrigger onToggle).
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/mesa-alta.json
Visual demo: https://media.scrollhaus.ai/previews/mesa-alta.stream-c9c89565.mp4
Thumbnail / loading poster: https://scrollhaus.ai/thumbs/mesa-alta.webp


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.