A dark launch deploys new software to production while keeping it hidden from general users. A feature flag separates deployment—the technical act of placing files—from release, the decision to expose a feature. section 13.3.4 section 13.3.4
An enterprise discount, kept under wraps
Ship new discount logic with its flag off, so production continues using the legacy path. Let internal QA testers or audit accounts access the new path by enabling the flag for them. When it is time to release, flip the switch in the management dashboard instead of redeploying. section 13.3.4 section 13.3.4
Figure 13.4 Separation of Concerns: Deployment is the technical operation of placing files on a server; Release is the business decision to expose those files to your users.

The diagram distinguishes deploying files from deciding to expose them to users. section 13.3.4
Dark launches can reduce the pressure to coordinate code delivery with a business launch, but flags need governance:
- Inactive flags can contain stable code while teams continue merging changes. section 13.3.4
- Abandoned toggles become flag debt, a long-term architectural liability. section 13.3.4
