I will grant you the letters from the starving children, but we had a discussion on hip chat today (so it didn't happen) about the kill switch configuration variables and how to name them. We did not burn white smoke, but I will argue that "enabled" is different from "use", especially for something like an API that is used by other subsystems. The background manager has a separate enable/disable API call that continues to track resources but behaves like there are no limits on tokens and locks. In contrast, the "use-background-manager" configuration variable is used by other subsystems to control if they even wish to call the API at all. This is the global "kill switch" that disables full use of the feature. We also observed that there is no consistent naming convention for kill switches or even whether it's "use it" versus "disable it". All of our new features do this a little differently. So, this is what I felt best described what the variable really controlled: "use it", rather than "it's turned off". Maybe we've gone too far with the kill switch concept.

AAE uses "anti_entropy = on | off | debug", for example. If the great spirits of the Cuttlefish have a unified proposal, I will sprinkle food in their tank as thanks.