Performance Events Documentation

Summary

Seven source-confirmed Performance domain events map to seven shared outbound contracts through a transactional outbox.

Audience

Engineering, QA, support, architecture, security, and implementation teams responsible for Performance integrations.

Overview

This section separates aggregate-local events, shared contracts, transactional publication intent, relay delivery, and consumer-owned effects. It records implemented behavior and verified gaps without implying distributed delivery guarantees.

Documentation map

Overview · Domain events · Integration events · Publishing · Delivery · Consumers · Catalog · Testing

The mapping and Notification path are implemented. Broader consumer ownership, replay, terminal failure policy, and compatibility parity remain Transitional or Foundation.

Requires confirmation

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

Related Articles

• Performance event overview
• Verified event catalog

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

Revision Information

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