Lifecycle-to-Contract Mapping

Summary

This is the authoritative one-row-per-transition mapping from lifecycle action to domain event, contract, producer and confirmed requested-scope consumers.

Audience

Product owners, architects, integration engineers, QA, and support teams.

Reference Content

#	Business transition	Domain event	Contract	Producer	Confirmed requested-scope consumer
1	Candidate applies	CandidateAppliedDomainEvent	CandidateApplied	Recruitment	None
2	Interview scheduled	InterviewScheduledDomainEvent	InterviewScheduled	Recruitment	None
3	Offer generated	OfferGeneratedDomainEvent	OfferGenerated	Recruitment	None
4	Offer created	OfferCreatedDomainEvent	OfferCreated	Recruitment	None
5	Offer approved	OfferApprovedDomainEvent	OfferApproved	Recruitment	None
6	Offer accepted	OfferAcceptedDomainEvent	OfferAccepted	Recruitment	None
7	Offer rejected	OfferRejectedDomainEvent	OfferRejected	Recruitment	None
8	Offer declined	OfferDeclinedDomainEvent	OfferDeclined	Recruitment	None
9	Offer withdrawn	OfferWithdrawnDomainEvent	None	Recruitment	None
10	Onboarding completed	CandidateOnboardedDomainEvent	CandidateOnboarded	Recruitment	None
11	Candidate marked joined	CandidateJoinedDomainEvent	CandidateJoined	Recruitment	None
12	Joining reminder created	JoiningReminderDomainEvent	JoiningReminder	Recruitment	None
13	Employee created	EmployeeCreatedDomainEvent	EmployeeCreated	Employee	Payroll, Leave, Notification
14	Employee updated	EmployeeUpdatedDomainEvent	EmployeeUpdated	Employee	Payroll, Leave
15	Employee marked deleted	EmployeeDeletedDomainEvent	EmployeeDeleted	Employee	None
16	Manager changed	ManagerChangedDomainEvent	ManagerChanged	Employee	None
17	Department changed	DepartmentChangedDomainEvent	DepartmentChanged	Employee	None
18	Employment status changed	EmploymentStatusChangedDomainEvent	EmploymentStatusChanged	Employee	Payroll, Leave
19	Timeline event explicitly recorded	EmployeeTimelineEventRecordedDomainEvent	EmployeeTimelineEventRecorded	Employee	None

Employee provisioning between rows 10/11 and 13 is synchronous HTTP, not a contract consumption path. No exit transition has a mapped event.

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/Infrastructure/RecruitmentDbContext.cs
• microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs
• microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs

Related Articles

• Events documentation
• Technical documentation

See Also

• API documentation
• Database documentation

Keywords

• Onboarding events
• Offboarding events
• Integration contracts

Revision Information

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