Skip to main content

Performance Compatibility and Cutover Operations

Summary​

The gateway-facing compatibility workspace reduces the canonical lifecycle to flat goal records. Create/update/delete behavior and evidence differ from canonical paths, and compatibility writes do not emit canonical lifecycle events.

Source includes parity comparison and a cutover assessment script. Their existence does not authorize production cutover. Safe governance requires approved scope, sanitized parity results, dependency readiness, unresolved-gap ownership, go/no-go approval, observation criteria, and an approved rollback decision.

Retirement timing, acceptable parity thresholds, freeze policy, and authoritative write path require confirmation.

Safety and confirmation boundary​

No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.

Source References​

  • microservices/src/performance-service/Api/PerformanceCompatEndpoints.cs
  • microservices/src/performance-service/Application/Compatibility/PerformanceCompatService.cs
  • microservices/scripts/compare-performance-parity.ps1
  • microservices/scripts/performance-cutover-go-no-go.ps1

See Also​

Keywords​

  • Performance operations
  • Safe support guidance

Revision Information​

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