Operator Boundary

What the operator does

At the architectural level, the operator may honestly be responsible for:

• the fact of intake of material;
• storage and replication within the declared profile;
• publication of outcomes of the network layer;
• compliance with the declared observability regime;
• issuance of verifiable receipts;
• availability of the service functions it explicitly services.

This is a real and strong role.

What does not follow from it

From the fact of servicing, the following must not automatically follow:

• ownership of the object;
• a right to the object's content;
• a right to final subject-matter interpretation;
• a right to replace an external contract or legal basis;
• a right to demand disclosure of closed content without an explicit basis;
• an unconditional claim against the network beyond the declared service profile.

Otherwise the service layer turns into a hidden center of power.

If the operator begins to read as the bearer of final meaning, Realith loses its own architectural task.

The network then becomes again:

• either a platform of one owner;
• or a private service with more complicated terminology;
• or a system where canon depends not on the model, but on whoever holds the infrastructure.

A right to the object and a claim against the network are not the same

Even if a subject has a right to an object or to its content, it does not follow that it has an automatic and unconditional demand against any operator to provide:

• any volume of storage;
• any form of computation;
• any depth of archive;
• any level of availability;
• any form of evidentiary surface.

This is a separate layer, and it must not be hidden inside the architecture of canon itself.

Main formula

> the operator supports the environment, but does not become the owner of content, the source of final meaning, or the automatic basis of right.

And an additional formula:

> a right to the object is not identical to claim against the network.