Dark Launch
Updated 2026-09-11
INTRODUCTION
English translation pending.
CORE DEFINITION
A new feature ships but stays invisible to users, running in production to test load, performance, and stability before gradual exposure. It validates technical feasibility in the only environment that truly matters, with real data and real scale, while the public announcement is held back, so a catastrophic failure can never become a public event in the first place.
SCAFFOLDING EFFECT
Reduce cognitive load
- Hides the blast radius: real traffic is exercised while the public interface stays off - Validates in the real environment: production data catches what staging cannot - Decouples release from launch: technical risk and market risk are handled separately
Anchor fast decisions
A feature can only be trusted once it has carried real production load, but a visible failure is expensive in reputation. Wrapping the feature behind a flag exercises the actual code paths with real traffic while users see nothing at all, so technical risk is retired in private and the eventual public launch starts from a position already proven.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- zh.wikipedia.orghttps://zh.wikipedia.org/wiki/%E7%89%B9%E6%80%A7%E5%88%87%E6%8D%A2verified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS