What Exactly the Network Canonizes ​

For Realith, the object of canonization must not read as “transaction in general” or “any message that arrived.”

Not everything is canonized indiscriminately ​

The network must not automatically canonize:

• any external message;
• any local data mutation;
• any signed record;
• any delivery order.

A signature, delivery, and a record by themselves do not yet constitute canon.

What must enter the canon ​

At the current level of architectural representation, the network must fix as canon the following:

1. an admissible transition;
2. the active version of the object from which it is built;
3. the new version of the object, if the transition is accepted;
4. the link of the transition to the applicable structure;
5. the link of the result to canonical current state;
6. the epoch outcome, if the network has already reached the step of period fixation.

This is what constitutes the object of network canonization.

The boundary of this list is important:

the network does not invent the object's state anew and does not create its meaning from nothing; it canonizes what is already distinguishable at the level of admissible transition, active version, and canonical current state.

If the network fixes only the order of messages, further reading again becomes local reconstruction.

If the network fixes an admissible transition of an object version, it retains not only history but also the basis for the next canonical step.

What does not follow from this ​

From the fact that the network fixes canon it does not follow that it must disclose:

• all internal content;
• the entire past array in an equally working form;
• all application details for any observer.

The canon must be verifiable.
But its verifiability is not equal to total openness of all network content.

The Realith network fixes not abstract transactions, but admissible transitions of versions of structurally defined objects and the results of their canonization.