Node Roles ​

A node in Realith must not be described only as a “network server.” What matters more is which logically distinguishable function it performs.

That is precisely what Node Role expresses.

What a node role defines ​

A node role defines:

• the service or verification function;
• the volume of observability;
• the limit of responsibility;
• operational constraints.

A node role does not define:

• ownership of content;
• final subject-matter interpretation of the object;
• monopoly over canon.

Basic roles ​

Gateway ​

A gateway links external interfaces to canonical network actions and outputs verifiable results outward.

Verifier Node ​

Such a node verifies signatures, causal basis, structure applicability, policy constraints, and admissibility of the next step.

Storage and Replication Node ​

It retains and distributes the material needed for the stability of the environment. The mere fact of storage does not create rights to content.

Archive Node ​

An Archive Node retains a deeper historical surface and supports restoration of the past beyond the ordinary working surface of the network.

Light Verifier ​

A Light Verifier verifies the current canon through published network outcomes and the evidentiary surface, without fully reproducing history locally.

Architecturally, what matters is not a list of machines, but the distinction between functions.

The same physical installation may combine several roles. Conversely, one role may be distributed among several nodes.

Detailed profiles of routing, key management, compatible layer execution, and internal indexing belong to a later level of specification.

At the current stage, it is enough to fix only the basic roles and their limits.