Not sure it's a "design pattern", but I would classify that type of behavior as end state configuration or desired state configuration, in the vein of Puppet, Chef or Powershell DSC. Typically those solutions operate at the systems management level, not a business logic level as the question describes, but it's the effectively the same paradigm. Most such tools are usually declarative, but there's no reason the same principles can't be applied in code/scripts, as the question implies.

Not sure it's a "design pattern", but I would classify that type of behavior as end state configuration or desired state configuration, in the vein of Puppet, Chef or Powershell DSC.

Those solutions typically operate at the systems management level, not a business logic level as the question describes, but it's the effectively the same paradigm, and although such tools are usually declarative in nature, the same principles can be applied in procedural code or scripting.