Evidence before exhibition

Show what works.
Name what does not.

A credible demonstration explains its purpose, visible behavior and limits. Prepare an evidence card before presenting a project to others.

For a demonstration that needs an honest account.

This is a method you can read and use independently. Begin with the question, follow the prompts, and keep uncertainty visible.

Name the task, creator, version and permission to display.

List routes and controls; mark each implemented, simulated, missing or unknown.

Identify sample data, storage, external services and security boundary.

Record what was actually tested, by whom and when.

Check rights, accessibility, technical status, accuracy and support ownership.

A useful next step can be a decision to wait. The purpose is to make the reasoning available for inspection.

Your output

A demo evidence card with project identity, tested behavior, data boundaries and publication limits.

A reason to pause

Pause when display rights are unclear or a simulated feature is being described as working.