> Anything that is defined in the top-level would be considered Dancer's
> core property.
>
> This would allow for specific checks, and could protect users from using
> a key that would become Dancer-native in future versions.
>
> I like that idea, but my main concern here is backward-compat, as I said...

Personally, I like the simplicity of being able to shove your app's own
config at the top level of the config file, and just say e.g.
config->{foo} in your code.