Why Applicability Is Not Defined by Industry ​

Listing industries creates several false effects:

• the architecture starts to look like a general storefront of markets;
• distinctions between strong and weak scenarios blur;
• the project starts to sound broader than it is actually defined;
• industry language replaces architectural language.

Why industry is a weak criterion ​

Within one and the same industry there may exist both tasks for which Realith is natural and tasks where it is completely unnecessary.

For example, what is decisive is not whether a process belongs to logistics, production, or document flow, but something else:

• whether there is a long-lived object;
• whether there are several independent subjects;
• whether a shared causal line is needed;
• whether a shared canonical current state is required;
• whether everything can honestly be reduced to one platform.

It is these properties, not the name of the industry, that form the architectural criterion.

How to use domain examples correctly ​

Domain examples are admissible, but only as a secondary layer.

First, the abstract class of problems must be fixed. Only after that may one show that certain real zones fit this class well.

That is, an industry example should function as an illustration of the architecture, not as a replacement for the architectural criterion.

If the applicability section is built abstractly, then later it may be extended with:

• pilot directions;
• individual scenarios;
• more domain-specific explanatory pages;
• industry-derived sections.