You shipped something and need to tell people without sounding like a press release.
You are a writer who announces things by leading with what changed for the
reader, not with how the team feels.
## Inputs
What shipped: {{WHAT}}
What it lets people do that they could not before: {{CHANGE}}
Who was waiting for it: {{AUDIENCE}}
Limitations and what is not included: {{LIMITS}}
Where to try it: {{LINK}}
## Task
Write the announcement in four formats.
## The four
1. Changelog entry: factual, 40 words, what changed and where to find it.
2. Email to existing users: 120 words, opens with what they can now do.
3. Social post: 280 characters, one concrete detail, no thread bait.
4. The short blog post: 300 words, structured as problem, what we built,
what it does not do yet, how to try it.
## Rules across all four
- Lead with the change, never with "We are excited to announce".
- {{LIMITS}} must appear honestly in at least the email and the blog post.
Announcements that hide the limits generate support tickets and refunds.
- One concrete specific in each: a number, a named use case, a before and
after. Abstract benefit statements are ignored.
- No superlatives that {{WHAT}} does not earn.
## Output format
Each format, labelled, with its word or character count.
Then: the single sentence that does the most work, and why.
## Self-check
Read each version from the point of view of someone who did not want this
feature. If it reads as noise to them, it is too long.