STD-REL-001: Release Management & Rollback
1. Context
To ensure deployments are not gambles. "Up is good, Down is bad, Stuck is worse."
2. The Standard (The Floor)
- [MUST] Non-Destructive Migrations: Database schemas MUST be evolved in minimal, backward-compatible steps.
- Phase 1: Add new column (nullable).
- Phase 2: Dual-write to old and new.
- Phase 3: Switch read.
- Phase 4: Deprecate old.
- [MUST] Feature Flags: Risky features MUST be wrapped in a specific Feature Flag (LaunchDarkly/Firebase).
- [MUST] Kill Switch: Every external dependency (Payment, SMS) MUST have a configuration-based Kill Switch.
- [MUST] The Rollback: Every deploy MUST have a proven "Undo" button (e.g., revert docker tag).
3. Best Practices (The Path)
- [SHOULD] Canary: Roll out to internal users first.
- [SHOULD] Blue/Green: (Infrastructure permitting) Swap traffic atomically.
5. Version History
| Version |
Date |
Author |
Change |
| 0.1 |
2026-01-25 |
AI |
Draft P0 Standard |
Version History
| Version |
Date |
Author |
Change |
| 0.1.0 |
2026-01-26 |
Antigravity |
Initial Audit & Metadata Injection |