Skip to main content

Performance Event Overview

Summary​

Domain events are aggregate-local state-change evidence; shared contracts are their cross-service representation.

ReviewCycle produces open/close signals. Appraisal produces goal, self-review, manager-review, approval, and finalization signals. The local save is atomic; publication and consumer effects are eventually consistent. Identity, occurrence, schema, tenant, actor, correlation and causation are envelope concepts, but current Performance mapping leaves correlation and causation unset.

Requires confirmation​

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

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

Revision Information​

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