Skip to main content

Performance Contract Versioning

Summary​

All seven mappings use schema version 1. The shared base supplies identity, type, occurrence, source and contextual metadata; shared JSON serialization omits null values.

Notification reads the version but has no confirmed adapter, rejection branch, or unsupported-version policy. Additive optional changes are safest; removed/renamed fields or changed meaning are breaking. Registry, compatibility gates, deprecation, and retirement governance are Foundation.

Requires confirmation​

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

Source References​

  • microservices/src/contracts/Events/IntegrationEvent.cs
  • microservices/src/contracts/Events/PerformanceLifecycleEvents.cs
  • microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs
  • microservices/src/shared-kernel/Outbox/IntegrationEventJsonSerializer.cs

Revision Information​

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