# INTERFERENCE — Good chaos

## 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/interference.stream-7e644c00.mp4
- Poster (still fallback only): https://media.scrollhaus.ai/thumbs/interference.19a5c4c7a2b5.webp
- Scene source · sphere loop video, 720×1280 H.264, phones: https://media.scrollhaus.ai/sites/interference/assets/orb-720.mp4
- Scene source · sphere loop video, 1080×1920 H.264, desktop: https://media.scrollhaus.ai/sites/interference/assets/orb-1080.mp4

Additional source assets. For each grouped list, prepend its base URL to each filename or path exactly as written.
- Base URL https://media.scrollhaus.ai/sites/interference/ → assets/seq/001.webp · assets/seq/080.webp · assets/seq/235.webp · assets/seq/395.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 complete, responsive, scroll-driven experimental studio website built around a supplied 15-second portrait motion piece of a revolving particle sphere. The sphere is one seamless 14.2-second loop (all 450 source frames, the last 24 cross-blended into the first) encoded as H.264 at 1080×1920 for desktop and 720×1280 for phones. The page downloads the whole loop first and plays it from memory, so it can never stall mid-revolve; while it loads, the first frame turns slowly (clipped to the sphere), and scrolling spins the sphere up to 1.8× before it eases back. The experience has four narrative beats, an editorial manifesto, three visual studies, and a working contact action.

Palette and type: --pink: #f677a5.
Font families: Space Grotesk,sans-serif / DM Mono,monospace.
Font stylesheet: https://fonts.googleapis.com/css2?family=DM+Mono:wght@400;500&family=Space+Grotesk:wght@400;500;600;700&display=swap

## Layout and copy
“GOODCHAOS.” → “Break thepattern.” → “Colour outsidethe code.” → “Make somebeautiful noise.” → “Leave asignal.” → “IF IT FEELSDIFFERENT,IT'S WORKING.” → “THEUNEXPECTED.” → “LET'S MAKEA SCENE.”
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
Match the recorded page’s distinctive text entrances, section transitions and hover/scroll states using the detailed motion notes in the JSON map. Hero: a 480–560vh runway with a fixed stage. The sphere is a <video muted playsinline loop autoplay> fed from a fully downloaded Blob of https://media.scrollhaus.ai/sites/interference/assets/orb-1080.mp4 (phones with a coarse pointer and a short side ≤820px use orb-720.mp4); until it plays, an <img> of seq/001.webp sits in the same place, rotates 7.5°/s × the current spin rate, and is clipped with clip-path circle(0.44 × drawn frame width) so the frame's corners never show, then crossfades out over .9s on the video's first 'playing'. Scroll velocity (sum of |Δy| per event, decayed ×0.9 per frame) sets playbackRate toward 1 + min(.8, v·.006), eased 12% per frame, settling back to 1. Scroll progress p over the hero runway drives the four beats (each visible between its data-start and data-end) and the progress bar --p. Reduced motion: no autoplay, no turning, the still stays.
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/interference.json
Visual demo: https://media.scrollhaus.ai/previews/interference.stream-7e644c00.mp4
Thumbnail / loading poster: https://media.scrollhaus.ai/thumbs/interference.19a5c4c7a2b5.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.