Object Canon Invariants ​

The minimal invariants of Realith must remain true under any reading scenario.

1. Object primacy invariant ​

The coordination unit is the object and its line, not merely a set of independent events.

2. Structure-boundedness invariant ​

The object does not exist outside the applicable structure version.
A transition cannot be considered admissible without a link to the applicable structure and its properties.

3. Explicit recognition invariant ​

A canonical position does not arise silently, but only through a distinguishable recognition basis.

4. No silent overwrite invariant ​

Conflict cannot be considered resolved by accidental delivery order, silent overwrite, or a private application heuristic.

5. Contour non-collapse invariant ​

Contour is a strong boundary of the environment.
It must not silently collapse into simple visibility and must not quietly lose semantic force.

6. Service/right separation invariant ​

A right to an object and a claim against the network are not identical.
A right to the object does not entail an unconditional duty of the network to service any service profile.

7. Compatibility subordination invariant ​

External compatibility, the execution layer, and bridge-path do not redefine the internal object canon.

If these invariants are violated, Realith begins to read not as an autonomous coordination infrastructure, but as a private process, permission system, or event log with an expanded vocabulary.