Conflict and Canonization ​

In Realith, conflict belongs not to the transport order of message delivery, but to canonization.

This distinction is fundamental. If the network confuses conflict with delivery order, it inevitably hides the problem of state inside technical processing.

When conflict arises ​

Conflict arises when two or more candidates cannot simultaneously occupy the same next canonical position for a given object or line of objects.

The problem is not that the network saw several messages, but that several candidates claim the same next step of the canon.

What must be checked ​

To distinguish an ordinary transition from a conflict, the network must be able to check:

• the causal basis;
• the applicability of structure;
• the applicability of admissibility rules;
• the applicability of contour;
• the compatibility of candidate versions with one another;
• the sufficiency of recognition basis.

A signature by itself does not make a transition canonical and does not resolve a conflict automatically.

Possible outcomes ​

At the conceptual level, it is enough to fix that every candidate transition must receive an explicit outcome. It may be:

• accepted as the next canonical step;
• rejected as conflicting;
• preserved as a conflict branch without the status of current canon;
• used as input for a separate conflict-resolution action that creates a new canonical version.

What must not count as an admissible resolution ​

Conflict must not be resolved by:

• silent overwrite;
• accidental delivery order;
• local queue behavior;
• a private application heuristic.

All such outcomes destroy the shared basis of the canon and return the system to a set of local readings.

Why this is tied to current state ​

Canonical current state is possible only where conflict is processed explicitly. Otherwise different participants will have different answers to the question of which object version is current.

That is why conflict and canonization are not a peripheral topic, but a mandatory element of state logic itself.

What is not yet finalized ​

At the current stage of the project, it is admissible to fix only architectural regimes:

• a strict linear regime;
• a regime that accounts for conflict branches;
• a regime that allows later merging.

The final low-level choice of regime belongs to a later and more specification-grade layer.