Publish compliance content and inspect protected delivery

Story

Send published compliance content, inspect provider outcomes and withhold subsequent mail to permanently bounced addresses.

The workflow moves from missing content through publication, acceptance, ordinary provider submission and feedback. Withholding is a recorded outcome, and completed-message redelivery differs from recovery of an ambiguous submission.

Verification Boundary

The structured steps and assertions carry their own provenance and sources. Test references describe inspected assertions at the pinned commits; this examination does not claim a fresh provider or browser execution.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Goal: Send published compliance content, inspect provider outcomes and withhold subsequent mail to permanently bounced addresses.
Intent sources: services-platform:docs/communications/architecture.md#2026-10-09 — Final acceptance

Steps

#	Surface	Action	Capability	Expected	Provenance
1	`requestCommunication`	CRM submits compliance mail for an organization type without published content.	`CAP-PFM-NOT-017`	The receipt acknowledges submission, while processing records configuration blockage and sends no mail.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#stores configuration_blocked behind the queue, naming the purpose and the record that owns no template
2	`saveOwnedTemplate`	The administrator saves content containing an undeclared variable and then fixes it.	`CAP-PFM-NOT-016`	The invalid save reports content problems; the corrected save publishes version one.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#publishes the corrected content as version 1
3	`renderPreview`	The administrator previews the published notice using sample records.	`CAP-PFM-NOT-016`	Preview matches rendering by the delivery renderer.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#previews the published version with the purpose’s sample data through the delivery renderer
4	`requestCommunication`	CRM submits to one eligible contact, one suppressed contact and one environment-disallowed contact.	`CAP-PFM-NOT-017`	Processing pins version one, queues one message and withholds the other two with their respective reasons.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#queues the deliverable contact, withholds the suppressed one and the one this environment may not e-mail
5	`platform_communications_send`	Dispatch and the sending consumer process the accepted request.	`CAP-PFM-NOT-018`	The queued message is submitted with provider correlation tags in the normal lifecycle.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#hands the provider exactly one message, the queued contact’s
6	`platform_communications_feedback`	The provider sends delivery, open and click feedback, including a repeated report.	`CAP-PFM-NOT-019`	New events are recorded once; an image-proxy open does not increase likely-human counts.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#records each new event and recognizes the repeated delivery as a duplicate
7	`platform_communications_feedback`	A different contact's message bounces permanently, and CRM submits a subsequent notice to that address.	`CAP-PFM-NOT-020`	Bounce protection suppresses the address and withholds the subsequent message.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#stores the next notice to that address suppressed, with the reason, and sends nothing
8	`listCommunicationMessages`	Staff inspect workspace communication history.	`CAP-PFM-NOT-019`	Source-record messages list in descending time order with their separate states, excluding other workspaces.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#lists every message about the organization, newest first, with its own states

Alternate and Failure Paths

Path	From step	Condition	Path taken	Outcome	Provenance
alternate	4	CRM supplies values outside the purpose data contract.	Queued acceptance records field-specific invalidity.	No mail sends, and staff can inspect the validation reason.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#stores it invalid where staff can read it, naming the paths
failure	5	The same request is consumed after all its messages have settled.	Processing recognizes the final message states.	No completed message is submitted again.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#never sends again when the run is repeated

Assertions

Id	Statement	Provenance
`01`	The Platform-rendered purpose sends no mail until its owning record has published a template.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#sends nothing at all
`02`	Reprocessing the completed lifecycle makes no additional provider send.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#never sends again when the run is repeated
`03`	A permanent bounce withholds the next message to that address before provider submission.	test services-platform:modules/communications/tests/integration/lifecycle/contact-role-compliance-communication.integration.spec.js#stores the next notice to that address suppressed, with the reason, and sends nothing

End-to-end policy: optional: The allowed console paths establish no communication interface for this lifecycle. The integration suite covers content, queued delivery and feedback; owning-module screens require their own browser examination.

Planning

Publish compliance content and inspect protected delivery ​

Story ​

Verification Boundary ​