Visual QA / local launch guard

Catch the failures the link checker cannot see.

A pre-launch visual checklist for the Start Here system: mobile overflow, hierarchy, CTA clarity, fictional-proof labels, safety gates, print/PDF readiness, and screenshot contact-sheet workflow.

Open Markdown checklistOpen system contact sheet
Viewport set390 / 430 / 768 / 1366 / print
Design standardPremium field manual
Safety ruleNo live systems connected
DecisionLocal GO / WAIT only

Review order / before launch testing

Inspect the full beginner path before judging any one page.

Visual QA should follow the way a beginner will feel the product: choose a manual, see examples, prepare approved feedback, synthesize objections, revise the pack, then make a launch decision. Passing this checklist does not authorize live action.

Local GO / WAIT only — no public launch authority.

01Manual routerCan a beginner pick the first manual without giving data? 02SamplesAre fictional examples clearly labeled and useful? 03Validation kitAre sharing scripts and logs still approval-only? 04Revision worksheetDo exact quotes stay separate from interpretation? 05Launch cardDoes the decision stay WAIT, manual, free, or paid?

Visual surfaces to check.

These are the pages that now make up the Start Here product system. Static verification proves the links load; this page makes the operator inspect whether a beginner can actually read, trust, and use them.

01

7-Day Worksheet Pack

Hero, route cards, day selector, download buttons, and ready checklist.

mobile + desktop
02

Manual Router

Stuck-point selector, recommendation card, and seven-manual route map.

no data capture
03

Sample Artifacts

Fictional example labels, proof disclaimers, and “what done looks like” clarity.

fictional only
04

Launch Bridge

Lead-magnet, paid-product, and listing gates without live connections.

approval gates
05

Manual Validation Path

Kit, FAQ, synthesis memo, and feedback revision worksheet.

human review
06

Downloads + Print

ZIP, manifest, printable pack, and download contact sheet.

package QA

Premium object check

Does it still feel like StackPilot?

  • Field manual / operator desk instead of generic AI SaaS.
  • No neon soup, robots, fake dashboards, sparkle icons, or passive-income language.
  • Headings are readable; no cramped/wavy type or overlap.
  • Dark-to-paper transitions do not cut through CTAs or ledes.

Beginner route check

Can a new reader move?

  • Next click is obvious in under 10 seconds.
  • Route order is visible: buyer → offer → stack → agents → content → customers → delivery.
  • One primary CTA wins; secondary links do not create button soup.
  • Fictional samples are clearly not proof, customers, or revenue.

Mobile check

Does it survive a phone?

  • No horizontal scrolling at 390px.
  • Hero text, cards, and buttons wrap cleanly.
  • Long filenames and mono labels do not overflow.
  • Tap targets are separated enough for thumbs.

Safety check

Are public actions still blocked?

  • No forms, inputs, capture widgets, checkout, analytics setup, or sending flows.
  • Human approval appears before publish, send, contact, buy, deploy, accounts, terms, deletion/record changes, or private/payment/tax/KYC details.
  • Feedback stays separate from proof until Tim approves exact non-private rows.

Required surfaces / no skipped context

Check every Start Here surface that affects trust, routing, or launch risk.

The static verifier covers these routes. Visual QA should still inspect the actual hierarchy, mobile wrapping, CTA dominance, fictional-proof labels, safety locks, and no-live-field expectations on each surface.

HubPublic route bridge and operator review strip. LibraryManual shelf, Start Here CTAs, and review order. 7-day packDay cards, download links, route clarity. RouterNo-data stuck-point selector and recommendation card. SamplesFictional/safe examples and proof disclaimers. ValidationApproved sharing script, logs, and manual gates. SynthesisFeedback turns into local decision memo only. FAQObjections do not imply proof or permission. RevisionExact quote vs Hermes interpretation lane. ReadinessLaunch blockers and preflight decision states. Launch cardWAIT/manual/free/paid gates before external action. System sheetFull route/download/package QA overview. Bridge sheetStart Here bridge, public-router, and pack handoff QA.
WAITUse if mobile, hierarchy, copy, samples, package, or safety gates fail.
Manual firstAllowed only after Tim approves exact audience, script, and feedback log.
Free magnetRequires approved capture/privacy/email provider setup before any connection.
Paid pathRequires checkout, tax, terms, support, refund, and listing approval first.

Screenshot/contact-sheet workflow

When browser tooling is available, capture the Start Here system before launch.

Save screenshots locally only, then build a contact sheet with page name, mobile screenshot, desktop screenshot, pass/fail note, and fix needed. Do not publish unreleased product screenshots or Tim-only approval notes.

python3 -m http.server 8777 --directory site
# Capture at: 390x844, 430x740, 768x1024, 1366x900, 1440x1000
# Save to: business-ops/qa-screenshots/start-here-YYYY-MM-DD/
# Output: contact sheet + GO/WAIT note

Local result only

This checklist can say GO or WAIT. It cannot launch.

Publishing, deployment, email capture, checkout, analytics, outreach, marketplace listing, account creation, terms acceptance, or payment/tax/KYC work still requires Tim approval.

Use checklist