The Operator Layer ​

Even if Realith is described as a coordination infrastructure rather than a single platform, that does not remove the need to service the environment.

Someone must provide:

• intake of material;
• storage and replication;
• routing;
• publication of outcomes;
• service diagnostics;
• issuance of receipts;
• limited evidentiary functions.

That is precisely why Realith needs an operator layer.

Without an operator layer, the network easily falls into one of two extremes:

• either abstract theory without operational usefulness;
• or a hidden platform in which the servicing role begins to determine the whole meaning of what is happening.

Realith requires a different form: the service layer must exist, but it must remain a service layer, not a governing one.

What the operator layer does ​

At the current architectural level, it is possible to say that the operator layer supports:

• preservation and holding of material within the profile;
• replication and restoration of the available working surface;
• routing of messages and actions;
• publication of network outcomes;
• limited indexing and diagnostics;
• issuance of receipts for servicing actions;
• transmission or collection of evidentiary material where required by the profile.

This makes the operator layer a necessary element of practical infrastructure.

What must be retained immediately ​

The operator layer is not needed in order to replace:

• the subject of action;
• the substantive meaning of the object;
• the external legal basis;
• inter-subject coordination as such.

It is needed only so that the network can work as an environment.

The same organization may simultaneously be both a subject of action and an operator of part of the network. But architecturally these are still different roles.

If they are not separated, the service layer will begin to mean more than servicing the environment.
For Realith that is inadmissible. The full boundary of the operator's service role is set out in Operator Boundary.