Deliver Committed Record and Link Events

Purpose

Other Rhythm workflows need reliable notification of relevant custom-record changes. A retained event ledger and dispatch work separate that notification from the originating save.

How It Works

A publisher writes the event inside the mutation transaction. After commit it can wake dispatch without moving the fact outside that transaction. The dispatcher resolves destinations and offers queued deliveries. Accepted work can leave the waiting queue while the ledger retains the event. The consumer reports failed deliveries for retry. A nightly sweep removes eligible old ledger entries without deleting events still waiting for dispatch. Ordinary link updates and CRM merge link changes currently have no event publication, and Platform has no native subscriber yet.

Relationships

Records and relationships publish events. Integration delivery and shared event infrastructure provide destinations and transport.

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: Other Rhythm workflows need reliable notification of relevant custom-record changes.A nightly sweep removes eligible old ledger entries without deleting events still waiting for dispatch.
Surfaces: job
Intent sources: services-platform:docs/milestones/PLAT-M7-custom-record-loads-reports-events.md#Scope (Proposed; architecture approved 2026-10-18)services-platform:docs/proposals/custom-objects/09-decisions.md#2. Choices taken as internal (event names)

Controls

26 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-DAT-004 TC-IAM-001 TC-IAM-006 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`system (no user permission key; events are written by the record and link writes)`	service	tenant

Business Rules

9 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	Record lifecycle and property mutations and link creation, ending or deletion append their event in the mutation transaction, while refused or rolled-back writes append nothing. proved by `ATS-PFM-MTD-012-18`, `ATS-PFM-MTD-013-10`, `ATS-PFM-MTD-015-01`, `ATS-PFM-MTD-015-08`, `ATS-PFM-MTD-018-13`, `TST-PFM-MTD-043`, `TST-PFM-MTD-048`, `TST-PFM-MTD-064`	invariant	service, database	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-object-records.events.integration.spec.js#publishes nothing when the transaction that wrote the record rolls back, in the ledger or the queue
`02`must prove Proposed	Record events identify the object, record, prefixed number, name, publication state and author, with update events listing changed property keys in sorted order. proved by `ATS-PFM-MTD-015-02`, `TST-PFM-MTD-048`, `TST-PFM-MTD-064`	calculation	service	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-object-records.events.integration.spec.js#publishes objects.record.updated naming the properties whose value changed, sorted
`03`must prove Proposed	Unchanged property values, external-identifier-only changes, repeated publication states and link updates that do not end the link produce no business event. proved by `ATS-PFM-MTD-015-03`, `TST-PFM-MTD-043`, `TST-PFM-MTD-064`	policy	service	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-object-records.events.integration.spec.js#publishes nothing for an update that changes no property’s value
`04`must prove Proposed	Events retain a ledger entry and waiting work until dispatch destinations accept their messages; any refused destination leaves work for another run without removing the ledger fact. proved by `ATS-PFM-MTD-015-04`, `TST-PFM-MTD-056`	lifecycle	service	test services-platform:modules/custom-objects/tests/integration/services/dispatch/business-events.integration.spec.js#keeps its queue row, claimed, for the next run to offer again
`05`must prove Proposed	Consumption sends the event to native subscribers or its versioned external-router contract to the router and reports only failed messages for redelivery. proved by `ATS-PFM-MTD-015-05`, `TST-PFM-MTD-056`	policy	service	test services-platform:modules/custom-objects/tests/integration/services/dispatch/business-events.integration.spec.js#answers the one message whose destination refused, so SQS offers that one again
`06`must prove Proposed	The nightly ninety-day sweep retains events still referenced by waiting queue rows; workspace reset or deletion purges the workspace events. no proof recorded yet	lifecycle	service	observed services-platform:modules/custom-objects/services/persistence/business-events.ts:sweepBusinessEvents
`07`must prove Proposed	Deletions announce link removals and cascaded records before the records they depend on. origin: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 B1 proved by `ATS-PFM-MTD-015-06`, `ATS-PFM-MTD-015-08`, `ATS-PFM-MTD-019-10`, `TST-PFM-MTD-064`	policy	service, database	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-object-records.events.integration.spec.js#publishes the deletion of the record a cascade takes, with its own object’s number, and the association’s
`08` Proposed	Platform has no native subscribers yet, and CRM merge moves or endings of links produce no business event.	policy	service	documented services-platform:docs/custom-objects.md#Events
`09`must prove Proposed	Retention sweeps refuse durations below one day or durations that are not whole numbers. proved by `ATS-PFM-MTD-015-07`, `TST-PFM-MTD-058`	validation	service	test services-platform:modules/custom-objects/tests/integration/services/persistence/business-events.integration.spec.js#refuses a retention shorter than a day

Scenarios

Id	Given	When	Then	Provenance
`01`	A registrar submits a valid boat create.	Commit it and compare a refused create.	The committed create leaves its creation event and dispatch work with the actor recorded; the refusal leaves no event.	test services-platform:modules/custom-objects/tests/e2e/business-events.e2e.spec.js#leaves no event for a create the API refuses

Edge Cases

Id	Given	When	Then	Provenance
`02`	No destination subscribes to an event.	Run dispatch.	No delivery is sent and the waiting queue entry is removed.	test services-platform:modules/custom-objects/tests/integration/services/dispatch/business-events.integration.spec.js#deletes its queue row where it stands

Planning

Implementation

Deliver Committed Record and Link Events ​

Purpose ​

How It Works ​

Relationships ​