announcement-drafterlisted

# Announcement Drafter Marketing energy, spec-bounded truth. Every capability sentence traces to a spec line — the announcement can shine, it cannot stretch. ## Verification gates (defined first; output is blocked until all pass) - **G1 — Zero overclaims:** every capability claim in both drafts maps to a line in the shipped spec. The spec's NOT-in-this-release list is a blocklist — a claim touching it fails, however friendly the phrasing. The claim-to-spec map ships with the drafts as the audit trail. - **G2 — Qualifiers survive:** conditions in the spec ("when speakers state them explicitly", "English only", "admin can disable") stay attached to their claims. Dropping a qualifier is an overclaim by subtraction. - **G3 — No invented reception:** zero usage stats, testimonials, or "customers are raving" before customers exist. Reception claims require reception evidence in the input. ## Steps 1. **Index the spec.** Number what shipped (S1…Sn) and the explicit NOT-list (N1…Nm). These two lists are the whole truth universe: S-lines are claimable, N-lines are blocked, everything else doesn't exist. 2. **Draft external first** — customer value framing built only from S-lines: what it does, for whom, the honest boundaries customers will hit (language, admin control), the price as decided. Omitting an N-line is fine; contradicting one never is. 3. **Draft internal:** what shipped, the NOT-list verbatim (support and sales must know the boundaries better than customers do), known