Lower Canonization Layer ​

Realith must not be read as an ordinary transaction chain to which object fields were added on top.
If the transaction log remains primary, then the object remains only an application description device.

For Realith, that is wrong.

The lower canonization layer is needed so that the network can:

• accept admissible transitions;
• relate them to active object versions;
• retain causal continuity;
• form a verifiable canonical result;
• make that result the basis for the next step of the network.

In other words, this layer works not around “the record as such,” but around the transition of an object version.

The lower canonization layer must not replace:

• the architectural model of the object;
• structure and its properties;
• contour;
• right;
• the operator layer;
• external compatibility.

It does not create the meaning of the object.
It gives that meaning a network form of canonization.

If the lower canonization layer is not separated from the rest of the model, two distortions appear.

The first is when the whole architecture starts reading as a blockchain with an expanded vocabulary.

The second is when the whole logic of canon dissolves into application interpretations and the network ceases to be an autonomous architectural basis.

That is why this layer must remain separate:
it is not primary in meaning, but it is primary with respect to the network fixation of the canon.

The lower canonization layer of Realith is needed so that an admissible transition of a structurally defined object can become part of the shared canon of the network, rather than remain a local record of one party.