Object and State in Realith ​

For Realith, it is important to avoid two opposite mistakes.

The first mistake is to read the network as an event-first flow in which the object dissolves into the event log.
The second mistake is to read state as a self-standing thing, almost detached from the object's line.

Both mistakes are wrong.

What is primary ​

In Realith, the object is the main network unit.

This means:

• coordination is built around the object;
• transitions relate to the object's line;
• relations are built between objects;
• structure defines the object's form and behavior.

Where state sits here ​

State does not exist separately from the object as a separate floating entity.

Canonical current state is read through:

• the object;
• the active version;
• the applicable structure version;
• the structure properties;
• relations;
• the contour context;
• previously accepted transitions.

This means that state is not abolished, but nor does it become the primary primitive in place of the object.

If the object dissolves into an abstract reading of state, the network starts to read as a system of “states in general.”

If state dissolves into object rhetoric alone, the main coordination question is lost:

what is currently considered valid for this object line?

Realith must retain both sides at once:

• an object-centered architecture;
• coordination that is sensitive to state.

the object is the main network unit, and canonical current state is read through the line of that object.

What should not be done ​

One should not write as if:

• state precedes object;
• object is state;
• it is enough merely to “have an object,” while state is secondary and unimportant;
• state is simply the last record in the log.