Notification Infrastructure — Slice 1

Local Implementation Certified

← All Architecture documents

Notification Infrastructure v1.0 — Slice 1

Status: Local Implementation Certified · 2026-08-09 Slice: In-App Core only Architecture: Philosophy · Domain · Baseline remain LOCKED

First institutional application slice to complete the full cycle: Architecture → Spec → Implementation → Automated → Manual UI → Local Certification.

Purpose

Prove the Standing Rule in working software:

Modules emit events. Notification Infrastructure decides if, how, and where recipients are notified.

Origin Module
        ↓
Institutional Event
        ↓
Notification Decision
        ↓
Notification
        ↓
Recipient Resolution
        ↓
Delivery: in_app
        ↓
Unread → Read | Dismissed

In: in-app only. Out: email · push · SMS · preference center · Notification Center product root.

Certified locally

  • Event ≠ Notification ≠ Delivery
  • Three-level idempotency (Event · Notification · Delivery)
  • Recipient Account snapshot at decision time
  • Action target from validated Context / router policy only
  • Live proof paths: article.published · identity.follow_created
  • Legacy flat notifications table is not on the write path

Schema

  1. nfb_events — permanent facts
  2. nfb_notifications — disposable decisions (snapshotted Account)
  3. nfb_notification_deliveries — in_app channel

Standing Rule (Slice 1 frozen)

No new events, channels, features, or UI in Slice 1. Bugs may be fixed; everything else waits for Slice 2+.

Related