Good point. Maybe I should separate the state elsewhere. The idea was that the configuration is provided via context, and the same config object would then build its state upon examining the account policy. 

Maybe it would make better sense if the `build` was to actually return some sort of a result object that only holds the result of a retrieved configuration? Would be easier to separate state from others.