Skip to main content

Rollback Plan

Reviewed on: 2026-01-21 Status: Draft (requires deployment-specific approval)

This document defines a baseline rollback strategy for services using Primus.

Goals​

  • Restore service availability quickly.
  • Minimize data loss.
  • Preserve auditability.
  1. Maintain a previous stable release artifact.
  2. Use blue/green or canary deployment where possible.
  3. Roll back application code before applying database down-migrations.
  4. If database migrations are irreversible, use feature flags to disable affected features.

Checklist​

  • Release artifacts are versioned and stored.
  • Feature flags or kill switches exist for critical workflows.
  • Rollback runbook is tested in staging.

Review Log​

  • 2026-01-21: Baseline rollback plan documented. Approval pending.