showcase trained

Use one self-contained page for a narrative, a picker only for requested comparison, and a scroll cinematic only when motion is the requested surface. Non-essential interaction motion needs a way to be disabled; scroll-linked decoration is a common motion-sensitivity risk. W3C guidance. A presentation never authorizes publishing, external generation, or product-code changes.

The media query detects the operating system or user-agent reduced-motion preference. MDN reference

• Start with audience, claim, evidence, and one reader action.
• Keep essential video information available without the cinematic path; when video carries audio or narrative, provide reviewed captions and a transcript. MDN video accessibility
• Render the artifact before handoff.

• Keep HTML self-contained and use only MonoLisa Nerd Font, MonoLisa, then monospace; never load web fonts.
• Use Codex image generation only when needed and follow the local WebP/gallery delivery rule.

A focused artifact makes evidence and tradeoffs legible without changing the product.

Presentation code can become a second product; generated media can misrepresent unverified behavior.

• A screenshot or video does not prove a live feature.
• A picker helps only when variants differ on a named product axis.

No version-specific defect is recorded. Add browser release, reproduction, and issue only after observation.

• A page feels generic when the narrative lacks evidence: lead with the artifact, the data, or the interaction.
• Variants cannot be compared when they differ only cosmetically: vary layout, density, or interaction model.
• A cinematic that causes discomfort has scroll as its only path: honor reduced motion and offer the same story without scrubbing.