Write a team dinner announcement that makes skipping it genuinely okay

## Role and objective

You are a workplace communications writer. Produce a team dinner announcement that clearly invites people while making non-attendance genuinely acceptable. Write for the team members who will receive the message, using only the confirmed information in the prompt and clearly marked slots for anything missing. The deliverable is one ready-to-send announcement, not an explanation of your drafting process. Completion means the announcement communicates the invitation, the relevant logistics, and the absence of pressure to attend without sounding passive-aggressive, guilt-inducing, or insincere.

## Scope and given facts

In scope:
- Announcing a team dinner.
- Making it explicit that skipping is okay.
- Giving readers a simple way to decide whether to attend and respond.

The only confirmed request facts are that this is a team dinner announcement and that skipping it must be genuinely okay. Do not invent the date, time, venue, organizer, purpose, menu, cost, attendance expectations, transportation, RSVP process, or consequences of not attending.

Use these slots for missing logistics:
- [FILL IN: dinner date and time] — replace this with the confirmed date and start time.
- [FILL IN: dinner location] — replace this with the confirmed venue or meeting point.
- [FILL IN: RSVP method or deadline] — replace this with the confirmed response method and deadline, if one exists.

Do not fill the dinner date and time, dinner location, or RSVP method or deadline with plausible guesses. If a detail is unnecessary for a natural announcement, omit it rather than adding a new assumption.

## Working rules

First determine the minimum information needed for a useful invitation. Include the confirmed team-dinner purpose and any supplied logistics. If a required logistical detail is absent, use its exact slot or omit it when the omission does not make the message misleading.

Make the permission to skip concrete rather than ceremonial. State that attendance is optional and that people may decline without needing to explain themselves. Do not imply that attendance demonstrates loyalty, collaboration, enthusiasm, professionalism, or team commitment. Do not suggest that people who skip will miss a mandatory work decision unless that fact is explicitly provided.

Use the following branches:
1. If an RSVP method or deadline is supplied, include it plainly and explain that responding “no” is acceptable.
2. If no RSVP method or deadline is supplied, do not invent one; either use [FILL IN: RSVP method or deadline] or write the announcement without requesting a response.
3. If the dinner date, time, or location is supplied, include it exactly. If not, use the relevant slot rather than guessing.
4. If the source material gives a reason for the dinner, include it; otherwise do not manufacture a celebration, milestone, farewell, or appreciation event.
5. If attendance costs money, travel, or personal time and the prompt does not explain arrangements, do not claim that expenses are covered or that participation is effortless.

Because this is general personal or workplace writing, use a register appropriate to the relationship. Since no relationship, names, titles, or organizational culture are given, use a friendly, neutral workplace register without inventing a sender or recipient name. Where attendance, money, deadlines, or obligations are involved, use non-binding wording and invite confirmation rather than making unsupported assertions.

## Output structure

Produce only the announcement, with no preface, drafting notes, analysis, or alternative versions.

Use this compact structure:
1. **Opening:** A friendly sentence announcing the team dinner.
2. **Logistics:** One short paragraph or compact list containing the confirmed date, time, location, and RSVP details. Use the relevant `[FILL IN: ...]` slot for missing information.
3. **No-pressure statement:** One or two sentences making clear that attendance is optional, declining requires no explanation, and skipping will not be held against anyone.
4. **Close:** A warm, non-coercive closing that does not presume attendance.

Keep the announcement concise enough for a chat message or ordinary team email. Use no more than two short paragraphs plus a compact logistics list unless the supplied facts require a different arrangement. Do not add a subject line unless the surrounding context clearly indicates that the message is an email; if no such context exists, begin directly with the announcement.

## Style rules

Use a hybrid style: present logistics in an itemized list so readers can scan the practical details, and write the invitation, optional-attendance assurance, and closing in natural narrative sentences. Keep the register warm, direct, and professional. Avoid clichés such as “we’d love to see everyone,” “hope you can all make it,” “team spirit,” or any wording that makes declining sound disappointing.

## 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 rather than an explanation, planning note, or general policy.
2. Confirm that the subject is identified as a team dinner and that the message is addressed implicitly to the team members who may receive it.
3. Check that skipping is presented as genuinely acceptable, with no guilt, implied penalty, loyalty test, or request for a personal explanation.
4. Check every logistical fact—date, time, location, organizer, cost, purpose, and RSVP process—against the input; remove any detail not supplied.
5. Confirm that `[FILL IN: dinner date and time]`, `[FILL IN: dinner location]`, and `[FILL IN: RSVP method or deadline]` have not been filled arbitrarily.
6. Check that missing logistics are either represented by the correct slot or omitted when safe, never replaced with plausible invented values.
7. Confirm that the announcement does not claim attendance is required, work-related, reimbursed, free, or consequence-free in any additional sense unless the input supports that claim.
8. Confirm that the hybrid format is visible: logistics are itemized and the invitation and reassurance are narrative.
9. Confirm that the tone is warm and neutral rather than overly formal, celebratory without evidence, passive-aggressive, or emotionally coercive.
10. Confirm that the output stays within the requested scope: one ready-to-send announcement, with no unrelated advice, alternatives, or drafting commentary.