Performance Domain Events

Summary

Audience

Developers, QA and support engineers, integration reviewers, solution architects, and implementation partners.

Reference Content

Exactly seven types are invoked: ReviewCycleOpenedDomainEvent, ReviewCycleClosedDomainEvent, GoalCreatedDomainEvent, AppraisalSelfSubmittedDomainEvent, AppraisalManagerReviewedDomainEvent, AppraisalApprovedDomainEvent, and RatingFinalizedDomainEvent.

Each maps one-to-one to the same base name without the Domain suffix. Commands coordinate audit/timeline evidence. Creation, intermediate cycle phases, HR review, reopen, close, goal update, and generic review submission have no dedicated domain event. Evaluation content is intentionally excluded.

Requires confirmation

Operational ownership, service objectives, reconciliation, replay, and future consumer governance require confirmation where not explicitly implemented.

Related Articles

• Performance events documentation
• Event overview

See Also

• Performance technical documentation
• Performance database documentation

Keywords

• Performance events
• Integration contracts

Source References

• microservices/src/performance-service/Domain/ReviewCycle/ReviewCycleDomainEvents.cs
• microservices/src/performance-service/Domain/Appraisal/AppraisalDomainEvents.cs
• microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs
• microservices/src/contracts/Events/PerformanceLifecycleEvents.cs
• microservices/src/performance-service/Domain/ReviewCycle/ReviewCycle.cs
• microservices/src/performance-service/Domain/Appraisal/Appraisal.cs

Revision Information

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