What is the best practice naming convention for business rules that handle inserting records without a domain?

The best practice naming convention that includes "Domain - Default" is appropriate because it effectively communicates the functionality and intended behavior of the business rule. When a business rule is designed to insert records without a specific domain, indicating "Default" in the name helps to clarify that this rule does not associate with any specific domain context but is meant to be a general or default implementation applicable across multiple scenarios.

Using a term such as "Domain - Default" provides a clear indicator to other developers and system administrators that the rule is a fallback option for cases where no domain is specified, ensuring better understandability and maintenance of the system. This practice aligns with the principle of self-explanatory naming conventions that enhance clarity within the codebase.

In contrast, naming conventions like "No Domain," "Global Scope," or starting with "Business Rule" may not provide the same level of clarity regarding the rule's default behavior related to domain context. While these options may still communicate aspects of the rule, they do not directly indicate the rule's specific purpose of handling records when there is no defined domain context in the same clear way as "Domain - Default" does.