Phase 26.1 (Sprints 1-5) is complete and frozen
(IRA26.1-NOTIFICATION-CENTER-PRODUCTION-READY) -- Dashboard, Inbox, Channels
(Email), Delivery History, and Reports are real and operationally verified against real AWS SES.
Factory lifecycle events (Start/Pause/Resume/Stop/Emergency Stop/failed-to-start) and the
LinkedIn security halt now publish real events (2026-07-30, Decision 045) -- see the Settings
tab to control which of those 7 also send email. Rules/Templates remain Coming Soon --
deliberately deferred until a real operational need justifies building a generic engine
(see FOC-FEAT-001C); Settings below is NOT that engine, just 7 fixed on/off
switches for events that actually exist today.
Execution Profile: .
Individual notification events do not carry this field yet -- adding it there is a backend change,
out of scope for the UI-only IRA26.3.1 pass (see docs/IRA26_3_1_EXECUTION_PROFILE_UI_DESIGN_2026_07_28.md).
| Title | Severity | Type | When | ||
|---|---|---|---|---|---|
| Loading… | |||||
Real customer/revenue lifecycle events (signup, verification, payment method,
request submitted/completed/zero-results/downloaded), read live from BOTH real
customerNotificationOutbox tables (apps/api + apps/factory-api) -- deliberately kept separate from
the Factory/Operations events elsewhere on this page, per the standing instruction not to flood customer/revenue
notifications with technical worker noise. "Delivered" below means the real operator email actually sent
(manoj@5winfo.com), not customer-facing delivery.
| Event | Title | Request/Subject | Source | Created | Delivered |
|---|---|---|---|---|---|
| Loading… | |||||
Rules Coming Soon
Rule management UI -- no rules exist yet to manage (none are seeded by any real producer). Comes with a later sprint once real Factory/Supervisor events publish here.
UI
Operationally verified 2026-07-27 against real AWS SES SMTP credentials (Test Email + full Event->Rule->Engine->Delivery->Dispatch->SES->real-mailbox pipeline) -- see the Notification Center Production Readiness Review. Known gap: every dispatched email goes to the single Default Recipient above; per-recipient routing via Notification Profiles needs a schema addition not yet built.
Templates Coming Soon
Editable per-event templates -- Sprint 4, alongside Email delivery.
Generate Report
Computed directly from real Notification/Delivery data -- no Campaign Analytics (Campaign Engine doesn't exist yet) and no precomputed statistics table (no real production volume yet to justify one). Both are real future enhancements, not omissions.
| Type | Generated | ||
|---|---|---|---|
| Loading… | |||
| Event | Channel | Status | When | Duration | Error |
|---|---|---|---|---|---|
| Loading… | |||||
Core Factory Notification Settings
7 fixed switches for the Factory events that exist
today -- not the generic Rules/Templates engine (still Coming Soon, see
FOC-FEAT-001C). Inbox and Email are independent -- any combination is valid,
including both off if you deliberately want to silence an event entirely. Email sends to the
configured Default Recipient (Channels tab).
| Event | Inbox | |
|---|---|---|
| Loading… | ||
Scheduled Reports
Any number of schedules, 2 report types (a full Daily Operations Report, or a short Factory Status ping), 2 firing modes (once daily at a set time, or every N hours). Detail Levels and per-section content toggles are named future work, not built until real usage shows they're needed. Delivery (Inbox/Email) for either content type is controlled by its row in the table above ("Daily Operations Report" / "Factory Status Update"), same mechanism as every Factory event.
| Label | Type | Fires | Timezone | Enabled | Last Sent | |
|---|---|---|---|---|---|---|
| Loading… | ||||||