Where Infrastructure Stops ​

Realith must not replace right with infrastructure, and must not replace infrastructure with right.

What infrastructure does ​

Realith infrastructure may:

• hold the object and its version line;
• fix admissible transitions;
• hold canonical current state;
• link objects by relations;
• define contour regimes;
• publish verifiable outcomes;
• make the operator's servicing acts verifiable.

That is its limit.

What infrastructure does not produce by itself ​

Infrastructure does not automatically produce:

• ownership rights;
• legal title;
• binding force for an external addressee;
• judicial recognition;
• automatic emergence of a claim against the operator;
• commercial reconciliation between parties.

All these things require a separate basis.

If this boundary is removed, the architecture will begin to sound stronger than it really is. Canonical current state will then be read as an external title, the operator's service role as ownership, and technical access as right.

For Realith, that is architecturally wrong.

Service also has a boundary ​

The service layer may be strong and verifiable, but it must not silently become a legal basis or a form of ownership.
The detailed boundary between service and ownership is disclosed on the page Why Service Does Not Create Ownership.

infrastructure retains the form of coordination, but does not replace right, contract, and external basis