A useful demo has a narrow claim. It names its prerequisites, uses an inspectable input, produces visible evidence, and states what remains unproven.

Recipe contract

Every recipe in this manual follows the same sequence:
1

Name the claim

Decide exactly what the run should demonstrate. “It works” is not specific enough.
2

Declare the boundary

Identify required accounts, providers, downloads, credentials, and network calls before running anything.
3

Use a stable input

Prefer bundled sample data, a deterministic seed, or an explicit health check.
4

Capture evidence

Keep the source rows, state snapshot, byte comparison, test output, or health report that supports the claim.
5

Record what it did not prove

A local success does not establish production security, scale, or compatibility with an untested environment.

Choose a recipe

Run showcase recipes in a disposable checkout. Never substitute production credentials or customer data for a bundled fixture.

What these demos do not certify

  • independent security review;
  • performance under production load;
  • behavior outside the documented platform range;
  • correctness of an external model or provider;
  • future roadmap capabilities.
The build and release proof page explains how a demo becomes one part of a broader evidence bundle.