Proof + safety / SP-PROOF-LOCK

Teach proof before launch pressure.

A no-form companion sheet for beginners who confuse examples, hypotheses, feedback, and proof. It shows what can be used publicly, what must stay internal, and what is forbidden to fake before any validation, lead magnet, or paid product path opens.

Use the proof ladderOpen Markdown sheet
StatusLocal no-form sheet
PurposePrevent fake proof
Used beforeValidation + launch
Live systemsNone connected

Command brief

Beginner trust breaks when examples look like proof.

Start Here already uses fictional samples so the reader can see the shape of finished work. This companion makes the label system explicit: fiction can teach, hypotheses can guide, feedback can improve, and permissioned proof can sell — but none of those are the same thing.

10-year-old mode

Do not say it happened unless it happened.

If the story is pretend, label it pretend. If the result is a guess, label it a guess. If a real person said it, ask permission and remove private details before using it.

Proof ladder

Six labels for every claim.

01 / Fictional sample

Can teach structure.

Use for examples like Tiny Bookkeeping Cleanup. Must say fictional, not proof, not testimonial, not customer data, not revenue.

02 / Hypothesis

Can guide questions.

Use when you believe a buyer has a pain but have not heard it directly. Good for manual validation prompts, not public proof.

03 / Private internal note

Can improve the product.

Use personal notes, messy observations, and pseudonym-only feedback to improve worksheets. Do not quote publicly.

04 / Permissioned quote

Can support copy after review.

Use only when a real person gave permission, private details are removed, and Tim approves the exact wording.

05 / Source-backed proof

Can become a proof block.

Use approved screenshots, anonymized before/after artifacts, delivery notes, or metrics only when source files and permissions exist.

06 / Forbidden fake claim

Cannot be used.

No invented customers, revenue, testimonials, logos, screenshots, purchase intent, validation, or “people love this” language.

Claim translation

Rewrite launch copy until the proof label is honest.

These examples keep StackPilot premium without pretending the product has market proof it does not have yet.

Do not say“Customers use this pack to launch profitable AI businesses in a week.”
Say instead“This local worksheet pack helps you create the first visible operating file before you test the offer.”
Do not say“Real founders love the Tiny Bookkeeping Cleanup example.”
Say instead“Tiny Bookkeeping Cleanup is a fictional teaching example. Copy the structure, not the fake business.”
Do not say“AI will validate your idea and find customers automatically.”
Say instead“AI may organize your questions and draft review notes. A human approves any real share, send, capture, or offer.”

Use this before choosing a launch path

What the evidence can safely unlock.

Fictional sample onlyKeep improving examples and worksheet clarity.Do not build checkout, public claims, or testimonials.
Tim-supplied feedbackUpdate Day 01 language, FAQs, objections, and manual validation scripts.Still no automation, capture, or public proof claim.
Permissioned quoteDraft a proof block for human review with exact permission context.No names, logos, screenshots, or metrics unless approved.
Source-backed proofPrepare a public proof section, sample output, or case note.Tim approves truth, privacy, claims, and publication.

Hermes-safe help

AI may label and organize.

  • Classify claims as fictional, hypothesis, private note, permissioned proof, or forbidden.
  • Rewrite hype into honest local draft copy.
  • Prepare permission checklists and proof review notes.
  • Create local files and QA contact sheets.

Human approval lock

AI may not create proof.

  • No fake customers, revenue, testimonials, screenshots, logos, or validation claims.
  • No publishing, sending, outreach, ads, capture, checkout, analytics, accounts, deployment, or terms acceptance.
  • No private customer, payment, tax, legal, KYC, identity, CRM, MLS, employer, or confidential data.

Next click

After proof labels are clear, return to the offer gate.

If all evidence is still fictional or hypothetical, improve the pack or run Tim-approved manual validation. If beginner questions keep repeating, use the FAQ desk before opening lead magnet, checkout, analytics, or deployment systems.

Open offer readinessRead FAQ deskBack to Start Here