// PLATFORM — NOTIFICATION CENTER

🔔 Notification Center

One view for every alert, event, and notification across the entire MelTuc platform. Aggregates signals from Herald, SRM, Kronos, and all registered blueprints — filter, acknowledge, and triage without switching tabs.

Launch Notification Center See How It Works Learn More View Herald Directly

Premier v1.0.0 Active

Aggregation Sources

Filter Dimensions

∞

Notifications Supported

🗂

Unified Inbox

All platform alerts from Herald, SRM, and other blueprints in a single chronological feed.

🔍

Multi-Dimension Filters

Filter by source app, severity level (critical/error/warning/info), or unread-only status.

✅

Bulk Acknowledge

Acknowledge individual notifications or clear everything in one click, with optional filters applied.

📊

Live Stats

Real-time counts for total, unread, errors, and last-24h activity. Auto-refreshes every 60 seconds.

📥

CSV Export

Export any filtered view to CSV for audit logging, reporting, or external processing.

🔌

Extensible Sources

New blueprints that emit to herald_alerts are automatically included. Zero configuration required.

// HOW IT WORKS — WALKTHROUGH

From scattered alerts to one triaged feed

Notification Center reads the platform-wide herald_alerts table and presents every blueprint's signals in a single, filterable, acknowledgeable inbox — no per-app configuration required.

Blueprints emit alerts

Any app calls Herald's emit_alert() helper, writing a row to herald_alerts tagged with its source app and severity.

Open the unified inbox

Launch the app shell — it calls /api/notifications to pull every alert into one chronological feed and refreshes the stats automatically.

Filter to what matters

Narrow by source app, severity level (critical/error/warning/info), or unread-only status to focus on the signal you care about.

Acknowledge & clear

Acknowledge alerts individually or in bulk; acknowledged rows are flagged and drop out of the unread count.

Export for audit

Add format=csv to any filtered view to download a CSV for audit logging, reporting, or external processing.

HOW IT WORKS

Notification Center reads from the platform-wide herald_alerts table. Every blueprint that emits notifications via Herald's emit_alert() helper automatically appears here, tagged with its source app name.

Future sources (SNT events, Mellissa inbox actions, Kronos job completions) will be added as additional aggregation layers in blueprints/notifcenter/routes.py — the API response shape is stable and additive.