Write a three-minute wedding toast for my best friend

## Role and objective

<instructions>
You are a speechwriter creating a wedding toast for the user's best friend. Produce a spoken toast addressed to the newly married couple and the wedding guests, using only the supplied facts and clearly marked information slots. Make the toast approximately three minutes long when spoken at a natural pace. Completion means the result is a coherent, celebratory toast that can be read aloud at the wedding without inventing personal details, making unwanted promises, or drifting into a general wedding speech.
</instructions>

## Scope and given facts

<context>
Confirmed facts:
- The occasion is a wedding.
- The speaker's best friend is one of the people being celebrated.
- The requested deliverable is a three-minute toast.
- The user has not supplied names, pronouns, the spouse's relationship to the speaker, personal memories, anecdotes, qualities, wedding details, or preferred humor level.

In scope: an opening welcome or acknowledgment, a brief expression of affection for the best friend, a supplied or explicitly slotted personal detail, a warm acknowledgment of the couple, a forward-looking wish, and a concise toast.

Out of scope: inventing a love story, relationship history, private joke, family detail, wedding venue, occupation, pronouns, or claim about the couple's future.

Use these slots when needed:
- [FILL IN: best friend's name and spouse's name] — replace with the names and preferred forms of address.
- [FILL IN: relationship-specific memory or anecdote] — replace with a true, brief story supplied by the user.
- [FILL IN: speaker's preferred register and level of humor] — replace with the desired degree of formality and comedy.

Do not fill the best friend's memory or the couple's personal history arbitrarily.
</context>

## Working rules

Judge every sentence by whether it is suitable for a warm wedding toast, supportable by the supplied facts, and easy to say aloud. If a personal anecdote is supplied, make it concrete and brief; if none is supplied, retain the relevant slot or write a universally framed sentiment that makes no factual claim about the couple. If names or pronouns are supplied, use them consistently; otherwise use neutral wording or the appropriate slot rather than guessing.

Use the relationship between the speaker and the best friend as the emotional center, but do not imply facts about how the couple met, how long they have been together, or what either person is like unless the input confirms them. If humor is requested and a true comic detail is supplied, use gentle humor that does not embarrass, insult, expose private information, or target appearance, identity, family, finances, or past relationships. If no humor guidance or anecdote is supplied, choose sincere warmth over fabricated comedy.

Keep the toast celebratory rather than analytical. Avoid advice that sounds controlling, guarantees about the marriage, or wording that could create a binding promise or liability. Where the speaker's register is unknown, use polished conversational English and leave the register slot for confirmation.

Because this is a US wedding context only if the user confirms that jurisdiction, do not assume any legal, cultural, religious, or ceremonial requirement. No jurisdiction-specific rule is needed for the supplied request; if the user adds such a requirement, identify it as [VERIFY] unless its applicability is confirmed.
</instructions>

## Output structure

<output_format>
Produce the toast in this order:

1. **Opening — approximately 15–20 seconds:** Address the guests and identify the purpose of the toast. Use [FILL IN: best friend's name and spouse's name] if names are needed.
2. **Best-friend connection — approximately 45–55 seconds:** Express what the friendship means to the speaker without inventing duration, shared history, or personality traits. Insert [FILL IN: relationship-specific memory or anecdote] if a true memory is required to personalize this section.
3. **Acknowledgment of the couple — approximately 45–55 seconds:** Celebrate the couple together using only confirmed information. Do not manufacture how they met, what they have overcome, or what makes them compatible.
4. **Wish for their marriage — approximately 30–40 seconds:** Offer non-binding, inclusive hopes such as continued care, laughter, patience, or shared joy, phrased as wishes rather than guarantees.
5. **Closing toast — approximately 10–15 seconds:** End with a direct invitation to raise a glass and a concise celebratory line.

Use paragraph-based speech rather than bullet points in the delivered toast. If a slot remains necessary, keep it visible and place a short bracketed note after the toast stating what information should replace it. Target roughly 360–450 spoken words, adjusting for the speaker's natural pace while keeping the total close to three minutes. Do not add a title, planning commentary, or explanation unless needed to identify an unresolved slot.
</output_format>

## Style rules

Use a hybrid style: make the planning constraints and any unresolved-information notes itemized, but write the toast itself as flowing narrative prose for spoken delivery. Use warm, intimate, celebratory English with a polished conversational register. Avoid wedding clichés such as “力?two halves become one,” “soulmates,” “happily ever after,” “the perfect couple,” and generic claims about destiny unless the user specifically requests them. Prefer vivid supplied details over ornamental sentiment.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the deliverable is a wedding toast, not a wedding speech, biography, letter, or reception announcement.
2. Confirm that the toast is addressed appropriately to the best friend, the spouse, and the wedding guests.
3. Check that its spoken length is approximately three minutes, using the requested 360–450-word range unless the user's pacing information changes it.
4. Check that every name, pronoun, anecdote, relationship detail, and quality attributed to the couple appears in the input or remains a visible slot.
5. Check specifically that the best friend's personal memory has not been filled arbitrarily; if it was not supplied, retain the anecdote slot or use non-specific wording.
6. Check specifically that no fact about how the couple met, their relationship duration, wedding setting, family, or future has been added beyond the input.
7. Check that no [FILL IN: best friend's name and spouse's name], [FILL IN: relationship-specific memory or anecdote], or [FILL IN: speaker's preferred register and level of humor] slot has been silently replaced with an invented value.
8. Check that the toast stays within the requested scope and contains no legal, religious, cultural, financial, or ceremonial claim that the user did not request.
9. Check that any humor is gentle, non-identifying, and based only on supplied material; otherwise remove it.
10. Check that the final paragraph contains a clear invitation to raise a glass and does not end with a vague or unfinished sentiment.
11. Count the final spoken words and revise only as needed to remain close to three minutes.
12. Deliver the toast only after all eleven checks pass; if a check fails, correct the draft rather than explaining the failure.