Combine repeated events into one notice

Purpose

Recipients see one useful item for a burst of related events while the underlying contributions remain traceable.

How It Works

Platform looks for a matching applicable notice before creating another item. The match considers recipient, definition, subject record, timing and scope. Read or archived items do not absorb later requests. Matching work shares a transaction lock. A successful collapse updates the notice and retains contribution references. Withdrawal removes one contribution and can transfer ownership or supersede the item. Rendering after withdrawal is conditional on remaining data and recipient eligibility. Those conditions can leave earlier wording visible even after the newest contribution disappears.

The rule rows define this outcome; the acceptance set identifies existing proof and proposed checks. Implementation evidence alone does not approve the observed details.

Relationships

Recipient selection supplies the eligible people and their audience explanations.

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.

Outcomes: Matching event bursts share one recipient notice.Withdrawal updates folded content when rerendering remains possible.
Surfaces: job
Intent sources: services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#2. Scopeservices-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#PLAT-M23-S11

Controls

27 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

Business Rules

8 rules, 8 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Within the configured collapse interval, requests for the same definition, recipient and subject record can share a notice; the default interval is two minutes; zero disables collapse; Different records or recipients remain separate. no proof recorded yet	calculation	service	test services-platform:modules/notifications/tests/integration/services/orchestration/cancel-and-supersede.integration.spec.js#folds five requests into one notification carrying the latest data and the count
`02`must prove Proposed	Only applicable, unread and unarchived notices accept another contribution; Otherwise processing creates a fresh unread notice. no proof recorded yet	policy	service	test services-platform:modules/notifications/tests/integration/services/orchestration/cancel-and-supersede.integration.spec.js#makes a new, unread notification when the one it would fold into was read
`03`must prove Proposed	When both contributions specify a scope, collapse requires equal scopes; a contribution without a scope can match a scoped notice. no proof recorded yet	policy	service	test services-platform:modules/notifications/tests/integration/services/orchestration/cancel-and-supersede.integration.spec.js#folds requests of the same scope and keeps requests of another scope apart
`04`must prove Proposed	Collapse adopts the latest contribution's data and wording, increases the contribution count and retains the latest fifty request references. no proof recorded yet	calculation	service	test services-platform:modules/notifications/tests/unit/collapsing.spec.js#keeps the newest fifty and drops the oldest
`05`must prove Proposed	A transaction lock serializes matching recipient, definition, record and scope identities; work with a different lock identity proceeds independently. no proof recorded yet	invariant	service, database	test services-platform:modules/notifications/tests/integration/services/orchestration/cancel-and-supersede.integration.spec.js#folds ten requests dispatched at the same moment into one notification of collapsed count nine
`06`must prove Proposed	Removing a contribution reduces the count and can move ownership to the oldest remaining open request; Removing the latest contribution refreshes wording when renderable; removing the final contribution supersedes the notice. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/orchestration/cancel-and-supersede.integration.spec.js#keeps the notification when the first of its requests ends, handing it to the next and dropping the count
`07`must prove Proposed	An occurrence produces at most one notice for each recipient even when repeated requests cross monthly boundaries. no proof recorded yet	invariant	service, database	test services-platform:modules/notifications/tests/integration/services/orchestration/orchestrate-request.integration.spec.js#makes one instance for one occurrence however many requests name it
`08`must prove Proposed	When link data has been redacted or the recipient is no longer eligible, a collapsed notice retains its earlier wording rather than re-rendering after withdrawal. no proof recorded yet	policy	service	observed services-platform:modules/notifications/services/orchestration/orchestrate-request.ts:rerenderMessage

Scenarios

Id	Given	When	Then	Provenance
`01`	Jane receives five Batch posting assignment events within two minutes with different ending dates.	All matching events pass through processing.	One unread item presents the latest details and four additional collapsed contributions.	test react-console:acceptance/notifications/playwright/journeys/pipeline/NT-ACC-0205.spec.ts#NT-ACC-0205

Planning

Combine repeated events into one notice ​

Purpose ​

How It Works ​

Relationships ​