Remove notices that have become stale

Purpose

Producers and Platform stop pending delivery when an event is withdrawn, replaced or too old to remain useful.

How It Works

A producer cancels work that no longer represents a useful event. Processing matches cancellation to the request or replacement identity. An earlier cancellation prevents the corresponding pending publication from reaching recipients. A later cancellation marks delivered console content no longer applicable rather than erasing its history. Pending channel work is stopped, while completed external sends remain recorded. Replacement applies only when the definition permits it and the new request is valid. Future work waits until due, and stale work expires. Reconciliation settles requests after expiry and completion of outstanding work.

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

Committed publication supplies the requests processed by this outcome.

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: Withdrawal stops applicable pending work and hides stale inbox items.Cancellation records the reason for ending the request.
Surfaces: jobapi
Intent sources: services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#2. Scopeservices-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#4. Assumptionsservices-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#PLAT-M23-S05

Controls

31 controls apply, from the corpus control catalogue.

TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-002 TC-LOG-003 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 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	A cancellation processed before its publication prevents notification and records cancellation, whether matched by publication key or replacement key and regardless of queue order; it does not cancel a publication submitted subsequently. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/orchestration/cancel-and-supersede.integration.spec.js#leaves nobody told and records the request cancelled when the cancel names the publish’s key
`02`must prove Proposed	Cancellation after console delivery keeps the item readable but marks it no longer applicable and removes it from unread totals; Reprocessing is harmless; settled requests are unchanged. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/orchestration/cancel-and-supersede.integration.spec.js#marks the instance superseded, leaves it readable and takes it out of the unread count
`03`must prove Proposed	Withdrawal cancels pending deliveries and removes their queued work; Messages already sent remain sent, although the console notice becomes superseded. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/orchestration/cancel-and-supersede.integration.spec.js#cancels the queued delivery and its work row, and does not recall one that already left
`04`must prove Proposed	With occurrence replacement enabled, a valid later publication using the same replacement key supersedes the earlier open request and produces a new notice; Disabled replacement and rejected later requests leave the earlier request intact. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/orchestration/cancel-and-supersede.integration.spec.js#supersedes the earlier request of a definition whose scope is the occurrence, and tells the person the new one
`05`must prove Proposed	Processing rejects expired requests without notification; Expiry uses the explicit deadline or the definition's age limit from publication, defaulting to seven days. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/orchestration/orchestrate-request.integration.spec.js#expires a request older than its definition’s expires_after from the instant the producer wrote it
`06`must prove Proposed	Future-dated work returns to the queue until its not-before instant; processing cannot deliver it early. no proof recorded yet	policy	service	test services-platform:modules/notifications/tests/integration/services/orchestration/orchestrate-request.integration.spec.js#gives back a request that is not due yet, writing nothing, never processing it early
`07`must prove Proposed	An accepted request remains open until expiry and outstanding delivery work end; Nightly reconciliation expires unsent deliveries, supersedes a notice when nothing else was sent, and settles the request; subsequent cancellation has no remaining effect. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/reconcile/reconcile-tenant.integration.spec.js#settles a request past its expiry whose notification was delivered, so a late cancel reaches nothing
`08`must prove Proposed	Before sending queued work, superseded notices cause cancellation and expired requests cause expiry. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/dispatch/deliver-delivery.integration.spec.js#cancels, not sends, a delivery whose notification was superseded after it was queued

Scenarios

Id	Given	When	Then	Provenance
`01`	Jane's new assignment ends two minutes later, before its announcement is processed.	Platform processes the announcement and withdrawal.	No assignment item appears and its request becomes cancelled; an ending announcement remains a separate outcome.	test react-console:acceptance/notifications/playwright/journeys/inbox/NT-ACC-0005.spec.ts#NT-ACC-0005
`02`	Jane read an assignment announcement the previous day.	The producer ends that assignment.	The retained item becomes inapplicable and cannot contribute to unread totals.	inferred react-console:acceptance/notifications/playwright/journeys/inbox/NT-ACC-0004.spec.ts#NT-ACC-0004

Planning

Remove notices that have become stale ​

Purpose ​

How It Works ​

Relationships ​