Mimere's Default Configuration Is Not Always Correct

Mimere is battle tested. Part of changing the defaults is us rolling the variables and config that we found work best in production back into the code. Another cool thing we have done in Mimere has been introducing a feature lifecycle policy. So now we have a written down policy on how new features are introduced and the experimental feature. Well, we commit to move from experimental features to stable features within six months of time. And will allow us to keep our default configuration up to date with the best practices.