Product shelf map / SP-SHELF-LOCAL

Compare the three launch doors without opening any of them.

A buyer-facing, operator-safe shelf for the Start Here pack. It explains manual validation, free lead magnet, and paid product paths in one place, then routes each path to the correct local review asset before email, checkout, analytics, deployment, outreach, or account systems exist.

Review the product shelfOpen Markdown sheetBack to QA sheet
StatusLocal no-capture map
PurposeCompare launch gates
AllowedReview + route
BlockedEmail, checkout, deploy

Command brief

The shelf keeps the product coherent.

The Start Here system now has many review assets. This page makes the simple public-facing path visible: the pack is the product, the proof is honest, and the next door depends on real feedback plus Tim approval.

10-year-old mode

Do not build a store until you know which door people want.

Show the pack. Learn by hand. If people ask for the file, review lead-magnet readiness. If people ask to buy, review paid-product readiness. If people are confused, improve the local pack first.

Start Here product shelf

Three paths, separated on purpose.

Safest first

Manual validation packet

Use this when there is not enough real feedback yet. Tim manually shares a reviewed asset with a tiny approved audience and records exact questions, objections, confusion, and pull.

  • No forms, email provider, analytics, checkout, deployment, or outreach automation.
  • Hermes may draft scripts and packets only.
  • Success signal: useful replies, not vanity traffic.
After utility pull

Free lead-magnet path

Use this only when right-fit readers ask for the worksheet, PDF, examples, or walkthrough. The local draft reviews value, privacy, delivery, and first metric before capture exists.

  • No email provider, account, terms, analytics, public download gate, deployment, or list automation.
  • Tim must approve privacy, sender identity, delivery, and support route.
  • Success signal: opt-ins plus useful replies or completion behavior.
After payment pull

Paid-product path

Use this only when right-fit readers ask price, buying, implementation help, or paid support. The local draft reviews package, support risk, proof limits, and delivery before checkout exists.

  • No checkout, listing, payment, KYC/tax/legal/identity data, support inbox, analytics, or public sales page.
  • Tim must approve price, refund/support terms, payment platform, and proof claims.
  • Success signal: purchase intent, preorders, paid orders, or clear buying objections.

Decision matrix

Route by evidence, not excitement.

Question
Manual validation
Free lead magnet
Paid product
Best whenFeedback is thin, polite, or untested.People ask for the worksheet or examples.People ask price, purchase, or implementation help.
Local assetPath A packet + message review + feedback log.Lead-magnet readiness draft + privacy/delivery checklist.Paid-product readiness draft + support/refund checklist.
Blocked until Tim approvesAny automated send, public posting, or contact system.Email provider, capture, analytics, deployment, account terms.Checkout, payment, listing, KYC/tax/legal/identity fields.
If weakImprove the ask and share manually again later.Return to FAQ, proof safety, or Day 01 clarity.Return to proof, support, delivery, or price clarity.

Safety lock

This is navigation, not permission.

The shelf does not authorize launch. It helps Tim compare paths before choosing one. Hermes remains local-only unless Tim explicitly approves the next external gate.

Hermes-safe

Prepare the route.

Write local copy, compare paths, update Markdown/HTML, regenerate ZIPs, run verifier QA, and organize approval checklists.

Human lock

Open a real system.

Publishing, deployment, sending, outreach, accounts, terms, analytics, email capture, checkout, payment, tax/KYC/legal/identity, support, customer data, and public proof claims require Tim.

Do not fake

Borrow confidence.

No fake customers, testimonials, revenue, screenshots, logos, validation, case studies, guarantees, or unsupported public proof claims.

QA rules

Keep the shelf draft-only until the chosen path is approved.

No captureNo forms, inputs, email provider, analytics, or public download gate.
No checkoutNo payment platform, listing, KYC/tax/legal/identity field, cart, or support inbox.
No outreachNo sends, posts, ads, account creation, terms acceptance, or customer contact.
No fake proofFictional examples stay labeled; real proof needs source/permission and Tim approval.