A.6.5 - Relation-Declaration Slot Discipline - SlotKind, ValueKind, RefKind, and participant-designation discipline
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
A.6.5:1 - Problem frame
Plain name. Relation-declaration slot discipline.
Use this when. Use this pattern after the direct relation kind has been recovered and a reusable typed declaration of its participants is current for another assertion, comparison, substitution, or reference use. Typical triggers are one relation declaration reused across patterns, another relation referring to an explicitly individuated occurrence, or an engineer checking a proposed replacement participant against the declared ValueKind.
Primary working reader and concern. The intended reader is an engineer making one relation declaration reusable.
Primary EntityOfConcern. One SlotSpec declaration in one RelationSignature.
First useful move. Write the readable relation sentence, identify the relation kind and relation-participant meanings, and name where its predicate, applicability and occurrence-identity rule are defined. For every relation-participant meaning whose reusable typed declaration is current, add one SlotSpec to the RelationSignature, using the compact declaration notation SlotSpec = <SlotKind, ValueKind, refMode>. refMode states how an assertion or relation-occurrence description episteme carrying a relation-participant designation denotes the entity named under that meaning. When refMode is a RefKind, the reference retains that RefKind and its referent retains the declared ValueKind; the SlotSpec remains declaration content. If the direct relation or its relation obtaining predicate is still unclear, stop and use A.6.P or A.6.RSIR; declaration notation cannot recover a missing ontology.
First-minute result. For Robot_7 is assigned to InspectorSystemRole for this inspection shift, start from an independently defined species under U.SystemRoleAssignment, here illustrated as InspectionShiftAssignment, and use its predicate and case facts to determine whether a shift occurrence obtains. When reusable participant typing is needed, give HolderSystemSlot the value kind U.System and entity-reference mode; give AssignedSystemRoleKindSlot the value domain InspectorSystemRoleKindDomain and ByValue designation mode. Add another participant only when it changes the predicate or occurrence identity. An assertion designates the occurrence’s participants and states its assignmentInterval separately. Stop there unless later work must substitute a participant, distinguish this assignment episode from another, or test an A.2.5 state condition.
What goes wrong if missed. In the readable sentence Robot_7 is assigned to InspectorSystemRole, the holder system, the system-role kind, each declaration-local SlotKind, and each participant designation carried by an assertion episteme can collapse into one word such as role or holder. A later claim then cannot tell what may be substituted, what retains identity, or whether it refers to a system, a system-role kind, an assignment occurrence, an assignment-state relation, or an assertion about either occurrence.
What this buys. Engineers retain a readable relation sentence while its load-bearing uses gain participant typing, unambiguous reference use, and a route to the definitions or constraints for predicate truth and occurrence identity.
Not this pattern when. Use A.6.P or A.6.RSIR first while the relation kind or its participants remain unresolved. Use A.6.REL for relation-occurrence identity, A.6.0 for the containing U.Signature, C.2.1 for an assertion or description, and C.3 for a local kind needed by membership, substitution, typed quantification, or subkind use; use C.3.2 for its declaration, membership judgment, or optional extension. In every other case, find the direct relation’s accepted definition before applying this slot discipline.
The following objects meet at this boundary and remain distinct:
- an obtaining relation occurrence in the world;
- the direct relation kind and its predicate;
- a
RelationSignatureepisteme whose content includes SlotSpecs corresponding to the direct relation’s relation-participant meanings and restates its predicate, applicability, and identity rule for reuse; - a
SlotSpeccontaining the declaration-local SlotKind name for one relation-participant meaning, its actual-participant ValueKind, and its designation mode; - an assertion or other episteme affirming, denying, modalizing or leaving unresolved whether the predicate holds.
Use the A.6.REL relation-object architecture. A relation-participant meaning specifies one domain contribution to the obtaining predicate. An actual relation participant is an entity participating in an obtaining occurrence under that meaning while retaining its own kind. A SlotSpec is declaration content corresponding to the participant meaning. A relation-participant designation is a value or reference carried by an assertion or description to designate the entity in that participant meaning. The entity is an actual participant in an obtaining occurrence only if the predicate holds; correct designation also serves negative or unresolved claims without establishing participation. Source-specific vocabulary retains its meaning until the applicable declaration or representation correspondence relates it to the FPF object.
A RelationSignature is a declaration episteme whose content includes SlotSpecs for reusable relation semantics. A world-side relation obtains under its direct predicate independently of those epistemes, and its own rule supplies any needed occurrence identity.
In Tech register, SlotKind is the declaration-local kind by which one RelationSignature distinguishes a relation-participant meaning. World-side relation prose names the meaning and actual participant directly; the relation occurrence contains no SlotKind. In an assertion or relation-occurrence description episteme, the corresponding SlotSpec distinguishes a relation-participant designation carried by value or by a reference of the declared RefKind. External representation elements retain their source-specific names. A declared correspondence must relate such an element to a named SlotSpec before an FPF relation claim can reuse it.
A.6.5:2 - Problem
The engineering problem appears when the same relation declaration is used in another claim, substitution, or comparison. A ValueKind that covers participants for which the predicate has different meanings makes typed reuse unsound. A reference value leaves its referent kind unstated. A designator for an actual participant is promoted into a U-kind. A role value is confused with the system that holds it. A verb-shaped predicate is read as proof that the relation is work, a method, a transformation, or an acting holon.
These errors change which substitutions are valid, which object a later claim may reference, what makes the relation obtain, and which definition or constraint the repair must preserve.
A.6.5:3 - Forces
| Force | Tension |
|---|---|
| Readability and reuse | The first relation sentence stays simple, while later claims may need typed SlotSpecs. |
| Local SlotKind and durable participant | A SlotKind is local to one declaration, while the relation participant keeps the identity and kind defined elsewhere. |
| Range and open-ended ontology | A ValueKind needs enough precision for the predicate without forcing every participant into a newly minted U-kind. |
| Embedded value and stable reference | An assertion or description may designate an entity by value or reference. When the relation obtains, that entity participates directly; the designation mode does not change the participant. |
| Logical form and constructive grounding | Predicate and slot discipline help review a relation, while FPF still needs grounded participants and direct rules for obtaining and occurrence identity. |
| Grammatical verb and ontological kind | A verb can express a relation predicate without turning the relation into work, method, transformation, agency, or a holon. |
A.6.5:4 - Solution
Apply relation-declaration slot discipline only after the direct relation and its relation-participant meanings have been recovered. Give every relation-participant meaning needed by the current typed use one complete SlotSpec in the RelationSignature. Let the direct-relation definition supply the obtaining predicate and occurrence-identity rule. Follow the A.6.REL minimum-current-object rule: a later use adds only its current object and the direct relation to an already recoverable object rather than restating the complete relation-object architecture.
A.6.5:4.0 - Ontological status of the discipline
A.6.5 constrains one SlotSpec declaration belonging to one RelationSignature. Operation argument and result declarations remain under A.6.1; mathematical operands and their order remain representation elements; use C.29 when that representation is used as a declared mathematical lens.
A.15.3 may cite one SlotSpec as the target of a planned participant designation inside a U.WorkPlan. That citation does not fill the SlotSpec, extend SlotSpec to another description family, make the planned designation an actual participant, or make the direct relation obtain. Planned operation arguments and results instead cite their A.6.1 declarations. Only a declaration-local participant specification inside one RelationSignature is a SlotSpec. Method-description, plan, work, evaluation, card, schema, and record fields retain the kinds and declaration rules supplied by their defining patterns. A field that receives relation semantics follows the applicable declaration or representation correspondence route in §4.2; the field, SlotSpec, designation, and actual participant remain distinct.
A.6.5:4.1 - Use each object’s defining rules
| Object or claim | Defining or constraining content | What A.6.5 contributes |
|---|---|---|
| Direct relation kind, relation-participant meanings, and relation obtaining predicate | the direct-relation definition | no replacement; A.6.5 supplies the SlotSpec discipline for a compatible RelationSignature |
| Relation occurrence and identity | the direct-relation definition and A.6.REL | participant ValueKinds; refMode applies only to relation-participant designations in an assertion or relation-occurrence description episteme |
RelationSignature declaration | A.6.0 defines the containing signature | complete SlotSpec declarations inside its vocabulary item |
| Assertion that a predicate obtains | C.2.1 defines assertion content; the direct claim pattern defines that claim family | no new assertion kind; the assertion can name relation participants |
| Local derived kind of participants | C.3 and C.3.1 define the kind, subkind, and continuity questions; C.3.2 supplies its KindSignature, membership judgment, and optional extension | when a RelationSignature is needed, its SlotSpec uses the declared participant ValueKind while the SlotKind remains local to that declaration |
| Planned participant designation | A.15.2 and A.15.3 define the planned claim | one SlotSpec may be cited as the target of a planned filling; A.6.5 contributes only the declaration-local SlotKind, ValueKind, and refMode discipline and establishes neither the plan claim nor actual participation |
None of these objects gets its identity or truth condition from A.6.5. A.6.5 supplies the participant-declaration and designation-typing discipline at their shared boundary.
A.6.5:4.2 - Declare one complete SlotSpec for each relation-participant meaning needed by typed reuse
The following code block is a compact representation of a declaration. Its assignment mark, angle brackets, order, and alternatives are notation elements.
SlotSpec := <SlotKind, ValueKind, refMode>
refMode := ByValue | RefKind
SlotKind is the declaration-local kind by which one RelationSignature distinguishes one relation-participant meaning. HolderSystemSlot and AssignedSystemRoleKindSlot are different SlotKinds inside the InspectionShiftAssignment declaration even when a receiving assertion designates the holder by reference and the assigned system-role kind by value. A receiving semantic field is covered by an explicit declaration against one SlotSpec. An external or independently named representation field keeps its source name and requires an explicit correspondence to the declared SlotSpec; use C.29 when that correspondence is part of a declared mathematical-lens use. Neither route makes the field a SlotSpec or the designation an actual participant. A mathematical operand or numbered argument belongs to its mathematical representation, not to the relation declaration.
ValueKind is the world-side kind admitted for an entity designated under the declared participant meaning. Recover it from the accepted declaration that defines that kind. The declaration may settle a durable U-kind, a current C.3 kind, a Concept-Set entry, or an imported sort whose bridge states the corresponding FPF kind. If one proposed ValueKind hides several kinds for which the predicate has different meaning, recover their common kind or split the relation kind. A prose list of alternatives does neither.
RefKind is the kind of reference used when a named-use assertion or relation-occurrence description episteme carries a relation-participant designation by reference. A system applying the declared resolution Method obtains a referent of the declared ValueKind; resolution alone does not establish participation. U.EntityRef, U.HolonRef, and U.EpistemeRef are examples only where their RefKind declarations and admission predicates apply. SelectedStructureReference uses the bounded declaration and resolution criterion in A.22:4.9. The shorthand byRef is usable in a compact local sketch only when the RefKind is declared next to that sketch; it is not a complete refMode by itself.
ByValue means that an assertion or description carries a value as its participant designation. By reference means that it carries a reference value of the declared RefKind. In either case, check the designated entity against ValueKind separately from checking whether the predicate holds. A reference retains its RefKind, its referent retains its own kind, the SlotSpec remains declaration content, and any obtaining occurrence retains its direct identity.
Naming and source-token repair. Use ...Slot for a declaration-local SlotKind inside one RelationSignature. Use ...Ref for a reference kind or value, distinguishing that reference from its referent. For example, HolderSystemSlot is the SlotKind, U.System is the participant ValueKind, and Robot_7_Ref : U.EntityRef designates Robot_7 : U.System. If a relation independently admits a reference itself as a participant, retain that reference’s kind and do not substitute its referent. Split a source word such as holder when it conflates these meanings. A source field keeps its own name and is related to the declared SlotSpec through the applicable declaration or representation correspondence.
A.6.5:4.3 - Apply the well-formedness constraints
A6.5-S1 CompleteSlotSpec:
every relation-participant meaning needed by reusable typed use has one SlotSpec
with exactly one SlotKind, one ValueKind, and one refMode.
A6.5-S2 LocalSlotKind:
SlotKind is interpreted only inside the RelationSignature that
contains the corresponding SlotSpec.
A6.5-S3 ExactParticipantKind:
each entity designated under a declared participant meaning has the declared ValueKind;
actual participation additionally requires the direct predicate to obtain.
A C.3 kind ordered by an explicit U.SubkindOf relation may narrow
that range only when typed membership or substitution is current.
A6.5-S4 HonestReference:
when refMode is a RefKind, the receiving assertion or description carries
a reference of that RefKind whose resolution denotes an entity
of the declared ValueKind, whether or not the predicate holds. The relation itself does not store it.
A6.5-S5 DirectPredicateDefinition:
the identified direct-relation definition states the predicate,
applicability, and the direct occurrence-identity rule.
A6.5-S6 NoHiddenUnion:
one ValueKind does not hide participant kinds for which the direct
predicate has different semantics. Recover one common ValueKind or split the relation kind.
A6.5-S7 RepresentationBoundary:
a representation or publication form does not become the
world-side participant or relation occurrence by form.
A system performing typed substitution keeps the SlotSpec fixed, resolves the designation under its declared scheme when refMode is a RefKind, and checks the designated entity against the ValueKind; the designation must still satisfy the declared refMode and, when applicable, RefKind. A system performing retargeting changes a reference value in an assertion or description while preserving SlotKind, ValueKind, and RefKind. Neither designation operation by itself changes a world-side participant or makes the direct predicate true. The identified direct-relation definition supplies that predicate and identity rule; the current case must supply the relevant facts or constituting history. A system applies the direct obtaining test to those facts or constituting history, and a claim-bearing episteme records the warranted affirmative or negative claim, or leaves the factual question unresolved. Only when an explicit reliance judgment is current does A.10 or the receiving evaluation separately record supported, refuted, or unresolved reliance. Type compatibility and assertion form do not by themselves establish obtaining or occurrence identity. Evidence supporting the case conclusion and any constitutive contribution are governed separately by the relevant evidence and direct-relation rules.
A.6.5:4.4 - Distinguish predicate grammar from holonhood and agency
A relation predicate is often written as a verb phrase: a system is assigned to a system-role kind, a part belongs to a whole, one claim supports another, or one occurrence results from Work. The grammatical verb only helps express the predicate. It does not settle the ontological kind of what the expression denotes.
Use the following definitions for that distinction:
A.15.1andA.3.1supply the constructive assembly, composition, identity, and meta-holon-transition conditions that admitU.WorkandU.Methodas holon kinds.U.Transformationis instead a root U-kind underA.3.4for one independently grounded actual bounded change. Verb-shaped wording proves neither classification.- One context-local system-role kind is admitted under
C.3and described throughA.2; it is neither a holon nor an assignment. An admittedU.Systemparticipates as holder in an assignment occurrence whose species is declared underU.SystemRoleAssignment. U.Relationis an individuable obtaining relation occurrence underA.6.REL. A SlotSpec does not give it constructive parthood or meta-holon transition and does not admit it as a holon.- Only an admitted
U.Systemacts. A system may be classified by a local system-role kind and may participate as holder in an obtainingU.SystemRoleAssignment; neither the kind nor the assignment acts. Work is performed, a Method is applied in Work, and a transformation occurs or is carried out.
When one word could denote a relation predicate or a holon occurrence, first ground the participants and ask what obtaining or occurrence identity rule the receiving claim needs. Then find its definition. Do not decide by part of speech.
Predicate grammar also decides neither claim polarity nor reliance. An ordinary relational assertion states affirmative or negative polarity for the direct predicate; a forecast, scenario, counterfactual, permission, or other claim family retains the rules that define that claim family. Only when an explicit reliance judgment is current for the declared use does A.10 or the receiving evaluation separately state supported, refuted, or unresolved reliance. Those claim-side distinctions do not by themselves make the world-side relation obtain; any constitutive effect follows the direct relation’s rule.
A.6.5:4.4a - Keep ordinary predicate parameters outside SlotSpec
A reusable predicate definition may be an ordinary A.6.0 U.Signature without being a RelationSignature. Its semantic parameters are not SlotSpecs unless an independently admitted direct relation kind has world-side participant meanings that a typed receiver must reuse. In particular, the dependentContent and baseContent parameters of RuleContentBasisFindingDefinition@R7 are NonemptyClaimContent values (C.2.1:4.1.2) in a predicate declaration, identified by their interpreted claims and selected semantic relations. They do not name relation participants, SlotKinds, occurrence positions, or a new relation kind.
A C.2.1 assertion of derivedUsingRuleContent or evaluatedAgainstRuleContent designates those values and its derivation or criterion-selection claim. A record or formula may represent the parameters; use C.29 when that representation is used as a declared mathematical lens. Table shape does not turn the parameters into SlotSpecs. If later work proposes a relation kind, it needs an independent A.6.RCD account of participant meanings, obtaining, applicability and a direct occurrence-identity rule. E.24 governs a proposed framework pattern, and E.24.UK applies when a new U-kind is proposed; the predicate declaration supplies none by implication.
A.6.5:4.5 - Use progressive elaboration
Start with the lightest object that supports the named engineering use. The branch diagram maps three independent receiving-use thresholds that share one recovered direct relation; none is a prerequisite for either of the others:
readable assertion of the recovered direct relation
+-- reusable RelationSignature with SlotSpecs, when the receiving use needs reusable participant typing
+-- explicit occurrence individuation, when a named claim or direct relation relies on occurrence identity
+-- relation-occurrence description episteme, when a receiving episteme describes the occurrence
+-- stable relation-occurrence reference, when a receiving episteme contains a designation of it
+-- local C.3 kind under C.3.2, when membership, substitution, quantification, or subkind use is current
The branches are independent thresholds; explicit occurrence individuation does not require a RelationSignature. The direct-relation definition supplies the obtaining predicate and direct occurrence-identity rule, while current case facts or constituting history must satisfy the predicate before that rule distinguishes an occurrence.
The local-kind branch does not turn every participant qualification into a kind. It is justified only when membership, substitution, quantification, or U.SubkindOf reasoning will be performed. C.3.2 supplies the KindSignature, pre-judgment admissibility, membership judgment, and any separately needed extension; a local-kind judgment does not require a RelationSignature or a materialized extension.
A.6.5:4.6 - Dispatch the world-side fact, claim, and local kind
| Current reading | Object or claim | Next pattern |
|---|---|---|
| Relevant current-case facts or constituting history satisfy the direct obtaining predicate for these participants | one world-side relation occurrence whose participants retain their own kinds | direct relation pattern for the test and identity rule; the current case for its factual basis; A.6.REL only when occurrence identity is consumed |
| A claim-bearing episteme designates the participants under declared SlotSpecs and records affirmative or negative polarity for the direct predicate; evidence and reliance remain separate when used | an assertion episteme about the direct relation; an affirmative assertion may designate an occurrence only after current-case facts or constituting history satisfy the direct predicate and the identity rule has been applied; the assertion states that result; assertion form by itself neither warrants nor constitutes the occurrence, and any constitutive contribution follows the direct relation’s rule; forecasts, scenarios, counterfactuals, permissions, and other claim families retain their own defining rules | C.2.1, A.6.5, and the direct claim-family definition; add A.10 or the receiving evaluation only when a reliance judgment is current |
| A typed claim ranges over all actual participants corresponding to one declared participant meaning | local C.3 kind whose extent rule selects those participants | C.3 and C.3.1 for kind, subkind, and continuity; C.3.2 for the KindSignature, admissibility, membership judgment, and optional extension |
Keep the direct relation fact under its relation pattern, the claim under C.2.1, and introduce a C.3 local kind only when membership, substitution, quantification, or typed reasoning is current.
The declaration’s local ValueKind constrains the actual participant corresponding to that meaning; when typed quantification is current, a separately defined C.3 local kind and its membership rule supply the reusable classification.
A.6.5:4.7 - Read the SlotSpecs of a Direct System-Role-Assignment Species
A.2.1 defines the U.SystemRoleAssignment relation family through directly declared species. The family has no root RelationSignature that hides several participant laws. Conditional on an independently defined two-participant InspectionShiftAssignment species, a compatible RelationSignature declares the following SlotSpecs under A.6.5. Its predicate, applicability, and InspectorSystemRoleKindDomain remain supplied by that species’ definition, not by the family citation:
| SlotKind | ValueKind | refMode | Meaning |
|---|---|---|---|
HolderSystemSlot | U.System | U.EntityRef | The admitted system that is the holder; a receiving assertion designates it by an entity reference. |
AssignedSystemRoleKindSlot | InspectorSystemRoleKindDomain | ByValue | The local system-role kind assigned under this direct species. |
Every assignment species declares its own participant meanings, predicate, applicability, and occurrence-identity rule. It adds another participant meaning only when its corresponding participant changes the predicate or occurrence identity. A KindSignature, system-role-taxonomy episteme, effective reference scheme, bridge, or model-use structure may interpret a receiving assertion or use when needed; it is not another participant merely because it helps interpret the claim.
assignmentInterval is not another SlotKind or a ValueKind admitted for a relation participant. It is a local content value in an assignment assertion or relation-occurrence description. The field states the currently known temporal extent of one occurrence, including an explicit open end when the occurrence is current. Under A.2.1, an occurrence of one direct species begins when its predicate starts obtaining for all fixed actual participants and continues while it obtains without interruption. A later assertion that supplies the end time can refer to the same occurrence when obtaining was uninterrupted. C.2.1 identifies the revised assertion separately. A missing-evidence interval remains unknown and establishes neither continuity nor a split. The direct rule ends the occurrence when a participant changes or its predicate ceases to obtain; demonstrated non-assignment supports concluding that it ended. A.2.5 defines assignment-state predicates and direct state relations; the patterns for capability, performed Work, and supporting claims retain their distinct definitions.
A.6.5:4.8 - Recover interface and port relations before declaring slots
Keep recognizable source words such as interface, port, endpoint, API, and signature in the recognition sentence; do not erase them and do not promote them into a generic U.Interface. Then use this sequence:
- Repeat the source sentence so the practitioner can still recognize the situation.
- Say in ordinary language what connects, crosses, or is transferred between which entities.
- Recover the direct relation and its definition. If no current definition supplies the needed participant meanings, predicate, applicability, and identity rule, require
A.6.RSIRor record one missing-relation result naming the proposed participants, required predicate, and receiving use. - Only after the direct relation’s definition is recovered, let its
RelationSignaturedeclare the SlotSpecs for participant meanings reused by the receiving typed claim.
Compact contrast. In “the evaporator outlet interfaces with the compressor inlet,” keep interfaces for recognition. If the intended claim is that refrigerant crosses from one named outlet to one named inlet, name that medium and those two endpoints and recover the transfer-relation definition before declaring any slots. If interface instead names a diagram boundary, API description, protocol, or publication form, use the definition for that object and use. A catalogue of possible participants closes neither branch; without a definition of the direct relation, stop before a RelationSignature.
A.6.5:4.9 - Name the operation by the object that changes
| Operation | Change | Defining or constraining content |
|---|---|---|
| supply a designation under one SlotSpec in an assertion or description | carry a value or reference that designates an entity of the declared ValueKind, without thereby asserting participation | A.6.5 supplies designation typing; the direct-relation definition supplies the participant meaning and predicate |
| replace a participant designation in an assertion or description | change the designation associated with one SlotSpec while preserving that SlotSpec | identify the entity designated under the SlotSpec’s refMode, then let a system apply the direct obtaining test to the relevant facts or constituting history before recording assertion polarity and any separate reliance posture |
| substitute a participant designation in typed reasoning | replace one designation with another while preserving the SlotSpec, resolving the designation under its declared scheme when refMode is a RefKind, and checking the designated entity against the ValueKind while the designation satisfies refMode and, when applicable, RefKind; designation substitution by itself does not replace a world-side participant or establish predicate truth | A.6.5; C.3/C.3.1 only when a local participant-kind or subkind use is current, and C.3.2 for that kind’s membership judgment |
| retarget a reference | replace one reference value in an episteme with another of the same RefKind | the receiving episteme’s definition states how it carries the designation; the effective reference scheme supplies the resolution rules and the RefKind declaration constrains the referent range; F.18 enters only when a durable name changes; world-side change is a separate claim |
| resolve a reference | obtain the designated referent from a reference under its reference scheme | the effective reference scheme supplies the resolution rules and the direct RefKind pattern constrains the referent range; F.18 enters only when durable naming is current |
| revise or re-edition a referent | change the referred object or episteme under its own continuity rules | direct object and edition patterns |
F.18 supplies the rules for durable name designation; participant-designation substitution and reference resolution do not. When a system selects a method at run time, use the definition of that method family or selector; A.6.5 supplies no method-selection operation. Do not rename that choice with the generic slot binding metaphor. If early or late timing matters, name which operation in this table is early or late.
A.6.5:5 - Archetypal Grounding
A.6.5:5.1 - System-role assignment: first minute, substitution, and repeated occurrence
First minute. Assume the case facts explicitly: Robot_7 is an admitted U.System; InspectorSystemRole is a local system-role kind; and InspectionShiftAssignment <: U.SystemRoleAssignment declares only two participant positions, holder System and assigned system-role kind. InspectionShiftAssignment-17 is the occurrence with those values that obtains without interruption from 09:00 to 17:00 on 13 July. A.2.1 supplies the family and continuity discipline; it does not inspect this robot or warrant the assertion. The species predicate, applicability, and InspectorSystemRoleKindDomain must come from the independent InspectionShiftAssignment definition, which is assumed but not supplied here. The directClaimFamilyRef below is a placeholder for that source. The stated case facts satisfy that predicate, and the SystemRoleAssignmentAssertion records affirmative polarity. Any evidence and reliance posture remain separately established. The following field block represents that assertion episteme:
SystemRoleAssignmentAssertion:
directClaimFamilyRef: <independent InspectionShiftAssignment definition>
participantDesignations:
HolderSystemSlot: Robot_7_Ref
AssignedSystemRoleKindSlot: InspectorSystemRole
assignmentInterval: [2026-07-13T09:00, 2026-07-13T17:00]
The two labels inside participantDesignations are convenient source-side labels in this compact representation. An explicit representation correspondence relates each label to the SlotSpec identified by the matching SlotKind in the InspectionShiftAssignmentRelationSignature; equal spelling does not identify field and SlotKind, and another source field keeps its own name. assignmentInterval is a different assertion field and corresponds to no relation-participant SlotSpec. Robot_7_Ref : U.EntityRef resolves to Robot_7 : U.System; InspectorSystemRole is carried by value under the declaration-local InspectorSystemRoleKindDomain. The assertion does not create the assignment, and neither the system-role kind, assertion, nor assignment performs inspection Work.
If inspection admission also needs InspectionReady, A.2.5 tests InspectionShiftAssignment-17 against that SystemRoleAssignmentStatePredicate. The resulting SystemRoleAssignmentStateRelation is separate from the assignment and has its own maximal continuous truth interval. The assignment may continue while that state relation ceases to obtain.
Substitution. Assume Robot_8_Ref : U.EntityRef resolves to another admitted Robot_8 : U.System. Replacing only the HolderSystemSlot designation with Robot_8_Ref passes the declared ValueKind check, but it does not create an assignment for Robot_8. Current case facts must separately satisfy the direct InspectionShiftAssignment predicate before an affirmative assertion is warranted. The proposed designation can therefore be type-correct while the direct claim remains negative or unresolved.
Repeated occurrence. If the same two participants enter another inspection shift after a demonstrated non-assignment period, the A.2.1 continuity rule ends the first occurrence and starts another. A copied field block or reused row key does not merge them. Conversely, an assertion that closes an open assignmentInterval can refer to the same uninterrupted assignment; an evidence gap alone does not split it. Under that continuing assignment, true → false → true for one fixed A.2.5 predicate creates two assignment-state-relation occurrences without creating another assignment.
A.6.5:5.2 - Hypothetical physical-assembly boundary
Bearing_B isPartOf Pump_P may remain a readable source claim, but current A.14 supplies no generic or installed-part occurrence-identity rule based on removal, reinstallation, installation interval, or installation work. PartHolonSlot, WholeHolonSlot, and their RefKinds are therefore only a hypothetical declaration candidate until an accepted direct part-relation pattern states the participant meanings, predicate, applicability, and same-versus-new-occurrence rule. Do not claim current conformance or an individuated part-relation occurrence from this sketch.
Conditional on such a future declaration, changing a proposed part designation from Bearing_B_Ref to Bearing_C_Ref could be ValueKind-compatible while the direct relation remains false because current case facts do not satisfy its predicate. Until that parthood relation is defined, keep the bearings, pump, installation work, proposed part relation, assertion, designations, and representation separate. The counterexample demonstrates that typed substitution cannot create obtaining; it does not supply the missing parthood settlement.
A.6.5:5.3 - Episteme fields are not relation participants by table shape
C.2.1 identifies an evaluation episteme by its EntityOfConcern, ClaimGraph, and effective ReferenceScheme. An EntityOfConcernRef designates that entity when such a reference is used. A card or tuple view may contain visible fields such as entityOfConcernRef, claimGraph, and referenceScheme. Their co-occurrence in one record does not by itself establish another world-side relation, make the fields participants, or declare SlotSpecs for them.
When a direct relation among an episteme and other entities is current, its definition states the relation kind, participant meanings, obtaining condition, and occurrence identity, and its compatible RelationSignature contains the needed SlotSpecs. A.6.5 supplies the rules for typing participant designations in a receiving assertion. This prevents a convenient episteme form from becoming a pseudo-relation merely because it can be drawn as a tuple or table.
A.6.5:5.4 - Relation-dependent result wording
After machining, the machined component can remain the same physical entity in a changed state. It does not acquire a special result kind. Start with one question: did this same component continue through the change, or did a new entity begin?
- Same component continued. Name that component, the characteristic that changed, and the machining transformation. Use the pattern that defines that characteristic and A.3.4 for the bounded change. The component’s identity continues; calling it the work’s “result” adds no kind, participant meaning, or relation.
- A new entity began. Use this branch only when a current definition supplies an admitted identity-inception predicate and identity rule and the current Work and change facts satisfy them. If no such definition exists, return one missing identity-inception result naming the candidate entity, relevant work and change facts, required inception predicate, and receiving use. Do not infer a generic work-result relation.
- The sentence names another relation. Rewrite it with its one verb and participants before declaring slots. For example,
Component_C was delivered to AssemblyCell_2selects one candidate delivery claim about that item and receiver, not aresultkind. Recover that direct relation’s definition and any additional participant meanings it requires; if that definition cannot be recovered, return a missing-relation result. Handle an evaluation or acceptance sentence separately when that is the wording rather than listing possible pattern families.
Only the direct relation selected by one of those sentences receives a compatible RelationSignature, and only when reusable typed use is current. Its assertion episteme records that relation; A.6.5 neither invents a broad result participant nor turns the domain choice into a catalogue.
A.6.5:5.5 - Formal reduced case
The expression 3 < 5 is notation in a mathematical assertion. Its numerals, comparison sign and operand places are representation elements; they are not thereby SlotSpecs. An ordinary comparison can stop with its mathematical meaning. Suppose a later FPF use needs to substitute operands under one reusable typed lesser-than declaration. The direct-relation definition must then supply the entities denoted by the numerals, the lesser-number and greater-number participant meanings, obtaining condition and direct occurrence-identity rule. A compatible RelationSignature may declare LesserNumberSlot and GreaterNumberSlot, with a correspondence from the representation’s operand places and designations. Operand order remains local to the representation. The mathematical interpretation and applicable rule supply the comparison’s grounds; notation shape alone supplies no FPF relation declaration. This receiving use needs typed substitution but no explicit occurrence individuation, so the engineer stops there.
A.6.5:6 - Bias-Annotation
This pattern has a typed-declaration bias because it serves relation uses that depend on reusable participant typing. Progressive elaboration limits that bias: ordinary users stop at a readable relation sentence when no receiving use depends on SlotSpecs.
It also has a logic-facing bias because predicates and typed declarations make substitution and comparison reviewable. Constructive FPF adds what that logical form alone cannot supply: grounded participants and direct rules for obtaining and occurrence identity.
A declaration episteme describes reusable relation semantics; a separate representation episteme may represent an assertion or relation-occurrence description. Neither episteme is the world-side relation occurrence by form. Publishing an unchanged episteme preserves its C.2.1 identity; any effect on a world-side occurrence follows that occurrence’s direct rule.
A.6.5:7 - Conformance Checklist
- The direct relation kind and the definition of its predicate, applicability, participant meanings, and occurrence-identity rule are named before SlotSpecs are declared.
- Every participant meaning needed by reusable typed use has one complete
<SlotKind, ValueKind, refMode>SlotSpec in theRelationSignature. - Each SlotKind is local to the one
RelationSignaturethat contains its SlotSpec. - World-side relation prose names participant meanings and actual participants. Declaration prose uses
SlotSpecfor the complete declaration and...Slotfor its declaration-local SlotKind. Receiving-episteme prose distinguishes a designation from its referent, using...Reffor the reference kind or value. For a field receiving relation semantics, apply the §4.2 declaration or representation-correspondence rule. Position and place remain ordinary representation words unless a declaration establishes a SlotSpec. - Each ValueKind is exact enough for the direct predicate and does not combine participant kinds for which the predicate has different semantics.
- An assertion or description episteme that designates a participant by reference names the RefKind and resolves it to the declared ValueKind.
- The actual relation participant, its reference, reference resolution, SlotSpec declaration, participant designation in the assertion, and relation occurrence remain distinct.
- A C.3 kind is introduced only for a current typed-quantification, membership, substitution, or subkind use.
- A verb-shaped predicate is not used as evidence of work, method, transformation, agency, or holonhood.
- Only an admitted
U.Systemis admitted forHolderSystemSlot. Each species underU.SystemRoleAssignmentdeclares itsAssignedSystemRoleKindSlotdomain and any additional participant meaning whose value changes the predicate or occurrence identity. U.WorkandU.Methodrely on their own constructive holon tests, whileU.Transformationrelies onA.3.4’s actual-bounded-change identity; A.6.5 admits none of them by grammar.- The direct-relation definition supplies the obtaining predicate and occurrence-identity rule; current-case facts or constituting history supply the factual basis; a claim-bearing episteme records polarity; and evidence or reliance remains a separate judgement.
- A declaration, assertion, description, representation, or publication episteme does not create the world-side relation by form.
- Ordinary use can stop before signatures, explicit occurrence identity, or C.3 kind derivation when the receiving use depends on none of them; typed reuse, occurrence identity, and local-kind quantification are independent thresholds, and none is a prerequisite for another.
- A relation fact, an episteme claim, and a locally derived kind are handled by the patterns that define those respective objects.
- A SlotSpec declares one direct-relation participant meaning inside one
RelationSignature. Method-description, operation, plan, work, evaluation, representation, card, schema, and record fields retain the kinds and declaration rules supplied by their defining patterns; a field that receives relation semantics uses the applicable §4.2 route. - An A.15.3 planned-filling row may cite a SlotSpec, but the planned designation remains plan content and establishes neither an actual participant nor relation obtaining.
- Interface, port, endpoint, API, and signature language remains available for recognition. The text states what connects, crosses, or is transferred between which entities and recovers the direct-relation definition before declaring SlotSpecs; an unresolved case requires A.6.RSIR or a missing-relation result.
- When result wording leaves continuation or inception unresolved, determine whether the same entity continued or a new entity began. Recover a separately asserted delivery, acceptance or evaluation relation from its predicate and participants; clear wording needs no additional history inquiry. A catalogue or generic result kind cannot supply a missing relation.
A.6.5:8 - Common Failure Modes and Repairs
| Failure | Why it matters | Repair |
|---|---|---|
Generic byRef without a RefKind | A later use cannot tell what referent kind can be resolved. | Declare the RefKind, or expand the compact sketch next to its use. |
| Reference substituted for the referent required by the direct participant meaning | A storage or publication choice changes the claimed world-side participant. | Keep that referent as participant; state refMode for the designation carried by the receiving assertion or description episteme. |
| One SlotSpec contains a ValueKind written as a list of unrelated alternatives | Different predicate semantics are hidden behind one participant meaning. | Recover the common ValueKind when one exists; otherwise split the relation kind. |
| One source word names a SlotKind, participant ValueKind, reference and field | A reader cannot tell what may be substituted, resolved or renamed. | Distinguish the declaration, designation and referent. For example, HolderSystemSlot is local to the declaration, Robot_7_Ref is an entity reference and Robot_7 is its System referent. Keep the source field name and state the applicable correspondence. |
| Active grammar treated as proof of literal agency | A grammatical subject is assumed to be the acting System without grounds. | Recover the actor when the claim depends on literal action. Keep clear ordinary metonymy; use the defining patterns only for a remaining relation, Work, Method or transformation question. |
A universal context, taxonomy, scheme, or model-use SlotSpec added to the U.SystemRoleAssignment family or every species | Interpretive or receiving-use material is turned into a world-side participant, and several assignment laws are hidden under one root signature. | Give each assignment species only HolderSystemSlot, its declaration-local AssignedSystemRoleKindSlot, and any additional participant meaning whose value changes the predicate or occurrence identity. Keep a KindSignature, taxonomy episteme, scheme, bridge, or model-use structure with the assertion or receiving use unless another relation independently makes it a participant. |
| Interface language erased or promoted | A recognizable source sentence is replaced by either a generic U.Interface or an untyped participant catalogue. | Keep the source word for recognition, state what connects, crosses, or is transferred between which entities, recover the definition of the direct relation, and declare only the SlotSpecs that a receiving typed use reuses. Stop at A.6.RSIR or a missing-relation result when the relation remains undefined. |
| Result-family catalogue | The word result triggers a list of possible relation families, so the reader cannot tell which object continued or what claim to make. | When that distinction is unresolved, ask whether the same entity continued or a new entity began. For continuation, name the changed characteristic and transformation. For inception, require an admitted identity-inception predicate and its definition. If another verb such as delivered is present, recover that one relation and its participants. Return the corresponding missing-relation or missing identity-inception result when the needed definition is absent. |
| A participant designation is promoted into a new qualification ontic | A value or reference in an episteme is mistaken for a further world-side object. | Apply the three-way dispatch in A.6.5:4.6: direct relation fact, assertion episteme, or current local participant kind. |
| A method-description, operation, plan, work, evaluation, card, schema, or record field is called a SlotSpec | A reusable direct-relation participant declaration is invented from representation shape or broad wording. | Require the direct-relation definition and one RelationSignature and SlotSpec. Apply §4.2: explicitly declare a receiving semantic field against that SlotSpec, or keep an external or independently named representation field’s source name and state its explicit correspondence to that SlotSpec. Keep the field, SlotSpec, designation, and actual participant distinct. Handle operation arguments and results under A.6.1 and use the definitions for the other fields. |
| An A.15.3 planned designation is treated as the actual relation participant | Plan content is mistaken for world-side participation and predicate satisfaction. | Keep the row in the WorkPlan; identify any later participant and obtaining relation independently under that relation’s definition. |
A.6.5:9 - Consequences
Benefits. Typed relation reuse becomes reviewable without treating an assertion or storage record as the world-side relation. Substitution checks can name the SlotKind and participant ValueKind. Reference changes can be distinguished from referent changes. Local system-role kinds remain separate from their holder systems and assignment occurrences, and relation predicates remain separate from Work and agency.
Costs. Load-bearing relation patterns need participant ValueKinds and designation modes. A proposed ValueKind may require a relation-kind split when the direct predicate has different semantics for different participant kinds. Existing compact byRef sketches may need adjacent expansion before another pattern can rely on them.
Limits. A.6.5 is limited to SlotSpec declarations and participant-designation typing. It neither defines the direct obtaining test nor decides a current case. The direct-relation definition supplies the predicate and identity rule, current facts or constituting history supply the case basis, and a claim-bearing episteme states the result. Separate patterns define evidence, reliance, model-use structure selection, and domain-interface semantics.
A.6.5:10 - Rationale
SlotKind, ValueKind, and refMode answer three different engineering questions about one RelationSignature: which participant meaning does this declaration distinguish, what kind must an entity designated under that meaning have, and how does a receiving assertion or description episteme designate that participant. When refMode selects reference designation, RefKind names the reference kind. Keeping the answers separate is enough to support typed substitution and reference use without adding a universal relation record.
The direct-relation definition remains essential. A pair of typed participants does not say whether the relation obtains or whether repeated occurrences with the same participants are identical. Constructive ontology therefore combines logical slot discipline with grounding and domain identity rather than treating a schema as the world.
The predicate boundary prevents a second collapse. Natural language often verbalizes relations, work, methods, and transformations. FPF admits their kinds through direct ontological tests, not through grammar. This keeps only systems as actors and as actual participants corresponding to HolderSystemSlot, while preserving the accepted holonhood of work and methods and the separate actual-bounded-change identity of transformations.
A.6.5:11 - SoTA-Echoing
| Source line | What it contributes | FPF adoption and practical effect |
|---|---|---|
| Lean 4 reference: structures and fields | The Lean language reference makes each structure field and its type explicit; a later field type may depend on an earlier field. | Adapt as a formal stress test. In a SlotSpec, the declaration-local SlotKind and participant ValueKind are explicit. FPF does not infer that a Lean structure is a world-side relation or ontic. This informs the formal reduced case in A.6.5:5.5, where operand order remains local to the mathematical representation and an explicit correspondence relates operands to RelationSignature SlotSpecs before FPF reuse. |
TypeDB relates statement | In TypeDB 3.x syntax, each external role type is declared through a named relation type, with explicit scope when equal labels occur under different relation types. | Adapt the declaration locality. FPF uses SlotKind, not SystemRole, for the declaration-local name of a participant meaning inside a RelationSignature; the system-role kind remains the by-value participant under a direct assignment species’ AssignedSystemRoleKindSlot, and occurrence identity remains with A.2.1 rather than storage identity. This prevents HolderSystemSlot, AssignedSystemRoleKindSlot, and InspectorSystemRole from collapsing in A.6.5:5.1. |
| RDF 1.2 Concepts | The RDF 1.2 Candidate Recommendation of 7 April 2026 distinguishes triple terms, propositions, asserted triples, and reifiers used in further statements. | Adopt the separation. A graph term or reifier may represent an assertion, but it does not replace the world-side relation, direct obtaining condition, or SlotSpec. This is the boundary exercised by the episteme case in A.6.5:5.3. |
| Almeida, Guizzardi, Sales, and Fonseca, gUFO, 2026 preprint | This comparison line exposes relation aspects, reification choices, and higher-order typing pressure. | Use as a stress comparator. Keep relation occurrence, signature, assertion, and local typed projection distinct without importing the source taxonomy as FPF ontology. This informs the three-way dispatch in A.6.5:4.6 and the result-qualification case in A.6.5:5.4. |
A.6.5:12 - Relations
A.6.0definesU.SignatureandRelationSignature; A.6.5 supplies SlotSpec declaration discipline inside their vocabulary declarations.A.6.RELdefines explicit relation-occurrence individuation and the progressive threshold for stable reference.A.6.PandA.6.RSIRrecover the direct relation and its participants before slot typing begins.- Use
A.2.1for the system-role-assignment family’s discipline and continuity rule, the direct species definition for its predicate, applicability, participant meanings, and assigned-kind domain, and A.6.5 for the SlotSpec reading of that species’ declaration. C.2.1defines episteme identity, assertion and description content, and their semantic fields; A.6.5 §4.2 gives the declaration and representation correspondence routes by which such fields receive relation semantics while field, SlotSpec, designation, and actual participant remain distinct.C.3andC.3.1define local participant kinds, subkind relations, and continuity when membership, substitution, typed quantification, or subkind use is current;C.3.2supplies the KindSignature, membership judgment, and optional extension.A.15.3may cite a RelationSignature SlotSpec for a planned participant designation; A.15.2/A.15.3 define the planned claim, the direct-relation definition supplies the participant meaning and later actual-participation predicate, and A.6.5 supplies only SlotSpec declaration discipline. Operation arguments and results remain A.6.1 declarations.A.15.1andA.3.1define the constructive holonhood and identity of Work and Methods;A.3.4defines the actual-bounded-change identity of transformations;E.18defines selected transformation-flow structures over those independently defined transformations and adjacent loci.A.1,A.2,A.2.1, andA.15keep acting systems, local system-role kinds, system-role assignments, Methods, and performed Work distinct.- Use
A.2.4for compact episteme evidence-use and status-use relation SlotSpecs,A.10for the full evidence-provenance path, andF.10for durable status semantics. - A named C.30 architecture-relation pattern supplies the rule for its relation.
A.6.Mrepairs module-interface claims and specifications; it admits no general direct module relation. After A.6.RSIR recovery, a direct relation needs its own definition before A.6.5 declares its SlotSpecs. C.29governs a declared mathematical-lens use of tuple, graph, database, or mathematical representations of a relation, assertion, signature, or occurrence description.E.10supplies wording-use recovery,E.24.UKsupplies the U-kind admission test, andF.18supplies designation guidance after the object is known.