Field-School Evidence Expedition Log

Design and implement Ridgebook, a mobile-first field-school task log for an adult ecology workshop. The learner is following a fictional creek transect itinerary and needs to complete one observation with evidence before the next safe task unlocks. The interface must not identify a real species, replace an instructor, provide survival guidance, or imply that demo evidence was collected in the field.

Treat the feed as a working expedition log rather than a list of generic task cards. Use a route header, ordered field tasks, a visible kit and safety check, one evidence tray, an instructor-review state, and an unlock marker. Every task, evidence record, warning, and control must be semantic HTML; no decorative map or specimen illustration is needed.

Use this exact demonstrated content: RIDGEBOOK; Creek transect 02 · training itinerary; Scenario field conditions; Field kit checked; Red flag: do not taste or handle an unknown specimen; Check weather board; Complete; Specimen observation; Active; Photograph leaf underside; Record vein count; Demo photo record LEAF-07; 7 visible lateral veins; Species ID pending instructor review; Stamp observation evidence; Evidence stamped; Map canopy edge; Locked until evidence; Unlocked · walk with instructor; Return before 15:30 scenario time; Next safe task ready. Do not add student names, grades, real coordinates, species claims, weather claims, dangerous collection instructions, badges, streaks, points, or invented learning outcomes.

Use field green #254f43, log paper #f0ead6, blaze orange #e5683f, route blue #2c6d85, safety yellow #e0bd45, ink #202521, and pencil #777970. Pair a sturdy field-manual display with a clear sans and mono evidence notation. Use ruled log lines, durable tabs, evidence stamps containing words, ordered task numbers because the itinerary is sequential, and one clear locked-to-unlocked transition. Avoid generic cards, gradients, outdoor stock photos, map art, emoji, phone frames, and handmade SVG/CSS illustration.

Stamp observation evidence is the deterministic five-second action. During 0–1.0 seconds the kit and safety check are verified for this training itinerary. During 1.0–2.5 seconds Demo photo record LEAF-07 and 7 visible lateral veins stamp into the evidence tray. During 2.5–4.0 seconds Specimen observation changes from Active to Evidence stamped while Species ID pending instructor review remains explicit. During 4.0–5.0 seconds Map canopy edge changes from Locked until evidence to Unlocked · walk with instructor and Next safe task ready settles. The sequence must replay deterministically and must not fabricate a real upload or identification.

Support active-task, kit-checked, safety-warning, evidence-validating, evidence-stamped, instructor-review-pending, next-task-locked, next-task-unlocked, empty-evidence, offline-log, loading, error, visible-focus, and reduced-motion states. The evidence tray uses read-only demo records; the learner can inspect them but cannot imply a live photo. Keyboard users can traverse tasks, activate the stamp, and open safety details. Announce task completion and unlock once. Put one data-preview-ready marker on the settled log and exactly one data-preview-action marker on Stamp observation evidence.

Design natively for 390×844 without a device frame. Keep the active observation, safety warning, action, stamped evidence, and unlocked next task legible without horizontal scrolling at 320px. At 960×600, show the same log at a readable width beside a compact route-and-kit index; do not transform it into a dashboard. With prefers-reduced-motion or Save-Data, show the final stamped evidence and unlocked instructor-led task immediately while preserving every control.

Return one complete standalone responsive HTML document using internal CSS and JavaScript. Use no framework, external runtime, camera API, location API, real upload, stock image, placeholder, handmade SVG/CSS illustration, emoji, lorem ipsum, or prose outside the product. Include one quiet source-prompt link and label all route, evidence, condition, and time values as scenario or demo data.