Notification Technical Source Map

Summary

This reference maps each technical topic in this section to the primary source that supports it, so every claim is reviewable against backend and frontend code.

Audience

Engineers, QA, support, architects, security reviewers and documentation maintainers.

Reference Content

Technical topic	Primary source evidence	Documented in
Composition root, DI, startup migration/seed	microservices/src/notification-service/Program.cs	Runtime composition, architecture
Configuration model	microservices/src/notification-service/Application/NotificationOptions.cs	Runtime composition, retry
End-to-end orchestration	microservices/src/notification-service/Application/NotificationDispatcher.cs	Processing, delivery, retry, service anatomy
Event-to-intent resolution and coverage	microservices/src/notification-service/Application/EventNotificationResolver.cs	Service anatomy, processing
Abstractions, records, outcomes	microservices/src/notification-service/Application/Abstractions.cs	Application layer, commands, queries
Template resolution and rendering	microservices/src/notification-service/Application/TemplateEngine.cs	Template architecture, queries
Preference evaluation	microservices/src/notification-service/Application/PreferenceEvaluator.cs	Processing, queries
Retry schedule	microservices/src/notification-service/Application/RetryPolicy.cs	Retry pipeline
Dispatch telemetry	microservices/src/notification-service/Application/NotificationTelemetry.cs	Logging and observability
Channel senders and registry	microservices/src/notification-service/Channels/	Channel architecture, delivery
Entities, statuses, stages, constants	microservices/src/notification-service/Domain/NotificationEntities.cs	Repositories, processing
Persistence mapping and indexes	microservices/src/notification-service/Infrastructure/NotificationDbContext.cs	Repositories, tenant isolation
Schema migration	microservices/src/notification-service/Infrastructure/Migrations/	Repositories
Event consumer and envelope	microservices/src/notification-service/Messaging/	Background processing
Default template inventory	microservices/src/notification-service/Seed/DefaultTemplateSeeder.cs	Template architecture
API surface	microservices/src/notification-service/Api/NotificationEndpoints.cs	Commands, queries, validation
Shared observability helpers	microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs	Logging and observability
Gateway routing toggle and shadow	microservices/src/gateway-api/Program.cs	Compatibility, authentication
Gateway ESS inbox integration	microservices/src/gateway-api/EssEndpoints.cs	Compatibility
Legacy monolith controllers	Controllers/NotificationsController.cs; Controllers/NotificationTemplatesController.cs	Compatibility
Portal inbox surface	UI/salary-ui/apps/client-hrms-portal/src/pages/NotificationsPage.tsx	Compatibility
Smoke coverage	microservices/scripts/smoke-notification.ps1	Testing

Integrations

The map spans the extracted notification service, the gateway, the legacy monolith controllers and the client portal because current behavior crosses all four boundaries.

Limitations

Repository source is evidence of implementation, not proof of runtime enablement. No deployment manifests, live environments, provider consoles or database contents were treated as authoritative.

Requires Confirmation

Repository ownership, production feature-flag state and the canonical source list for the next review require confirmation.

Source References

• microservices/src/notification-service/
• microservices/src/gateway-api/Program.cs
• microservices/scripts/smoke-notification.ps1
• Controllers/NotificationsController.cs
• UI/salary-ui/apps/client-hrms-portal/src/pages/NotificationsPage.tsx

Related Articles

• Technical overview
• Architecture overview
• Technical limitations

See Also

• Business source map
• Compatibility

Keywords

Source map, traceability, evidence, backend, frontend.

Revision Information

• Status: Draft
• Last reviewed: 2026-07-21
• Next review: 2026-10-21