Design Patterns vs. Blueprints in the BPMN Context

What do the two terms mean in the software engineering context? The research on «blueprint» did not result in an established definition. «Blueprint» just refers to a plan or design. The definition of "design pattern" is somewhat more specific (from the recommended Wikipedia article):

In software engineering, a design pattern describes a relatively small, well-defined aspect (i.e. functionality) of a computer program in terms of how to write the code.

Below are the definitions in the BPMN context, derived from the research and the exchange with Camunda.

Blueprints are reusable BPMN processes. These can be either

1. prefabricated solutions (e.g., a reservation process) or
2. sub-processes that are called by other processes (e.g., an approval process).

Ideally, the blueprint is only controlled via variables so that no customization is necessary when using it.

A design pattern shows how a specific modeling problem can be solved reliably. It is a (preferably) independent solution concept. This independence allows different design patterns to be combined with each other as desired. Examples of this would be

1. solutions to specific problems, such as the Updatable Timer Pattern, which describes how timers in processes can be made modifiable or
2. solutions to conceptual challenges, e.g., methods for breaking down a process into comprehensible components

The main difference is the concrete BPMN process and everything associated with it. Blueprints always contain a BPMN process and can theoretically be used as black boxes (you only need to understand the inputs and outputs, but not the process itself). Design patterns, on the other hand, are on a conceptual level, have no BPMN process (at most they are used for explanation) and without a clear understanding, they are useless. The way a design pattern is used is the same for all processes, but the implementation or the resulting process can look different each time.

Blueprints can include design patterns, but design patterns cannot include blueprints.

Whether blueprint or design pattern, the most important thing is to understand the context in which they are used.

Otherwise, a design pattern can quickly degrade into an antipattern (opposite).