# StackPilot Start Here — Download Manifest

Status: local ZIP QA manifest. This file is part of the draft download bundle and should stay review-only until Tim approves a launch path.

## Intended ZIP contents

The public download archive `site/downloads/stackpilot-start-here-7-day-worksheet-pack.zip` should contain exactly these local files:

1. `01-buyer-map.md`
2. `02-offer-one-liner.md`
3. `03-smallest-stack-map.md`
4. `04-agent-job-card.md`
5. `05-proof-content-route.md`
6. `06-customer-tracker.md`
7. `07-delivery-checklist.md`
8. `approval-gates.md`
9. `README.md`
10. `contact-sheet.html`
11. `launch-readiness-checklist.md`
12. `launch-approval-card.md`
13. `manual-validation-feedback-log.md`
14. `manual-validation-response-synthesis.md`
15. `manual-validation-decision-review.md`
16. `manual-validation-message-review.md`
17. `manual-validation-path-a-packet.md`
18. `offer-readiness-comparison.md`
19. `day-01-buyer-map-clarity.md`
20. `proof-safety-companion.md`
21. `faq-objection-desk.md`
22. `lead-magnet-readiness-draft.md`
23. `paid-product-readiness-draft.md`
24. `product-shelf-decision-map.md`
25. `printable-pack.html`
26. `sample-filled-artifacts.md`
27. `download-manifest.md`

## ZIP guardrails

- The archive must not contain another `.zip` file.
- The archive must not contain `__MACOSX/` artifacts.
- The archive must keep fictional samples clearly labeled as fictional teaching examples, not proof, case studies, testimonials, customer data, or revenue claims.
- The manual-validation feedback log must remain a blank template until Tim personally approves a manual share test and records responses. Hermes may summarize supplied feedback later, but may not contact people or collect it independently.
- The manual-validation message review and Path A packet must remain draft-only: Hermes may prepare share scripts and stop-rule sheets, but Tim chooses the audience, edits final wording, approves the visible asset, and manually sends only if he approves.
- The manual-validation response synthesis and decision review must use Tim-supplied feedback only and choose the most conservative next decision before any lead magnet, checkout, analytics, or public launch system is connected.
- The offer-readiness comparison must remain no-form and must use real Tim-supplied feedback before recommending manual share again, free lead magnet, paid product, improve, or wait.
- The Day 01 buyer-map clarity sheet must remain no-form and must improve only local buyer/pain wording; it must not publish, send, validate, scrape, capture, or create proof claims.
- The proof-safety companion must remain no-form and must label claims honestly; it must not fabricate proof, testimonials, screenshots, revenue, validation, customer names, logos, or permission.
- The FAQ/objection desk must remain no-form and must route beginner confusion to local worksheets, proof labels, offer-readiness review, or Tim approval before any capture, checkout, analytics, deployment, outreach, account, terms, payment, or public-proof system is opened.
- The lead-magnet readiness draft must remain no-capture and must not connect email provider, analytics, deployment, public download gates, account creation, terms, outreach, checkout, payment, KYC/tax/legal/identity data, or customer data.
- The paid-product readiness draft must remain no-checkout and must not connect payment platforms, listings, carts, analytics, deployment, account creation, terms, KYC/tax/legal/identity data, customer data, support inboxes, public delivery, fake proof, or outreach.
- The product-shelf decision map must remain navigation-only and must not authorize email capture, checkout, analytics, deployment, outreach, accounts, terms, payments, KYC/tax/legal/identity fields, support systems, or public proof claims.
- The archive remains local/draft-only: no checkout, email capture, analytics, deployment, account creation, terms acceptance, outreach, payment, or public delivery flow is connected.

## Regeneration note

Regenerate from `site/downloads/stackpilot-start-here-7-day-pack/` while excluding any existing `.zip` files so old archives cannot accidentally nest inside the new archive.