felipefontoura/pi-strategy/strat-proof-system

Proof System

Determine what makes the offer credible without inventing anything.

Workflow

1. Load ../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md.
2. Read .ai/strategy/signal/* and .ai/strategy/offer/product-offer.md, unique-mechanism.md, and mvp-scope.md.
3. Separate available proof, missing proof, proof needed, proof the MVP can generate, claims supported now, and claims that cannot be supported yet.
4. If proof does not exist, propose demo, example, walkthrough, teardown, behind-the-scenes, prototype, or real output proof.
5. Split evidence into Proof Now and Proof To Collect in 30 Days.
6. Save .ai/strategy/offer/proof-system.md.

Output template

# Proof System
 
## Available Proof
 
## Missing Proof
 
## Proof Needed For The Claim
 
## Proof Types
 
### Product Proof
 
### Demo Proof
 
### Screenshot Proof
 
### Before / After
 
### Case Study
 
### Testimonial
 
### Authority Proof
 
### Technical Proof
 
### Process Proof
 
## Proof We Can Generate From MVP
 
## Proof Acquisition Plan
 
## Claims We Can Support Now
 
## Claims We Cannot Support Yet
 
## Credibility Risks
 
## Do Not Claim

Output quality checklist

• Available vs missing proof is separated.
• Supported vs unsupported claims are explicit.
• 30-day proof acquisition plan exists when needed.
• Credibility risks are listed.
• Do Not Claim is explicit.

Critical rules

Never invent testimonials, logos, customers, revenue, metrics, scarcity, or cases.