Before activating a welcome automation, make it pass this release gate

Release record header: identify exactly what can send

Record the automation ID and version, signup path and copy version, triggering event, audience rule, sender name and domain, reply address, provider, message count, maximum duration, owner, approver, rollback version, test identities, and scheduled activation. Attach the resource or offer that created the expectation. PASS means another operator can locate and stop the exact workflow. REVIEW means a noncritical label or ownership detail has a dated correction. STOP means the audience, trigger, sender, or rollback cannot be identified. This header prevents a review of attractive screenshots from substituting for control of the live system. It also makes later incidents traceable to the configuration that actually sent mail.

Evidence: Google Gmail Help; Yahoo

Continuity gate: signup language survives the first inbox view

Compare advertisement, landing page, form, button, confirmation, From name, subject, first screen of the email, and promised asset. PASS requires the same sender, task, scope, and realistic cadence across these surfaces. REVIEW covers a minor wording inconsistency that cannot change the choice and has an owner. STOP covers an unrelated promotion, hidden recurring mail, unfamiliar identity, unavailable resource, or a form that cannot reproduce what the subscriber saw. Keep evidence from both desktop and mobile and include a text-only rendering. The recipient should understand why the message arrived without searching a policy or remembering a corporate name that never appeared during signup.

Evidence: Federal Trade Commission; Messaging, Malware and Mobile Anti-Abuse Working Group

Purpose-and-schedule gate: every row earns its send

List each message with trigger, delay, reader question, useful payload, primary action, dependencies, branch condition, and terminal state. PASS means each email fulfils a distinct part of the disclosed job and the complete series ends or offers a separate continuation choice. REVIEW covers redundant material that can be removed before the next enrollment window without misleading current recipients. STOP covers deceptive urgency, a subject unrelated to content, assumed behavior, an unbounded series, or a sales detour presented as required instruction. Verify time zones, delay units, weekend behavior, re-entry, duplicates, and what happens when events arrive out of order. A diagram is evidence only after those states are tested.

Evidence: Yahoo; Federal Trade Commission

Sender-and-render gate: inspect the received artifact

Send through production-like infrastructure to accounts at multiple providers. Inspect SPF, DKIM, DMARC alignment as applicable, headers, visible From and reply handling, HTML and plain text, contrast, keyboard and screen-reader cues, image alternatives, link destinations, tracking parameters, file access, and provider responses. PASS requires a recognizable, functional message with no unresolved authentication or access defect. REVIEW allows a cosmetic problem that does not obscure content, identity, choice, or exit. STOP applies to failed authentication, misleading routing, broken assets, unsafe redirects, inaccessible essential controls, or unexplained provider blocks. Gmail and Yahoo guidance is provider-specific; a passing sample does not guarantee placement.

Evidence: Google Gmail Help; Yahoo

Exit gate: prove suppression while messages are queued

Enroll a test identity, then unsubscribe or change preference between scheduled messages. Verify the visible control, destination page, confirmation, provider synchronization, suppression list, branch cancellation, re-import protection, and any correctly classified transactional exception. PASS means promotional mail stops under the documented rule and no queued job bypasses the decision. REVIEW covers a monitored delay inside an applicable requirement with evidence and an owner. STOP covers login, fees, extra data demands, dead links, confusing choices, or continued marketing after opt-out. FTC, Gmail, Yahoo, and M3AAWG sources address different duties and practices; use local legal review for the subscriber's jurisdictions. Never use a real subscriber as the test subject.

Evidence: Google Gmail Help; Federal Trade Commission

Ruling: activate only with zero STOP findings

The next action is to run this release record on one dormant welcome workflow before enabling enrollment. Every REVIEW item needs a reason, owner, due date, and proof that it does not undermine permission, identity, delivery, or exit. Preserve the prior version and define the kill switch. Monitor delivery errors, complaints, unsubscribes, replies, and support reports separately after activation. Limits remain: a controlled test cannot predict all mailbox decisions, a technical pass cannot prove reader interest, and this record is not global legal advice. Re-run it after any change to signup copy, resource, sender, provider, domain, authentication, cadence, branch signal, data use, or monetization. Release is an evidence decision, not a final glance at the automation canvas.