# StackPilot Start Here — Visual QA Checklist

Status: local review worksheet. This is not a public launch, deployment, analytics connection, email capture, checkout, or outreach authorization.

## Purpose

Use this checklist before Tim turns the Start Here pack into a public page, lead magnet, marketplace listing, or paid product. It catches the expensive-looking failures that static link checks cannot see: mobile overflow, unreadable headings, broken hierarchy, too many buttons, confusing safety gates, and screenshot/contact-sheet gaps.

## Required review order

Visual QA should follow the way a beginner will feel the system. Do not pass an isolated page until the route around it also makes sense.

1. Manual router — can a beginner choose one first manual without giving data?
2. Sample artifacts — are fictional examples clear, useful, and not presented as proof?
3. Manual validation kit — are sharing scripts, audience choice, and logs still approval-only?
4. Synthesis memo — does approved feedback become a local decision memo before any public action?
5. Feedback revision worksheet — are exact reviewer quotes separate from Hermes interpretation and smallest safe edits?
6. Launch review card — does the decision stay WAIT, manual-first, free-magnet, or paid-path?
7. Contact sheets/downloads — do the full product, manifest, printable pack, and ZIP match what the pages promise?

## Pages to visually inspect

1. `site/pages/start-here.html`
2. `site/pages/ai-business-guides.html`
3. `site/pages/start-here-7-day-worksheet-pack.html`
4. `site/pages/start-here-manual-router.html`
5. `site/pages/start-here-sample-artifacts.html`
6. `site/pages/start-here-launch-readiness.html`
7. `site/pages/start-here-launch-review-card.html`
8. `site/pages/start-here-manual-validation-kit.html`
9. `site/pages/start-here-manual-validation-synthesis.html`
10. `site/pages/start-here-public-page-copy-pack.html`
11. `site/pages/start-here-launch-path-brief.html`
12. `site/pages/start-here-manual-validation-faq.html`
13. `site/pages/start-here-feedback-revision-worksheet.html`
14. `site/pages/start-here-system-contact-sheet.html`
15. `site/pages/start-here-bridge-contact-sheet.html`
16. `site/downloads/stackpilot-start-here-7-day-pack/printable-pack.html`
17. `site/downloads/stackpilot-start-here-7-day-pack/contact-sheet.html`

## Viewports

- Mobile narrow: 390 × 844
- Mobile short: 430 × 740
- Tablet: 768 × 1024
- Laptop: 1366 × 900
- Desktop: 1440 × 1000
- Print/PDF preview for `printable-pack.html`

## Pass/fail checks

### 1. Premium field-manual feel

- [ ] The page feels like a serious field manual or operator desk, not a generic AI SaaS page.
- [ ] No neon gradient soup, robot/sparkle gimmicks, fake dashboards, fake revenue screenshots, or passive-income language.
- [ ] Fraunces headings are readable and not wavy, cramped, or overlapping.
- [ ] Dark command sections transition cleanly into warm paper sections without cutting through text or CTAs.

### 2. Beginner route clarity

- [ ] A beginner can identify the next click in under 10 seconds.
- [ ] The route order is visible: buyer → offer → stack → agents → content → customers → delivery.
- [ ] Buttons do not compete equally when one primary action should win.
- [ ] Sample/fictional artifacts are clearly labeled as examples, not proof.

### 3. Mobile CTA and layout QA

- [ ] No horizontal scrolling at 390px wide.
- [ ] Hero headings do not cover buttons or metadata cards.
- [ ] Button rows wrap cleanly and remain tappable.
- [ ] Cards keep enough spacing for thumb scanning.
- [ ] Long URLs, filenames, and mono labels do not overflow.

### 4. Safety and launch gates

- [ ] Pages clearly say local/draft-only where launch risk exists.
- [ ] No forms, inputs, textareas, selects, live capture widgets, checkout, analytics setup, or outbound sending flows are connected.
- [ ] Human approval gates appear before publish, send, contact, buy, deploy, create accounts, accept terms, delete/change records, or use payment/tax/legal/KYC/private identity details.
- [ ] Feedback language is not treated as proof unless Tim approved it and the source is non-private.

### 5. Download/package QA

- [ ] ZIP link opens/downloads the current intended bundle.
- [ ] Printable pack reads well in browser print preview.
- [ ] Contact sheet lists every surface and important download.
- [ ] Manifest count matches actual ZIP entries.
- [ ] No nested ZIPs or `__MACOSX/` artifacts.

## Launch decision gates

- **WAIT:** use if any mobile, hierarchy, copy, fictional sample, package, or safety gate fails.
- **Manual first:** only after Tim approves exact audience, share script, and feedback log.
- **Free magnet:** requires approved capture/privacy/email provider setup before connection.
- **Paid path:** requires checkout, tax, terms, support/refund, listing, and customer-facing copy approval.

## Screenshot/contact-sheet workflow when browser tooling is available

1. Start the local static server from repo root:

```bash
python3 -m http.server 8777 --directory site
```

2. Capture the key pages at mobile and laptop widths using Playwright, browser devtools, or another screenshot tool.
3. Save screenshots under a dated local folder such as:

```text
business-ops/qa-screenshots/start-here-YYYY-MM-DD/
```

4. Create a contact sheet with one row per page: page name, mobile screenshot, desktop screenshot, pass/fail note, fix needed.
5. Do not publish screenshots publicly if they include unreleased copy, draft product files, private feedback, or Tim-only approval notes.

## Result log

```text
Date:
Reviewer:
Static verifier result:
ZIP entry count:
Browser tooling used:
Viewport failures:
Copy/hierarchy failures:
Safety-gate failures:
Fixes needed before launch:
GO / WAIT:
```