Skip to content
notifications

notifications

The member’s notification inbox: the one way to send into it, and the list the navbar bell and the notifications page read. Package @unset/domains-notifications. The design is ADR 0079, Accepted, with point 3 amended by ADR 0081, Proposed: an entry stays until the member dismisses it.

Owns

The closed list of reasons, what a notification may carry, the list’s caps and how long an entry lives. The rows are in app.notification (migration 0036), behind infrastructure/postgres/notificationStore.ts; this folder opens no socket.

ModuleWhat it holds
domains/notifications/index.tsPackage root. Re-exports the names below.
domains/notifications/notifications.tsnotify (the send call), inboxList, REASONS, parseNotificationId, parseNotificationIds, the Inbox (list, dismiss, dismiss up to) and Outbox ports, BELL_LIMIT (5), PAGE_LIMIT (50), DISMISS_MAX (50), COUNT_CAP (10), KEEP_DAYS (30).
ReasonSent by
sign_inThe OAuth callback, in the transaction that makes the session; only browsers signed in before it see it.
privacy_noticeThe OAuth callback, once per notice version, when the changed-notice banner would show; withdrawn when the banner is dismissed.

A notification carries a reason, an optional topic (1 to 64 printable ASCII characters) and an optional dedupe key (1 to 128). Nothing a person typed is stored: the words come from the screens’ reason table.