Skip to main content

Technical Source Map

Summary​

This reference identifies the implementation sources used for Epic 14.2. It intentionally avoids publishing endpoints, payload contracts, configuration values, infrastructure addresses, database schema details, or test execution commands.

Audience​

Developers, QA, support, reviewers, and solution architects maintaining evidence traceability.

Reference Content​

TopicPrimary source areas
Host composition and endpoint registrationmicroservices/src/recruitment-service/Program.cs; Api folder
Application commands and queriesApplication/Commands; Application/Queries
Compatibility translationApplication/Compatibility; monolith Controllers/RecruitmentController.cs
Domain aggregates and eventsDomain/Recruitment; Domain/Repositories.cs
Persistence, tenancy, audit, timelineInfrastructure/RecruitmentDbContext.cs; Infrastructure/Persistence.cs
Employee and document gatewaysInfrastructure/EmployeeServiceClient.cs; Infrastructure/Gateways.cs
Workflow integrationApplication/WorkflowIntegration.cs; Infrastructure/WorkflowServiceClient.cs
Outbox relayMessaging/OutboxRelayHostedService.cs
Gateway transition routingmicroservices/src/gateway-api/Program.cs
Monolith exit lifecycleControllers/HrOperationsController.cs; Models/ExitRequest.cs; Models/ExitRequestAuditLog.cs
Monolith checklist/task modelModels/OnboardingTask.cs; Models/CandidateOnboarding.cs
Employee lifecyclemicroservices/src/employee-service/Domain/Employees; employee application commands
Payroll projectionmicroservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
Leave projectionmicroservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
Attendance boundarymicroservices/src/attendance-service/Application/Services/EmployeeProfileService.cs
Asset clearancemicroservices/src/asset-service/Application/Queries/AssetQueries.cs
Notification resolutionmicroservices/src/notification-service/Application/EventNotificationResolver.cs; monolith notification templates controller
Shared telemetry and correlationmicroservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs; Middleware/CorrelationIdMiddleware.cs
Client routing and pagesclient portal App.tsx, AppLayout.tsx, Recruitment Onboarding and HR Operations pages
Automated evidencemicroservices/scripts/smoke-recruitment.ps1; microservices/scripts/smoke-employee.ps1

Evidence rules​

  • A registered client or model is not treated as a completed integration without an invocation path.
  • A domain event is not treated as a notification or downstream update without a verified consumer.
  • Frontend visibility is not treated as server authorization.
  • A compatibility response is not treated as semantic side-effect parity.
  • Missing source evidence is recorded as Not implemented or Require confirmation, depending on what can be concluded.

Source References​

  • microservices/src/recruitment-service
  • microservices/src/gateway-api/Program.cs
  • microservices/src/employee-service
  • Controllers/RecruitmentController.cs
  • Controllers/HrOperationsController.cs
  • Data/AppDbContext.cs
  • UI/salary-ui/apps/client-hrms-portal/src/App.tsx

See Also​

Keywords​

  • Evidence traceability
  • Source map
  • Implementation ownership

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly