Skip to content

The Realith Subject

A subject is the bearer of a distinguishable identity and the source of action in the Realith model.

This is one of the basic primitives of the architecture. A subject is not reducible to an interface user role and should not be silently replaced with the word “account” when the architectural model is what is meant.

What the subject does

A subject may:

  • publish structures;
  • create an object as an instance of a structure;
  • initiate a transition;
  • receive or issue permission;
  • act within a given contour.

In other words, the subject is what participates in coordination as a recognizable initiator of action.

What the subject is not

A subject is not the same as:

  • an operator;
  • a node;
  • a contour;
  • an object.

An operator services the infrastructural environment. A node performs a network function. A contour defines an environmental regime. An object is the addressable unit of coordination. A subject must not be silently collapsed into any of these layers.

Why this distinction matters

If subject and operator are collapsed, the infrastructure starts reading as a system of private control. If subject and object are collapsed, the distinction between who acts and what the action is performed upon disappears. If the subject is reduced to an internal application role, the model ceases to be inter-subject.

For that reason, the subject in Realith must be retained as a separate primitive of the model.

Boundary of the page

This text describes only the subject as an architectural unit. The order of admissible actions, the limits of participation, and visibility must be disclosed separately through contour, permission, admission, access, and right.