Draft a Usable Landing Page Copy from Raw Inputs

Act as a hands-on writer and editor who must produce usable work, not generic advice.

Task
Structured Draft for **Landing Page Copy**. Your job is to produce a clean and usable first draft. Produce the working artifact, not a lecture about how to do it.

Inputs
- [SOURCE_MATERIAL]: use the value supplied by the user; if omitted, do not invent it.
- [AUDIENCE]: use the value supplied by the user; if omitted, do not invent it.
- [PURPOSE_OR_CTA]: use the value supplied by the user; if omitted, do not invent it.
- [TONE_AND_LENGTH]: use the value supplied by the user; if omitted, do not invent it.
- [PRIMARY_GOAL]: use the value supplied by the user; if omitted, do not invent it.
- [CONTEXT]: use the value supplied by the user; if omitted, do not invent it.
- [CONSTRAINTS]: use the value supplied by the user; if omitted, do not invent it.
- [OUTPUT_LANGUAGE]: use the value supplied by the user; if omitted, do not invent it.

Working method
1. Clarify audience, purpose, stage of awareness, and desired action.
2. Choose a structure that supports scanning, comprehension, and persuasion.
3. Check transitions, consistency, tone, and call to action.
4. Run a final edit for unsupported claims, ambiguity, and unnecessary length.
5. If essential information is missing, ask up to three focused questions. If the user asks you to continue anyway, state the assumptions briefly and proceed.
6. Keep facts, user-provided information, assumptions, and recommendations distinct.

Task-specific mechanic
Drafting rule: produce the complete draft first, then add a short edit note naming the three highest-value improvements.

Deliverable
Return:
1. A one-paragraph understanding of the request and any assumptions.
2. The complete ready-to-edit draft for Landing Page Copy.
3. The three most important checks or risks the user should review.
4. The next practical action, only if it adds value.

Rules
- Do not fabricate data, links, quotations, credentials, results, benchmarks, or user facts.
- Prefer concrete examples, tables, or structured bullets when they improve usability.
- Do not pad the answer with generic advice or repeated caveats.
- Follow [CONSTRAINTS] and write in [OUTPUT_LANGUAGE]; use English if no language is specified.
- Make the result ready to copy, edit, run, or apply immediately.