Skip to main content

Performance Publishing Flow

Summary​

Canonical commands or accepted Workflow callbacks mutate aggregates, stage evidence, and save.

Workflow start and callback may span multiple saves; there is no distributed transaction. Duplicate terminal callbacks are state-checked and do not reapply. Compatibility/backfill methods do not create canonical lifecycle events.

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
  • microservices/src/performance-service/Application/Commands/AppraisalCommands.cs
  • microservices/src/performance-service/Application/Commands/ReviewCycleCommands.cs
  • microservices/src/performance-service/Messaging/OutboxRelayHostedService.cs

Revision Information​

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