Abhishek Saxena

Notifications & Comms Center · Documentation

Architecture

Notifications & Comms Center's pipeline, its owned data, the events it emits/consumes, and what is out of scope.

← Notifications & Comms Center
eventtriggertemplatepickpersonalise$0msg-genmeteredsendsimulatedmetered · LLMdeterministic · $0
Live diagram — transactional sends are deterministic; only the marketing message-gen variant is metered.
event$0template$0personalise$0$msg-genmeteredsend$0COST LEVER · marketing variants only
Live diagram — confirmations and receipts are free; spend accrues only on an AI marketing variant.

Owned data + shared-core reads

The center owns and writes `notification` and `notification_template` (plus a `cost_ledger` row per AI variant), and reads shared-core `guest` and `booking` for sample + trigger context. The data invariant holds: an owner's template config (enable/edit) is canonical and mirrors durably, while a viewer's AI-variant generation is ephemeral (a credential-tagged cost row that resets) and does not change template state.

Metered AI + out of scope

One metered stage — `message-gen` (marketing variant composition) — dual-mode by design (Cloud `claude-haiku-4-5`, cost-capped/fail-closed / OSS recorded $0 on local hardware), running OSS-only and honestly labelled simulated (curated variant copy). Out of scope and clearly labelled: ALL delivery — email, SMS, and push are simulated into the in-app sent viewer; no real message leaves the demo. Cost, mode, and trace are inspector-only.

Architecture · Notifications & Comms Center · Abhishek Saxena