Publication approval

Public preview approval packet

A single approval surface for the next reputation-boundary step: turning the local Getaway Brief build into a public preview without skipping source checks, trust-page finalization, or affiliate-application gates.

Getaway Brief Public Preview Approval Packet

Status date: 2026-05-25

Current status: not approved for public deployment or affiliate signup.

Purpose: give the site owner a single low-friction approval surface for the next reputation-boundary step. This packet does not authorize publishing, affiliate applications, paid tools, credentials, or domain registration. It lists the exact decisions needed before the local static build can become a public preview suitable for affiliate-program review.

Current local state

Static site generated locally with 14 researched article drafts, 5 cluster hubs, trust pages, research/audit pages, sitemap, robots, and agent-readable files.
0 articles are marked publish_candidate or published.
0 live affiliate links are installed; CTA links remain #affiliate-placeholder until partner approval and exact-page checks.
Local build is tracking-free by default. Privacy-friendly analytics can be added later with Plausible or Umami only after the site owner approves provider, domain, and policy language.
Current research posture is strong enough for continued local development, but representative guide URLs still need exact-page verification before affiliate applications.

Decisions the site owner needs to make

Decision	Needed before	Safe default if no decision
Approve a public preview URL or domain	Any affiliate application or external review	Keep local-only
Approve contact method for `/contact.html`	Public preview and affiliate applications	Keep placeholder, do not publish
Approve final privacy wording	Public preview if analytics, cookies, forms, or affiliate links may appear	Keep local tracking-free placeholder
Approve disclosure/editorial wording	Public preview and affiliate applications	Keep current pre-launch draft language
Select 3-5 representative guides	First affiliate applications	Use the current shortlist, but do not submit externally
Approve exact-page verification pass	Promote any guide to `publish_candidate` or use it as an example URL	Keep all articles `researched`
Approve affiliate program signup order	Application submission under the site owner identity	Use handoff recommendation only as draft guidance

Minimum public-preview checklist

Before public deployment, complete and record all of the following:

Choose either a domain or a deploy-preview URL and document it in the handoff.
Replace /contact.html placeholder copy with a the site owner-approved email or contact-form destination.
Finalize /privacy.html for the chosen hosting, analytics, affiliate-link, cookie, and contact-form posture.
Re-run source health, claim-language audit, affiliate-safety audit, accessibility audit, static build, and validation.
Confirm local build still has no live affiliate links or Google Analytics markers.
Choose representative pages and complete the exact-page verification template for each page before using the URLs in applications.
Only after the site owner explicitly approves: deploy/publish the static files.

Recommended representative guides for the first verification batch

Use these only after the exact-page verification template is completed and archived:

weekend-trips-from-nyc-without-a-car — no-car hotel/tour intent.
where-to-stay-near-zion-without-a-car — national-park lodging/tour intent.
things-to-do-in-gatlinburg-when-it-rains — activity/ticket intent.
dog-friendly-weekend-trips-from-atlanta — pet-friendly lodging/rental intent.
warm-weekend-trips-from-chicago-in-march — flight/hotel/car-rental intent.

What not to do without explicit approval

Do not register or buy a domain.
Do not publish or deploy publicly.
Do not submit affiliate applications.
Do not use the site owner credentials or private accounts.
Do not add live partner links, partner IDs, tracking IDs, price claims, or savings guarantees.
Do not enable GA4/Google Analytics; keep Plausible/Umami as the only default analytics candidates.

Exact next action after approval

If the site owner approves a public-preview path, the agent should:

Update contact/privacy/disclosure copy using the approved details.
Run python3 scripts/audit_source_health.py, python3 scripts/audit_claim_language.py, python3 scripts/audit_affiliate_safety.py, python3 scripts/audit_accessibility.py, python3 scripts/build_site.py, and python3 scripts/validate_site.py.
Prepare a final local deployment bundle report with the chosen URL/domain, representative pages, audit outputs, and remaining manual verification notes.

Until those approvals happen, Getaway Brief remains a local pre-launch affiliate-readiness build.