The Object as a Coordination Unit ​

The object is the main addressable unit of coordination in the Realith network.

This is the central primitive of the model. An object is not merely a record about something external and should not be understood as the payload of a message.

What distinguishes the object ​

An object:

• lives longer than a single event;
• has stable identity;
• exists as an instance of a specific structure version;
• has a place in relations;
• exists in an applicable contour context;
• permits only those transitions that are compatible with structure, policy, and permissions.

This is what distinguishes the object from a set of local records about it.

The object is not reducible to data ​

If the object is treated as mere data, the network turns into a layer of messaging or storage. In that case coordination again collapses into external reconstructions.

In Realith, the object is defined not only by content, but also by:

• the structure version;
• the structure properties;
• the active version;
• origin;
• relations;
• contour;
• the causal line;
• admissible actions.

Why the object is the main network unit ​

Realith attempts to solve not the lack of events, but the lack of a shared infrastructural holding of the object between independent participants. That is why the object, rather than the transaction or the event log, must be recognized as the main network unit.

This does not cancel the importance of events, but changes their place: the event becomes a step in the object's line rather than the primary basis of the whole architecture.