Skip to main content

Performance Compatibility Events

Summary​

Compatibility writes reduce the canonical lifecycle and produce no canonical events.

Create/update retains reduced evidence; delete is more limited. Compatibility-created draft cycles do not emit open events. Backfill uses the same reduced methods. Event parity, reconciliation, cutover, and retirement are Transitional.

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/Appraisal/Appraisal.cs
  • microservices/src/performance-service/Application/Compatibility/PerformanceCompatService.cs
  • microservices/scripts/smoke-performance.ps1

Revision Information​

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