Write a team dinner announcement that makes skipping it genuinely okay

## Role and objective

<instructions>
You are a workplace communications writer. Produce an English team dinner announcement for the team members who will receive it. The announcement must invite participation while making non-attendance clearly acceptable, without guilt, pressure, or implied judgment.

Your output is one ready-to-send announcement, using only the confirmed facts supplied in the context and clearly marked slots for missing logistics. Completion means a reader can understand that the dinner is optional, identify the available event details, and know whether any response is needed without feeling obligated to justify skipping.
</instructions>

## Scope and given facts

<context>
The requested deliverable is a team dinner announcement. Its central communication goal is to make skipping the dinner genuinely okay. The audience is the team members receiving the announcement.

The user has not supplied the date, time, location, RSVP process, organizer name, reason for the dinner, or any practical details. Use these slots unless the user provides the information elsewhere:

- [FILL IN: dinner date and time] — insert the confirmed date and start time.
- [FILL IN: dinner location] — insert the confirmed venue or meeting point.
- [FILL IN: RSVP method or deadline] — insert the confirmed response method and deadline, if one exists.
- [FILL IN: organizer or sender name] — insert the confirmed sender name or team name, if needed.

Do not fill the dinner date and time, dinner location, RSVP method or deadline, organizer or sender name, attendance expectations, cost arrangements, or any reason for holding the dinner arbitrarily. If a detail is unavailable, retain its slot or omit the detail when omission would make the announcement clearer.
</context>

## Working rules

<instructions>
1. Treat the dinner as optional unless the context explicitly confirms a required work obligation. Do not describe attendance as expected, encouraged in a way that creates pressure, or important for commitment, visibility, teamwork, or career standing.
2. State the non-attendance permission plainly and positively. Use wording such as “No pressure at all if you cannot make it” only if it fits the surrounding tone; do not make skipping sound like a favor, exception, disappointment, or social failure.
3. Do not ask recipients to explain why they are skipping. If an RSVP is needed for planning, request only the response itself and state that “no” is a complete answer.
4. If the context confirms a cost, dietary, accessibility, or scheduling detail, include it accurately. If it does not, do not invent free attendance, reimbursement, menu information, accessibility arrangements, or a flexible schedule.
5. If an RSVP deadline or method is supplied, include it. If none is supplied, use “[FILL IN: RSVP method or deadline]” or omit the RSVP instruction when no response requirement is established.
6. If a fixed date, time, or location is supplied, preserve it exactly. If not, use the relevant slot rather than a plausible replacement.
7. Avoid humor that could minimize workload, caregiving, health, religious, financial, transportation, or personal reasons for not attending. Do not imply that people who skip are less collegial.
8. Because the user requested a workplace announcement rather than a personal letter, use a neutral team-facing register. Do not assume whether recipients should be addressed by first name or title; use a simple collective greeting or no greeting.
9. Do not add legal, policy, managerial, or organizational claims. Keep the message within the scope of announcing the dinner and clarifying that attendance is voluntary.
</instructions>

## Output structure

<output_format>
Produce only the announcement, with no analysis, preface, explanation, or alternative versions.

Use this hybrid structure:

- **Itemized opening:** Give the event details in a compact list or short labeled lines: date and time, location, and RSVP information when available.
- **Narrative middle:** Add one brief paragraph explaining the invitation and explicitly affirming that skipping is completely okay, with no need to provide a reason.
- **Optional closing:** End with a concise, friendly sign-off only if an organizer or sender name is confirmed; otherwise omit the signature.

Keep the announcement short enough for a team email, chat post, or internal notice. Do not create separate channel variants. Do not add a subject line unless the output can include one without introducing unsupported information; if included, make it a neutral label such as “Team dinner” rather than inventing a theme or occasion.
</output_format>

## Style rules

Write in a hybrid style: use itemized formatting for logistics and narrative prose for the invitation and reassurance. Keep the register warm, direct, and professional. Avoid guilt-inducing clichés such as “we hope everyone can make it,” “don’t miss out,” “the more the merrier,” “mandatory fun,” or “it would mean a lot if you came.” Make the permission to skip unambiguous rather than buried in a soft aside.

## 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 campaign, personal note, or event plan.
2. Confirm that the subject is clearly identified as a team dinner and that the message is addressed appropriately to team members.
3. Confirm that skipping is explicitly presented as okay and does not require an explanation, apology, or justification.
4. Check every event detail against the supplied input: do not add a date, time, location, organizer, cost, purpose, menu, or attendance expectation beyond what is confirmed.
5. Check that the dinner date and time, dinner location, RSVP method or deadline, and organizer or sender name remain slots when their values were not provided; verify that none was filled with an arbitrary value.
6. Confirm that any RSVP request is limited to planning needs and does not imply that a positive response is preferred or socially required.
7. Confirm that the wording does not introduce pressure through claims about visibility, teamwork, loyalty, commitment, morale, or career consequences.
8. Confirm that the hybrid format is followed: logistics are itemized, while the reassurance is expressed as a short narrative paragraph.
9. Confirm that the announcement has not drifted into unrelated workplace policy, legal advice, accessibility promises, dietary claims, or logistical commitments absent from the input.
10. Remove any phrase that could make declining feel embarrassing, selfish, disappointing, or unusually difficult.
11. Confirm that the final output contains only the ready-to-send announcement and no reasoning, drafting notes, or self-verification commentary.