Write what was actually said.
Paste approved feedback as written. Do not clean it up until a separate revision step.
quote stays separateUse this before claims get written.
The ledger does not collect data. It is a local desk template for rows Tim has already approved for product review. The goal is to prevent a useful comment from becoming an unsupported public claim.
Explain what it means for the product.
Hermes may summarize patterns and suggest edits, but interpretation cannot become a testimonial.
local review onlyLabel what can and cannot be used.
Most rows should remain private review, objections, or revision signals until Tim approves exact public use.
Tim gateBlank row format.
This is the same structure included in the Markdown download. It is intentionally a static table, not a form.
| Row ID | Date | Source type | Manual/artifact | Exact feedback | Hermes interpretation | Evidence status | Public claim allowed? | Tim approval note |
|---|---|---|---|---|---|---|---|---|
| SP-EV-001 | YYYY-MM-DD | private review | Start Here pack | Approved exact wording only. | What this means for product edits. | private_review | No | Tim approval required before public use. |
| SP-EV-002 | objection | No | ||||||
| SP-EV-003 | revision_signal | No |
Fictional filled row.
This sample shows how to keep a useful comment, Hermes interpretation, evidence label, and public-claim permission separated. It is invented for training and cannot be used as validation proof.
| Row ID | Date | Source type | Manual/artifact | Exact feedback | Hermes interpretation | Evidence status | 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 | No | Teaching sample only. Tim approval still required before any real validation, quote use, public claim, page, CTA, platform, link, or launch path. |
Approved real row checklist.
Use this before a real reviewer comment can move beyond private product review. A row can be useful for edits and still be blocked from public quotes, sales copy, launch pages, social posts, or proof claims.
Confirm Tim approved the source and method.
Record how the feedback was collected, who approved the review method, whether the reviewer gave permission for local product review, and whether any public quote permission exists. If any part is unclear, label the row not_usable_publicly.
Remove sensitive context before synthesis.
Strip names, contact details, company/client identifiers, screenshots, account data, CRM records, payment details, private business information, and any legal/tax/KYC/identity content before Hermes summarizes the row.
Approve the exact use, not the vibe.
Tim must approve the exact quote or paraphrase, evidence label, claim wording, page, CTA, platform, link, timing, and distribution path before anything public. Anonymous still needs approval.
| 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. |
Evidence labels.
Use conservative labels until Tim has a real source, explicit permission, and a final claim ready for review.
fictional_sample
Teaching examples such as Tiny Bookkeeping Cleanup. Useful for showing what done looks like, but never evidence of demand, customer results, revenue, testimonials, or market validation.
private_review / objection / revision_signal
Good for product edits and FAQ improvements. Not for public quotes, social proof, sales pages, or conversion claims.
approved quote / verified outcome
Labels such as approved_anonymous_quote, approved_public_quote, and verified_outcome still require Tim to approve the exact claim, context, page, CTA, platform, link, timing, and distribution path. Use not_usable_publicly for private, unclear, unsupported, or sensitive rows.
Safety scope / No public action occurred
This page is a local review template only.
- No form, input, textarea, select, checkout, email capture, analytics connection, account setup, deployment, post, upload, outreach, message, purchase, CRM/API write, private-data use, or proof-claim approval is connected here.
- 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.
Next safest route: Proof/sample index → Evidence ledger → Manual validation kit → Synthesis memo → Feedback revision worksheet → Launch review only after evidence exists.
Verifier expectation: RESULT ok · bad_links=[] · js_errors=[] · forms_fields=0.