Store notification preferences and channel configuration

Purpose

Platform stores future delivery choices and their validation, without representing them as active runtime preferences.

How It Works

Platform persistence accepts category preferences and definition exceptions for future channel selection. Workspace settings and wording are stored separately from personal choices. Validation preserves mandatory and console requirements. Version checks prevent overwriting an update based on stale state. Successful workspace changes append audit information. Identity and phone-challenge records track future reachable destinations. Text reservations and digest records provide accounting primitives. The current pipeline and console do not expose or apply these stored choices.

Stored configuration is evidence of persistence behavior; future channel selection still requires a product plan and implementation.

Relationships

Registration supplies the event contract that later work validates and renders.

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: Stored settings validate category, definition and channel choices.The implemented runtime does not yet consume these future delivery preferences.
Surfaces: consoleapi
Intent sources: services-platform:docs/proposals/notifications/23-decisions.md#D-05services-platform:docs/proposals/notifications/23-decisions.md#D-10

Controls

31 controls apply, from the corpus control catalogue.

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-002 TC-IAM-004 TC-IAM-005 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-PRV-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01` Confirmed	Personal preferences store channel switches and digest selection for each category, with optional overrides for individual definitions. origin: services-platform:docs/proposals/notifications/23-decisions.md#D-05	policy	service	documented services-platform:docs/proposals/notifications/23-decisions.md#D-05. The preference grain is the category, with per-definition exceptions
`02`must prove Proposed	Preferences require known categories or definitions and valid switches; console cannot be disabled, mandatory e-mail cannot be disabled when supported, a nonempty channel-configurable override includes an enabled switch, and per-definition daily digest requires digestibility, while empty overrides and category-level digest selection remain valid. no proof recorded yet	validation	service	observed services-platform:modules/notifications/services/persistence/preferences.ts:refuseInvalid
`03`must prove Proposed	Preference and setting writes use optimistic versions; initial creation needs none, while subsequent writes require the version read; omitted or stale versions reject the entire update. no proof recorded yet	validation	service, database	test services-platform:modules/notifications/tests/integration/services/persistence/preferences.integration.spec.js#refuses a stale version with a 409 and leaves the choice as it was
`04`must prove Proposed	Workspace channel defaults enable console and e-mail and disable chat and text; console cannot be disabled, connections apply only to connected channels, and text limits use whole segment counts. no proof recorded yet	validation	service	test services-platform:modules/notifications/tests/integration/services/persistence/channel-settings.integration.spec.js#answers the defaults for a tenant that wrote nothing: the console and e-mail on, chat and SMS off
`05`must prove Proposed	Workspace definition settings cannot disable mandatory notices, turn them into another requirement or narrow them below e-mail; Allowed channels are supported by the definition and include console. no proof recorded yet	validation	service	test services-platform:modules/notifications/tests/integration/services/persistence/definition-settings.integration.spec.js#refuses to turn a mandatory definition off
`06`must prove Proposed	Wording drafts advance numbered versions with one active override per definition, channel and locale; Publication checks field use and rendering limits; deactivation removes the override, while the current pipeline does not apply these overrides. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js#leaves exactly one active version per definition, channel and locale
`07`must prove Proposed	Successful workspace channel, definition-setting and wording changes record actor and before-and-after audit data; Rejected updates produce no audit entry. no proof recorded yet	policy	service	test services-platform:modules/notifications/tests/integration/services/persistence/channel-settings.integration.spec.js#audits the first write as a create and an update with the before and after
`08`must prove Proposed	Quiet-hour storage requires unequal start and end times and distinct weekdays numbered one to seven; Digest delivery time defaults to 08:00 and accepts only valid times of day. no proof recorded yet	validation	service	test services-platform:modules/notifications/tests/integration/services/persistence/user-settings.integration.spec.js#refuses quiet hours that begin and end together
`09`must prove Proposed	A person holds one current identity per chat or text channel, and a phone number identifies one person; Pending identities can become active, unreachable, opted out or revoked; revoked is terminal. no proof recorded yet	lifecycle	service, database	test services-platform:modules/notifications/tests/integration/services/persistence/identities.integration.spec.js#refuses a second current identity on a channel for the same person
`10`must prove Proposed	Phone challenges retain a code digest, allow one open challenge per number and expire; Five incorrect submissions exhaust a challenge. no proof recorded yet	validation	service	test services-platform:modules/notifications/tests/integration/services/persistence/identities.integration.spec.js#spends the challenge after five wrong codes, refusing even the right one
`11`must prove Proposed	Text sending reserves segments against the workspace's UTC calendar-month allowance; Atomic reservation admits only sends that fit; zero admits none, and the first ceiling refusal time is retained. no proof recorded yet	calculation	service, database	test services-platform:modules/notifications/tests/integration/services/persistence/sms-usages.integration.spec.js#lets only the sends that fit through when they race at the edge
`12` Proposed	Digest records identify one recipient, category and window; Opening is idempotent, contributions increment the count while open, and settlement happens once.	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/persistence/digests.integration.spec.js#answers the digest already open for the same person, category and window
`13`must prove Proposed	Stored preferences have no user interface or runtime effect yet; All definitions are treated as enabled, and individual delivery remains console-only. no proof recorded yet	policy	service	observed services-platform:modules/notifications/services/orchestration/orchestrate-request.ts:definition_disabled

Scenarios

Id	Given	When	Then	Provenance
`01`	In a future preference release, Jane wants assignment e-mail and console delivery while suppressing optional job notices.	Jane chooses both assignment routes and disables her jobs category.	The proposed outcome delivers assignments on those routes and suppresses optional jobs, while mandatory supported routes remain enabled.	proposed services-platform:docs/proposals/notifications/23-decisions.md#D-05. The preference grain is the category, with per-definition exceptions

Planning

Store notification preferences and channel configuration ​

Purpose ​

How It Works ​

Relationships ​