Skip to content
EN FR

Structural and Reserved Dimensions

Documentation status: architecture — see Maturity and evidence.

The conceptual Runtime gives a small set of positions and access names special semantics. They form part of the structural geometry of a conceptual node and of logical relations; they are not a generic metadata bag.

A useful mental model is:

conceptual node
  structural identity / participant slots
  distinguished Kind semantics
  reserved computed accesses

logical relation
  polyadic role map
  source
  target
  context
  relation attributes such as weight/order metadata

The distinction matters because an ordinary business role participates in the modeled domain, while a reserved dimension can change how the Runtime interprets identity, subtype relations, implication, comparability, or role alignment.

Core distinctions

  • me, identity, and Self explains why entity identity and self-access are separate mechanisms.
  • Context describes context as an input to logical interpretation, not merely request-local state.
  • Kind describes the distinguished type/kind position used by matching and subtype-aware evaluation.
  • Polyadic map describes explicit role alignment used throughout polyadic reasoning.
  • Extended reserved accesses documents computed node metadata exposed through reserved names.
  • Quantifier covers logical range semantics.

Public-contract rule

Do not copy internal numeric indexes into application models. The stable concepts are the public names and semantics. Internal storage positions are implementation details and may evolve independently of application-level syntax.