E.24.UK:4.2.1 - Accepted Root Settlement For U.Relation
FPF has already admitted U.Relation; project users do not repeat this ontology decision. The root kind classifies individuable obtaining relation occurrences. A direct relation can obtain before a system explicitly individuates, names, describes, or references one occurrence, but admission under this root requires the direct relation pattern to supply an occurrence-identity rule.
| Admission condition | U.Relation settlement by value |
|---|---|
| governed individuals | the extent contains exactly those obtaining relation occurrences for which a direct relation pattern supplies an occurrence-identity rule |
| stable identity or membership | A.6.REL supplies the common discipline, and each exact direct relation pattern states how one occurrence is reidentified and distinguished from another. Participant identity, maximal continuous obtaining, constituting work, or another domain discriminator is used only when that defining passage selects it. |
| reviewable witness | A.6.REL supplies the common occurrence discipline; the direct relation pattern supplies relation-participant meanings, the obtaining condition, and the relation-specific identity rule |
| action-facing need | comparisons, qualifications, change claims, nested relations, and receiving direct relations can depend on one occurrence being distinguishable from another |
| non-duplication | relation-kind-specific assertions do not provide one common kind for a relation occurrence used as the EntityOfConcern of an episteme or as a participant of another direct relation |
| direct governing locus | A.6.REL governs the root occurrence distinction and progressive individuation; each direct relation pattern defines or constrains whether its relation obtains and how its occurrences are identified |
| shared E.24-family settlement | E24UK-AR-URELATION-R11-01 is the accepted reconstructed root result. This by-value settlement records primary subject kind U.Relation, A.6.REL plus each needed direct relation pattern as the minimal rule set, named receiving reliance, and the non-use boundary below. IdentityBearingDirectRelationIfSelected = none: admission invents no relation among the U.Relation kind, a relation kind, or another relation occurrence. Because this result predates separate output identifiers, the registry does not fabricate an OnticSettlementResult suffix; reopen it into the current shared schema if a receiving use requires a separately identified ontic output. |
| by-value dependence | A.1 part-relation admission, relation-occurrence descriptions, and direct relations whose participant kind admits U.Relation rely on this root by value |
The admission does not force explicit materialization of every obtaining relation. Ordinary engineering prose can stop at the direct relation sentence. A system performs explicit-individuation work only when a named receiving episteme, direct relation, or operation-application assertion depends on occurrence identity. The accepted Tech label U.Relation is governed separately through its F.18 NameCard; the label does not establish the extent.
Apply the positive extent rule before classifying a nearby object. Predicate content is a rule; an assertion or occurrence description is a C.2.1 episteme; a designator or reference stays under F.18; a reusable form stays under E.24.PUB; and a row, graph edge, or diagram element stays under C.29. None is the obtaining occurrence. Connect it to the occurrence only through its explicit assertion, description, designation, reference, publication, or representation relation.
The rule is not lexical. An individuable publication-relation occurrence is itself a U.Relation when E.24.PUB defines that relation and states its obtaining and identity conditions. A row that represents the occurrence remains a representation element. Reidentify the current object by the rule that defines or tests it instead of inferring membership from words such as relation, edge, link, record, or reference.