THE EXPERIENCE
TEMPLATE.
Use this structure whenever you publish a new public game, technical tool, tutorial, demo, learning resource or agent experience. All fields should be filled before claiming production readiness.
Minimum public description
IDENTITY / PURPOSE
Product: [Verified product name and version]
What it is: [One accurate sentence]
Why it exists: [Problem or entertainment/learning value]
Audience: [Who should use it, prerequisites and supported devices]
USING / WINNING / FAILING
Start: [Public URL and first step]
Controls: [Input/interaction method]
Win or success: [Observable, measurable criterion]
Expected output: [What the user sees]
Error and recovery: [Failure, retry, undo, rollback]
THOUGHT / VISION / AI
Mental challenge: [Initial state → legal choice → predicted result → explanation]
Real screenshot: [Capture date, alt text, actual page path]
Video: [Intro or real demonstrated task, labeled accurately]
Accessible media: [VTT captions and full transcript]
Read-only guide: [GET JSON rules and examples; no unauthorized writes]
TRUST / EVIDENCE
Data handling: [Storage, retention, third-party dispatch]
Evidence: [Receipts and exact test scope]
Limits: [Unknowns, untested devices or unavailable features]
Release: [Canonical source, version, monitor and rollback target]
Do not insert invented videos, product screenshots, test counts, AI responses or hidden provider capabilities to make the page appear complete.