# Start Here Evidence Ledger Template

Status: local review template. Use only after Tim approves the audience, wording, validation method, and feedback log. This file is not a form, CRM, survey, email capture system, analytics event, checkout record, testimonial release, or public claim source.

## Purpose

Separate real Tim-approved validation notes from fictional teaching examples before any public copy, launch page, social card, sales page, checkout, marketplace listing, or proof claim is considered.

## Ledger rules

- Record only feedback Tim approved for local product review.
- Do not add private contact details, private business data, screenshots, CRM records, payment details, tax/legal/KYC/identity details, or confidential customer information.
- Keep exact reviewer language separate from Hermes interpretation.
- Label every row as `private_review`, `approved_anonymous_quote`, `approved_public_quote`, `objection`, `revision_signal`, or `not_usable_publicly`.
- A row is never launch approval by itself. Tim still approves the exact claim, page, CTA, platform, link, timing, and distribution path.

## Evidence status labels

| Label | Meaning | Public use |
| --- | --- | --- |
| `fictional_sample` | Teaching example created locally | Never use as proof |
| `private_review` | Feedback Tim allowed for local review only | Do not publish |
| `approved_anonymous_quote` | Exact quote may be paraphrased/anonymized if Tim approves the final copy | Tim approval required |
| `approved_public_quote` | Reviewer gave explicit written approval for exact public use | Tim approval still required |
| `objection` | Useful concern or blocker | May inform product edits |
| `revision_signal` | Repeated confusion or missing step | Use for local edits first |
| `verified_outcome` | Outcome backed by source documentation Tim approved for that claim | Claim-by-claim approval required |
| `not_usable_publicly` | Private, unclear, unsupported, or sensitive | Never use publicly |

## Blank ledger

| Row ID | Date | Source type | Manual/artifact reviewed | Exact feedback or observation | Hermes interpretation | Evidence status | Private details removed? | Product change suggested | Public-claim allowed? | Tim approval note |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| SP-EV-001 | YYYY-MM-DD | private review / owner review / manual test | Start Here pack / Manual 01 / Manual 02 / etc. | Paste only approved exact wording here. | What the feedback means for the product. | private_review | yes / no | Keep / revise / retest / wait | no | Tim approval required before any public use. |
| SP-EV-002 | YYYY-MM-DD |  |  |  |  |  |  |  | no |  |
| SP-EV-003 | YYYY-MM-DD |  |  |  |  |  |  |  | no |  |

## Fictional filled row example

This row is invented for training. It shows how the ledger should separate exact wording, interpretation, evidence label, and public-claim permission. It is not market proof, a testimonial, customer feedback, revenue evidence, launch approval, or permission to contact anyone.

| Row ID | Date | Source type | Manual/artifact reviewed | Exact feedback or observation | Hermes interpretation | Evidence status | Private details removed? | Product change suggested | Public-claim allowed? | Tim approval note |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| SP-EV-SAMPLE-001 | Fictional | fictional owner-review rehearsal | Start Here pack / Day 02 offer one-liner | “I understand the tiny bookkeeping cleanup example, but I would want one more before/after line before showing this to a real buyer.” | The sample likely needs a clearer before/after sentence. This is a product-edit signal, not demand proof, testimonial language, or launch permission. | fictional_sample | yes | Revise sample only | no | Teaching sample only. Tim approval still required before any real validation, quote use, public claim, page, CTA, platform, link, or launch path. |

## Fictional sample boundary

The existing Tiny Bookkeeping Cleanup examples are useful teaching samples. They are not demand proof, customer proof, revenue proof, testimonials, market validation, screenshots, case studies, endorsement claims, or launch approval.

## Approved real row checklist

Use this before a real reviewer comment can move beyond private product review. A row can improve the product and still be blocked from public quotes, sales copy, launch pages, social posts, or proof claims.

| Gate | Required before public use | If missing |
| --- | --- | --- |
| Source approved | Tim-approved audience, reviewer, collection method, and local-use purpose are documented. | Keep as `private_review` or `not_usable_publicly`. |
| Exact wording preserved | Original quote/objection is stored separately from Hermes interpretation and edits. | Use only as a product revision signal. |
| Private details removed | No personal, business, customer, CRM, account, payment, legal, tax, identity, or confidential details remain. | Do not synthesize for public copy. |
| Permission scope clear | Public quote, anonymous quote, paraphrase, or outcome-claim permission is explicit and narrow. | No quote, testimonial, or proof claim allowed. |
| Claim reviewed | Exact claim, page, CTA, platform, link, timing, and distribution path are reviewed by Tim. | Row may inform local edits only. |

Approval rule: anonymous use still needs Tim approval. Do not turn exact feedback, objections, or repeated patterns into testimonials, customer proof, revenue proof, conversion claims, endorsement claims, or launch permission without an approved real row and exact public-use review.

## Safe synthesis prompt

```text
You are helping review StackPilot Start Here validation notes.
Use only the evidence rows pasted below.
Keep exact quotes separate from interpretation.
Label every claim as private_review, approved_anonymous_quote, approved_public_quote, objection, revision_signal, verified_outcome, or not_usable_publicly.
Do not invent market demand, revenue, testimonials, customer outcomes, screenshots, logos, conversion results, or public proof.
Output:
1. Product edits to make locally.
2. Objections to answer in the manual.
3. Claims still blocked.
4. Claims Tim could review later, with exact evidence row IDs.
5. Next safest step: wait, revise, retest manually, prepare free lead magnet copy, or prepare paid-product copy for review.
```

## Human approval lock

AI may summarize, classify, score, route, draft local notes, and create local files. Humans approve publishing, sending, contacting, buying, account changes, terms acceptance, deployment, deletion, checkout, analytics, email capture, private details, compliance-sensitive claims, and every public use of evidence.