# StackPilot Start Here — Proof + Safety Companion

Status: local draft-only review sheet. No publishing, checkout, email capture, analytics, outreach, deployment, account creation, terms acceptance, payment, tax, legal, KYC, identity, private-data, or customer-system action is connected.

## Purpose

Use this sheet before launch validation, lead-magnet prep, paid-product packaging, or public proof copy. It teaches the difference between fictional samples, hypotheses, private feedback, permissioned quotes, source-backed proof, and forbidden fake claims.

## 10-year-old rule

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.
- If you do not have proof, write an honest learning claim instead of a sales claim.

## Proof ladder

### 1. Fictional sample

Can teach structure. Cannot prove demand or results.

Safe wording:

> Tiny Bookkeeping Cleanup is a fictional teaching example. Copy the structure, not the fake business.

Do not call it a case study, customer story, testimonial, or proof.

### 2. Hypothesis

Can guide questions. Cannot support public proof.

Safe wording:

> I think solo home-service owners may struggle with messy receipt workflows. This needs manual validation.

### 3. Private internal note

Can improve the product. Should stay private unless rewritten and approved.

Use pseudonyms only. Do not include emails, phone numbers, exact private quotes, screenshots, financial details, employer/customer data, or confidential notes.

### 4. Permissioned quote

Can support copy after review.

Required before use:

- real person granted permission,
- exact wording reviewed,
- private details removed,
- context is not misleading,
- Tim approves publication.

### 5. Source-backed proof

Can become a proof block after review.

Examples:

- anonymized before/after artifact,
- approved screenshot,
- delivery checklist outcome,
- permissioned metric,
- public source note.

Required: source file, permission context, privacy review, claim review, and Tim approval.

### 6. Forbidden fake claim

Cannot be used.

Never invent:

- customers,
- testimonials,
- revenue,
- conversion rates,
- screenshots,
- logos,
- before/after results,
- purchase intent,
- validation,
- “people love this” language.

## Claim rewrite examples

Bad:

> Customers use this pack to launch profitable AI businesses in a week.

Safer:

> This local worksheet pack helps you create the first visible operating file before you test the offer.

Bad:

> Real founders love the Tiny Bookkeeping Cleanup example.

Safer:

> Tiny Bookkeeping Cleanup is a fictional teaching example. Copy the structure, not the fake business.

Bad:

> AI will validate your idea and find customers automatically.

Safer:

> AI may organize your questions and draft review notes. A human approves any real share, send, capture, or offer.

## What evidence can safely unlock

| Evidence | Safe next step | Still blocked |
|---|---|---|
| Fictional sample only | Improve examples and worksheet clarity | Checkout, public proof claims, testimonials |
| Tim-supplied feedback | Update Day 01 language, FAQs, objections, and manual validation scripts | Automation, capture, public proof claims |
| Permissioned quote | Draft a proof block for human review | Names/logos/screenshots/metrics unless approved |
| Source-backed proof | Prepare public proof section or sample output | Publication until Tim approves truth/privacy/claims |

## Hermes-safe help

Hermes may:

- classify claims by proof level,
- rewrite hype into honest draft copy,
- prepare proof-review checklists,
- organize Tim-supplied feedback,
- create local files,
- run QA and verifier checks.

Hermes may not:

- fabricate proof,
- contact people,
- collect feedback independently,
- publish, send, post, deploy, or buy,
- create accounts or accept terms,
- connect email, analytics, checkout, CRM, ads, or live systems,
- use private payment/tax/legal/KYC/identity/customer/employer data.

## Final approval lock

Before any proof claim becomes public, Tim must approve the exact claim, source, permission context, privacy handling, visible asset, channel, and next action.