Build a pitch visitors can challenge

Build an interactive one-page explainer for [IDEA OR OFFER] aimed at [AUDIENCE]. The central claim is [CLAIM]. My evidence pack is [SOURCES AND DATA]; unknowns and limitations are [UNKNOWN FACTS]. The page should invite a visitor to ask, “How do you know?” instead of asking for blind trust.

Design three paths, each starting with a different practical question the audience might ask. Each path should reveal one concise answer, the exact supporting source or data point, one important limitation and a useful next step. Include a fourth path for “What remains unproven?” A visitor must be able to switch paths without losing context. Make the page understandable even if JavaScript fails.

First return a content map that labels every statement as source-backed, inference or proposal. Then provide semantic HTML, responsive CSS and minimal JavaScript for an accessible, keyboard-operable prototype with visible focus, reduced-motion support and no tracking or login. Put citations close to their claims and dates next to time-sensitive figures. End with tests for every path, empty or missing evidence, narrow screens and screen-reader navigation. If the evidence pack is insufficient, create clearly marked placeholders rather than inventing proof.