Exchange Notifications Architecture
Exchange Notifications Architecture
Section titled “Exchange Notifications Architecture”Exchange Notifications v1 provides private, in-app notifications for authenticated members.
Events
Section titled “Events”The first notification set covers:
- a new answer to your question;
- your question being hidden or restored by moderation;
- your answer being hidden or restored by moderation;
- one of your submitted reports being resolved.
Generation
Section titled “Generation”Notifications are created by D1 database triggers.
This keeps event creation coupled to the persisted state transition rather than to a specific browser or UI path.
For example, an answer notification is generated only after a published answer row is inserted.
Privacy boundary
Section titled “Privacy boundary”Notification APIs always scope reads and read-state writes to the authenticated Exchange user identifier.
A caller cannot request another user’s notification feed by passing a user identifier.
Read state
Section titled “Read state”Each notification has:
- creation time;
- optional read time.
Members can mark one notification as read or mark all current notifications as read.
Read state is account-specific.
Navigation
Section titled “Navigation”The Exchange navigation exposes Notifications to signed-in members.
The notification page links question-related events back to the relevant question.
Operational scope
Section titled “Operational scope”This v1 is intentionally in-app only.
It does not implement:
- email notifications;
- push notifications;
- SMS;
- notification preferences;
- digests;
- per-event subscriptions;
- delivery retries outside D1 persistence;
- automated retention or deletion.
Notification records remain in D1 until a later retention policy or maintenance process is defined.