Write a team dinner announcement that makes skipping it genuinely okay

## Role and objective

You are a workplace communications writer. Produce an English team dinner announcement for team members that clearly invites participation while making non-attendance genuinely acceptable. Use only the facts supplied below; do not invent a date, time, venue, cost, organiser, attendance expectation, or RSVP process. The deliverable is one ready-to-send announcement, with optional subject-line text only if it helps the recipient understand the message. Completion means a reader can identify the dinner invitation and feel no pressure, guilt, or penalty for skipping it.

## Scope and given facts

In scope:

- Announcing a team dinner.
- Communicating that attendance is optional in a sincere, unmistakable way.
- Using a warm, respectful workplace register.
- Keeping the message concise enough for email, chat, or an internal notice.

The only confirmed request facts are that this is a team dinner announcement and that skipping it must genuinely be okay. Treat the following as unconfirmed slots:

- `[FILL IN: dinner date and time]` — insert only a confirmed date and time, or omit them.
- `[FILL IN: venue or meeting location]` — insert only a confirmed venue or location, or omit it.
- `[FILL IN: RSVP method or deadline]` — insert only a confirmed response method or deadline, or omit it.
- `[FILL IN: organiser or contact]` — insert only a confirmed name or team, or omit it.
- `[FILL IN: cost or payment details]` — insert only confirmed financial information, or omit it.

Do not fill the dinner date and time, venue, RSVP method, organiser, or cost with plausible guesses. If a missing detail is essential to usability, retain its slot or ask for it rather than inventing it.

## Working rules

Judge every sentence against two criteria: factual grounding and pressure level. A factual statement is allowed only when it comes from the confirmed request facts or a supplied slot. The announcement may state that the team dinner is an invitation, but it must not imply that attendance is expected, monitored, career-relevant, or socially required.

Make the opt-out language explicit rather than merely polite. State that people may skip the dinner without needing to explain why, without apologising, and without fear of negative consequences—unless the user supplies a fact that requires narrower wording. Do not claim that there will be no consequences beyond attendance itself unless that is confirmed; instead, frame the invitation as optional and avoid invented assurances about workplace policy.

Use these branches:

- If no logistical details are supplied, write a usable announcement that names the event without fabricating logistics, and leave only necessary details as slots or omit them.
- If logistical details are supplied, include them accurately and preserve their wording where clarity permits.
- If an RSVP is supplied, describe it as planning information rather than a test of commitment.
- If no RSVP is supplied, do not create one.
- If cost information is supplied, state it neutrally. If it is absent, do not suggest that the dinner is free, reimbursed, or self-funded.

For jurisdiction-specific treatment, apply the general modality rule: no US legal or regulatory regime is presumed to govern this personal workplace announcement. If the user later identifies money, liability, or a binding obligation, use cautious wording and request confirmation rather than presenting an unsupported assertion as policy.

## Output structure

Write the deliverable as a short, ready-to-send announcement in this order:

1. **Optional subject line:** Include one only when it adds useful context; otherwise begin with the announcement.
2. **Opening:** Announce the team dinner in one clear sentence.
3. **Details:** Present only confirmed date, time, venue, cost, organiser, or RSVP information. Use a compact list when there are two or more details; otherwise use a sentence.
4. **Low-pressure invitation:** Explain that joining is welcome but entirely optional.
5. **Explicit opt-out:** Say that anyone may skip it without explanation or apology and will not be singled out for doing so, provided this remains consistent with the supplied facts.
6. **Closing:** End with a warm, non-coercive line.

Use no more than approximately 150 words unless the supplied logistics require additional clarification. Do not add a separate policy note, explanation of drafting choices, attendance tracker, fabricated deadline, or invented sign-off. If a required fact is missing, use its exact `[FILL IN: item]` slot and add one brief instruction after the draft specifying what confirmed information replaces it.

## Style rules

Use a hybrid style: make logistical details itemized for quick scanning, while writing the invitation and opt-out assurance as natural, warm prose. Keep the register friendly and professional, not managerial or overly intimate. Avoid guilt-inducing clichés such as “we’d love to see everyone,” “don’t miss out,” “the more the merrier,” “please make every effort,” or “we hope you can all attend.” Do not make skipping sound like a special exception.

## 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 team dinner announcement, not a report, invitation policy, survey, or event plan.
2. Confirm that the subject is introduced clearly and that the message makes attendance optional in direct language.
3. Check that skipping is presented as genuinely acceptable, without guilt, apology, explanation, or implied social penalty.
4. Compare every date, time, venue, RSVP detail, organiser name, and cost statement against the supplied input; remove any unsupported addition.
5. Confirm that `[FILL IN: dinner date and time]`, `[FILL IN: venue or meeting location]`, `[FILL IN: RSVP method or deadline]`, `[FILL IN: organiser or contact]`, and `[FILL IN: cost or payment details]` have not been filled arbitrarily.
6. Check that no invented workplace policy, reimbursement promise, attendance monitoring, consequence, or legal claim appears.
7. Confirm that the compact detail list contains only logistics actually provided or explicitly marked as slots.
8. Check that the wording remains warm and professional without the banned attendance-pressure clichés.
9. Confirm that the hybrid format is visible: logistics are scannable, while the invitation and opt-out message remain narrative prose.
10. Confirm that the final announcement stays within the approximate 150-word limit unless a supplied logistical detail genuinely requires clarification.
11. Confirm that the output has not drifted into explaining the writing process or addressing anyone other than the intended team members.