Configuration Inheritance Needs a Reason
Defaults are not magic. They should say where they came from.
When a customer sees a pricing strategy or permission rule, the system should explain whether it is local, inherited, or platform default.
Configuration inheritance is useful and dangerous. It is useful because teams do not have to repeat the same rule. It is dangerous because users often see the result without knowing why it appeared.
HotelByte configuration should not be only a final value. Effective configuration is a conclusion with provenance: what was overridden locally, what came from an ancestor, what came from the platform default, and which fields were intentionally empty.
That makes the interface more honest and debugging faster. When a strategy looks wrong, the team should not first guess who set it. The system should say where it came from.