Skip to content
EN FR

Structural and Reserved Dimensions

Documentation status: architecture — see Maturity and evidence.

This section documents Runtime-defined structural positions and reserved accesses of conceptual nodes.

They are not ordinary business fields. Some participate directly in type identity, logical relations, contextual reasoning, or role mapping; others expose computed node metadata through reserved access names.

The current engine sources distinguish four mechanisms that should not be conflated:

  1. structural slots, such as the entity identity position and the distinguished Kind position;
  2. logical-relation structure, where polyadic mapping, source, target, and context have dedicated semantic positions;
  3. reserved extended accesses, such as Self, FormalName, Id, ClassId, SlotCount, and Count;
  4. logical annotations, such as quantifiers, which affect interpretation without becoming ordinary application fields.

Application models should rely on public names and H-Logic semantics rather than on internal numeric slot indexes.