Object Version and Transition ​

In Realith, the object must be read not as an immobile entity, but as a line of distinguishable versions between which admissible transitions are possible.

This is how the network holds causal continuity without returning to a “last write wins” logic.

Object version ​

An object version is the canonically distinguishable form of a given object within its causal line.

Through the version, the network must be able to answer:

• which version is currently active;
• on which version the next transition is built;
• which version has been extinguished;
• which version constitutes the current basis of the canon.

What a transition is ​

A transition is an admissible change in the line of the object.

It may:

• create an object as an instance of a structure;
• create a new version of an existing object;
• generate a derived object;
• change relations;
• formalize conflict resolution;
• change the current canonical position of the object.

Why transition is constrained by structure ​

A transition must not be understood as an arbitrary change of data. It is always bound to a specific structure version, its properties, the applicable policy, confirmation requirements, and the limits of the contour.

Without this basis, the transition again starts to read as an ordinary message or transaction without architectural discipline.

Causal basis ​

A new transition must not arise without a causal basis. If this is not the primary creation of the object, the network must understand from which object version and from which prior canonical basis the next step is built.

This is what keeps the object's line continuous and verifiable.

Boundary of the section ​

This page fixes the basic triad “object – version – transition.” The full logic of active version, canonical current state, conflicts, and further canonization is developed in the next section of the corpus.