Community Field-Signal Waitlist Station

Build a high-fidelity responsive waitlist launch page for Flockline, an AI-assisted field companion for volunteer bird-migration observers. The visitor has limited evenings free and wants to know whether the product supports a real nearby listening shift before sharing an email. Flockline may organize human observations and suggest note structure, but it must never present an automated species identification as certain. The first viewport must prove one job: choose a local observation window, understand its conditions, and receive a compact demo field pass.

Compose the page as a working community-science signal station, not a startup hero with a product screenshot. Use a dispatch log, one live field plot, three nearby observation windows, a conditions strip, and a paper confirmation printer as one connected instrument. Avoid a text-left/mockup-right hero, metric cards, AI glow, satellite-photo background, floating chatbot, generic gradient, testimonial strip, or decorative map pins.

Use this exact demonstrated content: FLOCKLINE; Listen where the migration is moving.; Community field preview · scenario data; Hudson North; Cedar Ridge; Brackish Point; Tonight · 10:40–11:20 PM; Light north wind; Low cloud; Bring headphones + red light; Join this watch; observer@fieldnotes.test; Demo only — nothing is sent.; FIELD PASS 04; Cedar Ridge listening watch; Check in at the east trail marker; Notes stay yours. Include a second available window and one capacity-unavailable window, but do not invent user counts, detection accuracy, conservation impact, partner logos, endorsements, or a launch date.

Art-direct the station with midnight ink #142231, field paper #f1ecd9, marsh green #52705a, signal coral #ef6b4a, survey blue #276c8a, and pencil gray #6d716c. Pair a compact humanist display face with a highly legible sans and mono dispatch notation. Use field-book rules, punched registration marks, a calibrated time axis, square controls, and restrained paper shadow. The plot may use deterministic Canvas, but every station, condition, and selected route needs an equivalent semantic list. Do not draw a decorative illustration with CSS or SVG.

Join this watch is the deterministic five-second preview action. During 0–1.0 seconds the Cedar Ridge row engages and the station reports that the demo slot is being checked. During 1.0–2.5 seconds a fixed signal sweep crosses the field plot and the route from Hudson North to Cedar Ridge becomes legible. During 2.5–3.8 seconds the chosen time, wind, cloud, and kit notes align in the dispatch log. During 3.8–5.0 seconds FIELD PASS 04 prints with the east trail marker check-in and Notes stay yours, then the interface settles. The sequence must be repeatable and must not send or store the sample email.

Support idle, checking, selected-window, pass-ready, invalid-email, capacity-unavailable, offline-demo, visible-focus, reduced-motion, and Canvas-fallback states. Use a real labeled email input populated with the reserved .test address for the demo; entering an invalid address shows a specific inline correction. The unavailable window must explain that no demo place is held. Announce material changes through a polite live region, never rely on color alone, and keep every station usable by keyboard. Put one data-preview-ready marker on the settled root and exactly one data-preview-action marker on Join this watch.

At 960×600, keep the brand, dispatch log, local plot, window list, and emerging field pass within the first 16:10 composition. Below 720px, order the content as purpose, available windows, selected conditions, action, field pass, then the simplified plot; never require horizontal scrolling, and keep the action visible at 320px. With prefers-reduced-motion or Save-Data, render the final Cedar Ridge pass immediately, stop the sweep, and preserve all validation and window-selection behavior.

Return one complete standalone responsive HTML document with internal CSS and JavaScript. Use no framework, external runtime, network request, live location, stock map, placeholder image, handmade SVG/CSS illustration, lorem ipsum, copyrighted mark, or explanatory prose outside the product. Include one quiet source-prompt link and label all locations, weather, availability, and routing as preview or scenario data.