# Hero proof: change a real product UI issue and hand it to engineering ## User belief to change Every AI tool demos well, but none fit my real product stack, preserve context, or produce something engineering can trust. ## Current environment The viewer is AI-tool fatigued: hundreds of tools, lots of “production-ready” claims, partial wins in isolated places, and repeated disappointment when demos fail against real repos, components, handoff, or review workflow. ## Why this matters This is the first proof Mode needs. If this works, Mode feels real. If it does not, every other claim collapses into generic AI-tool noise. ## Aha moment A designer starts from a real running product surface, fixes one visible UI issue using existing context/component patterns, and produces a reviewable output engineers can inspect. ## What to show Supported existing repo/product -> live portal/product surface -> select actual UI element -> make one visible UI polish/component-aware change -> show before/after -> show component/context preservation -> show diff/branch/PR or clearly labeled reviewable output with review notes. ## Belief gates - Real product, not toy: the surface is clearly an existing product, not a generated blank app. - Stack/context fit: the workflow starts from a supported repo/product path, not a disconnected mockup. - Useful product action: one visible UI issue gets materially better. - Component/context trust: the change uses or preserves an existing component/pattern where possible. - Reviewable handoff: output can be inspected by engineering as a diff/branch/PR/export, with limitations named honestly. - No overpromise: the proof says exactly what it demonstrates and what it does not claim yet. ## Pass criteria The viewer can understand the value without being sold: this is a real product change, made in context, with an inspectable output path. No hidden manual cleanup changes the story. If there is no real PR, the artifact is not called a PR. ## Failure modes Looks like a toy/generated app; too much setup; weak or invisible UI improvement; random component output; no review path; “without engineering” or production-ready-by-default messaging. ## Claim unlocked Mode lets designers work on real product surfaces, propose useful UI changes, and hand reviewable output to engineering. ## Evidence basis - Mode W1/W6 active wedge tests - Mode W2/W4/W5 future wedge proof needs - ICP trigger: distrust of AI tools for production output - ICP trigger: design QA/handoff/visual polish friction - Public AI adoption high but trust in output fragile ## Asset outputs - 60-90 sec hero demo - 15-30 sec before/after cutdown - sample reviewable output/PR artifact - landing-page proof section - claim-boundary panel ## Priority note Make this first. The other proof angles should not distract from this until the hero proof is convincing.