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 exact world-side kind must the corresponding actual participant have, and how does a receiving assertion or description episteme designate that participant. When refMode selects reference designation, RefKind names the exact reference kind. Keeping the answers separate is enough to support typed substitution and honest 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.