Skip to main content

Expense Cutover and Rollback

Summary

Source-backed cutover assets support readiness, backfill/parity validation, gateway routing change, observation, and routing rollback. This page does not reproduce environment-specific commands.

Audience

  • DevOps engineers, support engineers, QA engineers, developers, solution architects, and the accountable product owner.

Prerequisites

  • Approved change authority, named owners, verified monitoring, a tested recovery path, and environment-specific values supplied through controlled channels.

Procedure

Follow the verified runbook below. Treat every stop condition as binding and retain the evidence generated by each checkpoint.

Rollback or Recovery

Use the repository rollback script only under approved change control. Restore the prior routing posture, validate health and parity, and escalate instead of changing persisted Expense data directly.

Escalation

Escalate when ownership is unclear, a dependency is unhealthy, parity cannot be established, or rollback does not restore the prior verified state.

Runbook

Preconditions

Approved owners, backup/recovery posture, source/target access, validation criteria, rollback decision authority, and communication plan.

Safe execution principles

Use the repository runbook and approved automation; record evidence; stop on invariant/parity failure; do not improvise direct data changes. Treat rollback as routing restoration followed by reconciliation, not data undo.

Validation

Claims and statuses, compatibility parity, receipt references where in scope, outbox state, downstream projections, and route ownership.

Requires confirmation

Production approval chain, maintenance window, rollback owner, reconciliation SLA, and completed rehearsal require confirmation.

Source References

  • microservices/docs/expense-cutover-runbook.md
  • microservices/scripts/expense-cutover-go-no-go.ps1
  • microservices/scripts/compare-expense-parity.ps1
  • microservices/src/gateway-api/Program.cs

See Also

Keywords

  • Expense operations
  • Cutover and Rollback

Revision Information

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