Canon Boundary ​

Compatibility must not replace the internal canon.

What the external environment does not define ​

External systems must not define:

• what counts as an object;
• which structure is admissible;
• which transitions are canonically admissible;
• which canonical current state is recognized as valid.

These belong to the internal architecture of Realith.

What may go outward ​

The following may go outward:

• canonical current state in an admissible form;
• its verifiable representation;
• a limited result sufficient for external reconciliation;
• a compatible interface for work with a contractual or application environment.

But this external layer remains derivative. The compatibility section does not define the network artifact of canonization itself.

Neither an external registry, nor an API, nor a contract surface must silently become the source of object identity or the criterion of canonical recognition.

If this boundary is not retained, false readings arise:

• the external registry begins to look like the source of truth;
• the contract interface begins to look like the main canon;
• the integration format begins to look like the architecture of the network itself.

External compatibility is mandatory for the practical work of Realith, but it must remain subordinate to the internal canon.