Defined Layer ​

The following already belong to the defined layer:

1. The object as the main network unit ​

Realith is described as an object-centered coordination infrastructure, not as a network in which the transaction is the primary unit.

2. A structurally defined object model ​

Every object exists as an instance of a specific structure version.

3. Structure properties as the source of behavior ​

Admissible transitions, relations, confirmations, contour applicability, and other behavioral regimes are derived from structure properties, rather than from a class label.

4. Canonical current state ​

The network must hold not only the history of events, but also the canonical current state of the object or object line.

5. The causal discipline of transitions ​

A canonical transition cannot be an arbitrary new record. It must have a causal basis.

6. Structure and relations as part of the canon ​

The form of the object and its meaningful relations belong to the canon and must not remain only an external reconstruction.

7. The contour model ​

Contour defines the regime of participation, visibility, isolation, publication, and applicability.

8. The separation of admission, permission, access, right, and claim against the network ​

These layers must not collapse into an ACL system or platform management logic.

9. The limited role of the operator layer ​

The operator services the infrastructural environment, but does not become the owner of content, of right, or of final meaning.

10. The network canonization layer ​

The lower layer must canonize transitions of object versions and the results of epochs, rather than abstract transactions.

11. Consolidation of history without loss of verifiable canon ​

The working surface of the network need not coincide with the full raw past on every node.

12. The EVM layer as an admissible embedded compatibility and execution layer ​

The EVM layer is admissible in the Realith architecture as an embedded compatibility and execution layer, but it does not define object canon.

13. Published State Summary as a mandatory compact verification surface ​

The outcome of an epoch must have a published and verifiable compact surface. At the current stage, Published State Summary is already admissible as the owner concept of such a surface.

14. Compatibility and conformance as a derived boundary discipline ​

Compatibility is already defined as a layer derivative with respect to the internal canon. Gateways, adapters, external interfaces, and the EVM layer may translate, constrain, and export admissible external forms, but they do not define the object, the admissible transition, or canonical current state.

15. Operational and security regimes as derived constraints ​

Deployment modes, node roles, observability limits, and security profiles may differ, but they must not redefine object canon, canonical recognition, or the operator boundary. Their architectural boundary is already defined, even if precise profiles are not yet finalized.

16. Token layer, bridge-path, and ACT as derived layers ​

Token layer may already be asserted as a limited admission layer for those decentralized regimes where it is genuinely needed. Bridge-path may already be read as an explicit transition between external and native token forms, and ACT as a separate layer of accounting for actually engaged resource. None of these layers becomes the source of object canon or of state truth.

The defined layer is already sufficient to speak of Realith as a distinguishable architecture at the A2–A3 level.