# Launch Copy Drafts

This folder holds the current launch-copy assets for the Kestrel open-source launch.

## Files

- `LANDING_PAGE_WIREFRAME.md` — full landing-page wireframe with section-by-section copy, proof points, CTA guidance, and implementation notes.
- `SIMPLE_LAUNCH_PAGE_ONE_SCREEN.md` — a tighter one-screen version for a minimal launch page.
- `PUBLISH_READY_LANDING_PAGE_COPY.md` — tightened publish-ready copy for a fuller public page.
- `LANDING_PAGE_HTML_STRUCTURE.md` — implementation-ready semantic HTML section structure for engineering.
- `PREVIEW_PACKET_LANGUAGE.md` — canonical preview-packet send language for the builder cohort and the lighter outside-the-bubble variant.

## Intended Use

- Start with `PUBLISH_READY_LANDING_PAGE_COPY.md` if the team wants final prose that can go straight into a launch page.
- Start with `LANDING_PAGE_HTML_STRUCTURE.md` if engineering needs a fast implementation map.
- Use `LANDING_PAGE_WIREFRAME.md` when revisiting section order, message flow, or page logic.
- Use `SIMPLE_LAUNCH_PAGE_ONE_SCREEN.md` if the team wants a fast, minimal page that can ship with low implementation overhead.
- Use `PREVIEW_PACKET_LANGUAGE.md` when the team needs the actual preview/send language rather than public landing-page copy.
- Treat these as launch-copy assets, not long-term product docs.

## Source Constraints

These drafts are aligned to the current launch framing already visible across:

- the canonical message stack in issue #603 comments
- the open-core boundary proposal in issue #612
- the preview-packet/send language in issue #188
- the current README opening in the repo

## Positioning Guardrails

- Keep `Sovereign AI` as the category frame.
- Do not let the page read like a feature release.
- Do not over-index on the product family; keep Kestrel as the foundation.
- Use the regional home healthcare partnership as proof of seriousness, not as the headline.
- Keep the first-screen message emotionally legible before it becomes technical.