Beginner

Evidence Checklist

Prove your app works with evidence: build a claim-by-claim verification pack with receipts.

5 steps15 verify checks45-60 minutesWorks with: emergent · chatgpt · claude · cursor

Start Guided Walkthrough

#evidence #verification #claims #proof #qa

The Route

0/5 verified

Inventory every claim

Collect what the product says about itself - everywhere.

3 checks 02

Define verification procedures

Each claim needs a repeatable test a stranger could run.

3 checks 03

Execute and collect evidence

Run every procedure and record what actually happened.

3 checks 04

Fix or reword failures

Reality and copy must match - change one of them.

3 checks 05

Assemble the evidence pack

Package the proof so anyone can audit it.

3 checks

Every step ends at a Verify Gate. Do not continue until every check passes.

Context Pack

Paste this first. It briefs the AI on requirements, constraints, and the Definition of Done before your first build prompt.

Context Pack

PROJECT CONTEXT:
Before I demo, submit, or ship, I want documented proof - not vibes - that every claimed feature works.

GOAL:
Produce an evidence pack: every product claim paired with a verified, reproducible demonstration.

REQUIREMENTS:
- A list of every claim the product makes
- A verification procedure per claim
- Executed evidence per claim (observed results)
- Failed claims fixed or honestly rewritten
- A final evidence pack document

CONSTRAINTS:
- Screenshots of UI are not evidence of function - actions are
- Claims that cannot be evidenced get removed or reworded

DEFINITION OF DONE:
- Every claim has reproducible evidence
- No claim overstates what was verified
- The pack lets a stranger re-verify everything
- Marketing copy matches verified reality

COMMON FAILURES TO AVOID:
- Claiming 'real-time' for polling, 'secure' for nothing-in-particular
- Evidence that is just a screenshot of the UI existing
- Untested claims shipped in the landing copy
- Verification steps nobody could reproduce

Paste this into your AI builder first. It teaches the AI what you want before you give it the build prompt.