shipping-and-launch

Ship with confidence. The goal is not just to deploy — it's to deploy safely, with monitoring in place, a rollback plan ready, and a clear understanding of what success looks like. Every launch should be reversible, observable, and incremental. Ship behind feature flags to decouple deployment from release: Feature flag lifecycle: Rules: Use these thresholds to decide whether to advance, hold, or roll back at each stage: Roll back immediately if: In the first hour after launch: Every deployment needs a rollback plan before it happens: Before deploying: After deploying: - Deploying a feature to production for the first time - Releasing a significant change to users - Migrating data or infrastructure - Opening a beta or early access program - Any deployment that carries risk (all of them) - Every feature flag has an owner and an expiration date - Clean up flags within 2 weeks of full rollout - Don't nest feature flags (creates exponential combinations) - Test both flag states (on and off) in CI - Error rate increases by more than 2x baseline - P95 latency increases by more than 50% - User-reported issues spike - Data integrity issues detected - Security vulnerability discovered - For security pre-launch checks, see references/security-checklist.md - For performance pre-launch checklist, see references/performance-checklist.md - For accessibility verification before launch, see...