Onboarding & Offboarding Events and Integration Contracts
Summary
The verified onboarding/offboarding event model contains 19 domain-event types across Recruitment and Employee, with 18 mapped version-1 integration contracts. Recruitment maps 11 of 12 domain events and runs a hosted outbox relay. Employee maps all seven but does not register a hosted outbox relay in its service startup.
Payroll and Leave consume three Employee contracts to maintain local projections. Notification consumes EmployeeCreated only. Attendance and Asset do not consume Employee lifecycle events, and Asset clearance is not event-integrated with exit. Workflow uses HTTP requests/callbacks, Gateway performs routing only, and compatibility onboarding/offboarding emits no verified lifecycle integration event.
Audience
Backend and integration engineers, QA and support engineers, solution architects, security/privacy reviewers, product owners, and implementation partners.
Overview
Everything in this section remains Draft. Broker topology, infrastructure names, payloads, operational identifiers, credentials, endpoints and commands are intentionally excluded.
Confirmed totals
| Measure | Total |
|---|---|
| Recruitment domain-event types | 12 |
| Employee domain-event types | 7 |
| Domain-event types in authoritative lifecycle catalog | 19 |
| Mapped outbound integration contracts | 18 |
| Unmapped domain-event types | 1 |
| Contract schema versions represented | 1 |
| Direct lifecycle producer services | 2 |
| Confirmed Employee-event consumer services in requested scope | 3 |
| Event-driven Attendance employee synchronization | 0 |
| Event-driven Asset exit-clearance integration | 0 |
Documentation map
- Event overview, architecture, domain events, and integration contracts
- Lifecycle mapping, publishing/outbox, producer behavior, and consumer landscape
- Recruitment, Employee, Payroll, Attendance, and Leave
- Asset, Notification, Workflow, Gateway, and compatibility
- Versioning, idempotency, ordering/correlation, and retry/failure
- Testing, verified catalog, limitations, and source map
Maturity
The architecture is Transitional: Recruitment has a complete local outbox-to-relay path, Employee has contract staging but no confirmed relay invoker, consumer idempotency differs by service, and offboarding remains outside the extracted event model.
Requires confirmation
Unless explicitly confirmed above, live delivery, consumer deployment, replay, reconciliation, retention, contract governance, monitoring and production ownership require confirmation.
Source References
microservices/src/recruitment-service/Domain/Recruitment/RecruitmentDomainEvents.csmicroservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/employee-service/Domain/Employees/Employee.csmicroservices/src/employee-service/Infrastructure/EmployeeDbContext.csmicroservices/src/shared-kernel/Messaging/OutboxProcessor.cs
Related Articles
See Also
Keywords
- Onboarding events
- Offboarding events
- Integration contracts
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly