System Structure Properties ​

Structure properties are system-significant features that define how an object of a given structure may exist, change, relate, be confirmed, and be recognized in the network.

If structure answers the question of the form in which an object is admissible, then structure properties answer the question of how that object may behave in the model.

What structure properties define ​

Through structure properties, the network distinguishes, for example:

• whether the object is unique or interchangeable within a kind;
• whether it has quantitative measure;
• whether it permits division and aggregation;
• whether it is composite;
• whether it requires confirmations;
• whether it may be derived;
• whether it depends on a specific contour;
• whether it permits limited observability;
• whether it requires joint action by several subjects.

If the behavior of an object is explained only by a class label or by the private logic of an application, Realith loses universality. In that case the network turns again into an application platform where the true meaning of the object lives outside the architecture.

Structure properties make it possible to retain a different position: the behavior of the object is expressed through network-recognizable features of the structure itself. This is how a stable Object Mode is read in the architecture, that is, the character of the object's admissible behavior.

Examples of property groups ​

At the current level, it is sufficient to retain the following groups:

• identity properties;
• quantitiveness properties;
• divisibility and aggregability properties;
• compositeness properties;
• derivation properties;
• confirmability properties;
• transition properties;
• restriction and binding properties;
• contour applicability properties;
• observability properties;
• external-binding properties;
• subject-action properties.

This is not an application catalog of the domain world, but a basic architectural vocabulary of behavior.

Important boundary ​

Structure properties must not be replaced by arbitrary user attributes. User-defined features are possible, but they cannot destroy the meaning of system structure properties and cannot retroactively rewrite an already published structure version.